Fix JUnit rule run order #1363
Merged
Fix JUnit rule run order #1363
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
marcphilipp
previously approved these changes
Jul 28, 2021
Prior to this commit the rules were executed in the wrong order. When rules we used in both parent and child classes, then the rules in the child classes were executed before those of the parent class. Fixes spockframework#1050
leonard84
force-pushed
the
1050-fix-junit-rule-run-order
branch
from
e1c2490
to
64bfef1
Compare
marcphilipp
approved these changes
Aug 5, 2021
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.
Prior to this commit the rules were executed in the wrong order.
When rules we used in both parent and child classes,
then the rules in the child classes were executed before those of the parent class.
Fixes #1050