Deprecate cucumber-junit in favour of cucumber-junit-platform-engine #3016
+15
−4
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.
⚡️ What's your motivation?
With JUnit 4 in maintenance mode and JUnit vintage being deprecated support for JUnit 4 is winding down. As such users should be encouraged to migrate away from JUnit 4 and
cucumber-junit
onto JUnit 5 with thecucumber-junit-platform-engine
.Closes: #3015
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
To the best of my knowledge,
cucumber-junit
andcucumber-junit-platform-engine
have feature parity. If there is something is missing, please create an issue.📋 Checklist: