[Automation] - Stabilize imported generic cluster e2e spec#17795
Open
izaac wants to merge 1 commit into
Open
Conversation
Fix flakiness on imported cluster create against Prime Rancher and wrap cluster manager tests with their Qase case IDs: - accept Pending as a transient state alongside Provisioning/Waiting - select provider column by .col-cluster-provider (formatter-derived) - wait for cluster list visibility before masthead/list interactions - extend cluster detail registration page wait to medium timeout - disable Cypress retries on create to avoid stale clusters - wrap eligible it() statements with qase() using the oldest matching Qase case ID per title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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#2317
Depends on: rancher/qa-infra-automation#111
Occurred changes and/or fixed issues
Fix flakiness on imported cluster create against Prime Rancher and wrap cluster manager tests with their Qase case IDs:
.col-cluster-provider(formatter-derived)masthead/listinteractionsit()statements withqase()using the oldest matching Qase case ID per titleAreas or cases that should be tested
Jenkins
Areas which could experience regressions
Jenkins CI
Screenshot/Video
PRIME
COMMUNITY
Checklist
Admin,Standard UserandUser Base