Shorten time of lesson_lock feature testing - #51362
Merged
Merged
Conversation
hannahbergam
changed the title
bethanyaconnor
approved these changes
Apr 14, 2023
bethanyaconnor
left a comment
bethanyaconnor
left a comment
Contributor
There was a problem hiding this comment.
Yay thanks for doing this!
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
2 participants
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.
The lesson_lock feature file takes the longest to run and makes our drone runs take longer and longer. Splitting it in half will allow the scenarios to run in parallel, shortening the overall required time. I split them along the lines of 'retake' vs 'everything else'.
Links
Testing story
Deployment strategy
Follow-up work
Privacy
Security
Caching
PR Checklist: