-
Notifications
You must be signed in to change notification settings - Fork 115
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
Discovery Provisioning UI coverage #12991
Discovery Provisioning UI coverage #12991
Conversation
25a8943
to
b9f750c
Compare
trigger: test-robottelo |
trigger: test-robottelo |
b9f750c
to
cb1056d
Compare
trigger: test-robottelo |
2 similar comments
trigger: test-robottelo |
trigger: test-robottelo |
trigger: test-robottelo |
1 similar comment
trigger: test-robottelo |
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.
Shall we add test steps
for the modified tests along with chages? one can easily relate execution flow & test steps before starting with reivew or contribution.
The test steps are already there in the tests :) |
Yea, seems like only |
The failing PRT is not because of the changes in the PR. |
cb1056d
to
25af558
Compare
Yes those are the one-liners there @vijaysawant |
25af558
to
ba846f5
Compare
(cherry picked from commit e803cc4)
(cherry picked from commit e803cc4)
Discovery Provisioning UI coverage (#12991) (cherry picked from commit e803cc4) Co-authored-by: Adarsh dubey <[email protected]>
Discovery Provisioning UI coverage (#12991) (cherry picked from commit e803cc4) Co-authored-by: Adarsh dubey <[email protected]>
Adding UI coverage for Discovery provisioning scenarios.