-
Notifications
You must be signed in to change notification settings - Fork 258
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] - Additional user retention settings tests #11688
Merged
Merged
+103
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
izaac
added
area/authentication
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
labels
Aug 23, 2024
izaac
force-pushed
the
user_retention_cases
branch
6 times, most recently
from
August 26, 2024 21:55
dcce55b
to
fd3a5d6
Compare
izaac
force-pushed
the
user_retention_cases
branch
3 times, most recently
from
August 27, 2024 14:49
c749501
to
a60802e
Compare
yonasberhe23
previously approved these changes
Aug 27, 2024
I'll revisit this implementation as it's no longer applicable on |
izaac
force-pushed
the
user_retention_cases
branch
6 times, most recently
from
September 13, 2024 16:55
bb166fb
to
0b7dc18
Compare
izaac
force-pushed
the
user_retention_cases
branch
from
September 16, 2024 17:04
0b7dc18
to
ff0595e
Compare
yonasberhe23
approved these changes
Sep 20, 2024
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!
Linked issue: rancher/rancher#46795 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/authentication
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes rancher/qa-tasks#1400
Occurred changes and/or fixed issues
Adding new scenarios to the user retention test automation suite.
Technical notes summary
The account has the
Disable After
andDelete After
enabled.Checking a standard user can't access the Retention settings.
Areas or cases that should be tested
Automation of User retention settings
CI execution
Areas which could experience regressions
Jenkins/GA
Checklist