-
Notifications
You must be signed in to change notification settings - Fork 114
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
[UI] Test LCE and CV assignment of newly created AK #16880
[UI] Test LCE and CV assignment of newly created AK #16880
Conversation
|
PRT Result
|
session.activationkey.create( | ||
{'name': ak_name, 'lce': {'Library': True}, 'content_view': constants.DEFAULT_CV} | ||
) |
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.
I think it would make more sense to test if non-default lifecycle and CV's are selected while AK creation
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.
@Gauravtalreja1 Can you elaborate on that? Also, I am following the bug description.
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.
I think this might be easily expanded to test also non-default org/loc/... But it covers the specified bug reproducer. ACK.
* Test lce and cv assignment of new AK * Remove unused module_lce_library * docstring change (cherry picked from commit 37a277b)
Problem Statement
SAT-28981 introduced a bug when creating a new AK which had Library and Default Content view assigned during its creation, it did not have it assigned after its creation.
Solution
Adding UI automation for this bug that tests that LCE and CV assignment went through.
PRT test Cases example