[660] Use the correct implementation of the MethodOrderer for the @Te… #661
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.
…stMethodOrder annotation.
resolves #660
What's changed?
Changed the value for the
@TestMethodOrder
class toMethodOrderer.OrderAnnotation.class
when migrating Arquillian JUnit 4 tests to JUnit 5 that use the@InSequence
annotation.What's your motivation?
The current value,
MethodOrderer.class
, is an interface and cannot be instantiated.Have you considered any alternatives or workarounds?
The only workaround is to simply manually change the annotation value.
Any additional context
N/A
Checklist