Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge vyper locators natively in uiveri5 #175

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gtreskas
Copy link

@gtreskas gtreskas commented Mar 9, 2020

No description provided.

"data-sap-ui": "*categoryList-0",
"role": "option",
"class": "*sapMLIB*sapMSLI",
"id": "__item1-container-cart---homeView--categoryList-0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please avoid examples with unstable ids

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its intented this way but will be adjusted anyway

});

it("step0v1: check name is Accessories - check with dom properties nodename and id", async function () {
await browser.sleep(5000);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are all these sleeps necessary? is there something wrong with the synchronization?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no not necessary again intented

*/
VyperLocator.prototype.register = function (by) {
this.logger.debug('Registering custom locator');
by.ui5All = function(mMatchers) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all to me sounds like 'element.all' and is confusing

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the way that is writen currently, it will not change yet but improvement will be considered (unfortunetaly was called like that always before we got it handover to us)

if(mParams.prevSiblingProperties ||
mParams.nextSiblingProperties ||
mParams.siblingProperties) {
// ?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

until we have a matcher/selector for this, log a message saying this isn't supported and will be ignored?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will do, I want to write everything down and send an email with all the consolidate points

var elem = await common.locator.getDisplayedElement(ui5ControlProperties);
var attribute = "tooltip";
var compareValue ="Open category Accessories";
var val = await ui5ControlConverter.getControlAggregationProperty(elem, attribute);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we have a getProperty method in uiveri5/control.js, perhaps we should just extend it with getters for aggregations and bindings?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes thats another point that in my list

"text":[{"path": "i18n>welcomeCarouselShipping"}]
}}
};
await ui5.common.assertion.expectAttributeToBe(ui5ControlProperties, "showHeader", "true", 0, 1, 30000);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: we can declare the custom matchers in conf.js

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what do you mean custom matcher?

@gtreskas
Copy link
Author

hi @tsaleksandrova : Thanks for the review, but its not intented on review this yet, have to adjust things first

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants