Change afterEaches to run in more natural order #359
Merged
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.
This fixes #357. In order to have afterEaches run in a more natural order (closest to the test first and out through the experiments), this prepends the afterEaches to the returned set as it finds them. The blocks are then run in a more natural order. As a side note: this still is running them in the order they are defined in the experiments.
A test has been added in the suite for this change, but to specifically show the test displayed in the issue, the output with this branch is as follows: