Finally randomize feature & scenario ordering #204
Merged
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
added 10 commits
September 4, 2017 14:08
We need the relative filename involved in both so that a seed can generate stable randomizations across runs and machines. Similarly, that's why we need the line number for Scenario#ordering_id.
I could narrow it down to the exact versions of which librariess and figure out exactly why that combination made the failure happen. However, I can't find a compelling reason why this test shouldn't pass in step_definitions like the others in this file, and that change makes the test pass with the library version combos where it previously failed, and doesn't affect it elsewhere. So, we're going with that.
oriolgual
approved these changes
Jun 4, 2018
|
Thanks @yarmiganosca, this looks really nice! |
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.
So, yeah, it's been a over a year since a said I'd get to this "next week". My bad. Anyway, I'm finally delivering #196. Here's an overview of the design. Both the feature and scenario runners will have the same
Ordererinstance attached to them, which decides the order the features or scenarios are executed in. The only 2 currently availableOrderers areDefaultandRandom.--seed SEEDallows you to specify the seed provided to theRandomorderer, and--randactivates theRandomorderer with a random seed.