-
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
Modify test_positive_ansible_custom_role to cover non-admin user scenario #15163
Modify test_positive_ansible_custom_role to cover non-admin user scenario #15163
Conversation
trigger: test-robottelo |
PRT Result
|
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.
LGTM
Signed-off-by: Gaurav Talreja <[email protected]>
ce949c0
to
7edcddf
Compare
trigger: test-robottelo |
PRT Result
|
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.
LGTM
…ario (#15163) Modify test_positive_ansible_custom_role to cover non-admin scenario Signed-off-by: Gaurav Talreja <[email protected]> (cherry picked from commit 9f38177)
…ario (#15163) Modify test_positive_ansible_custom_role to cover non-admin scenario Signed-off-by: Gaurav Talreja <[email protected]> (cherry picked from commit 9f38177)
…ario (#15163) Modify test_positive_ansible_custom_role to cover non-admin scenario Signed-off-by: Gaurav Talreja <[email protected]> (cherry picked from commit 9f38177)
…ario (SatelliteQE#15163) Modify test_positive_ansible_custom_role to cover non-admin scenario Signed-off-by: Gaurav Talreja <[email protected]>
Problem Statement
Currently, test_positive_ansible_custom_role covers only admin scenario, and as part of component audit its suggest to modify this test to cover non-admin user scenario
Solution
Parametrizing the existing test to cover both admin and non-admin user scenarios with few more changes