Split assessment tab UI test scenarios to speed up re-runs #26567
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
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.
As DotD today, I needed to re-run
teacher_dashboard_assessments.featureand it took 20 minutes to fail! It only takes 6 minutes to pass, but since it has many steps where waiting for elements is required, re-runs can be time consuming.Since the test's 2 scenarios are not dependent on one another, I split them into two files to expedite both the initial runs and any re-runs that need to occur. This is consistent with other files that have been split for expediency (example) as a lightweight mitigation for long running tests.