-
Notifications
You must be signed in to change notification settings - Fork 266
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
automation: services tests #13152
base: master
Are you sure you want to change the base?
automation: services tests #13152
Conversation
bde4b16
to
efa6db7
Compare
9cda750
to
e892ba2
Compare
e892ba2
to
61d53af
Compare
61d53af
to
cfab139
Compare
@a-arias could you take a look at this too? 👍🏽 |
@yonasberhe23 Will this only cover external names ? In that case the task can be break down to smaller ones for Other than that it looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great job, I added 2 observations that could be potential improvements.
resourceDetail() { | ||
return new ResourceDetailPo(this.self()); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be good to add a little documentation on these methods to get a quick idea of what UI element they return
} | ||
|
||
growlList() { | ||
return this.self().find('.growl-list'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the classes the only way to get these elements? , we could use ids or a combination of classes and names with xpath to create stronger locator strategy.
Summary
Fixes #rancher/qa-tasks#1581
This PR also includes small fixes to address flaky Extensions tests.
Checklist