Warn when surefire naming strategy is used #3067
Draft
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 Surefire 3.5.4 the heuristic for naming tests changed[1]. As a result the
surefire
strategy no longer works as expected. But thelong
strategy now does provide reasonable results.On Surefire <= 3.5.2 with the
surefire
strategy the test results would be rendered as:On Surefire >= 3.5.4 with the
long
strategy the test results will be rendered as:Closes: #2984
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
There is no way to detect which version of Surefire is being used. So recommending an upgrade of Surefire seems to be the only sensible thing to do.
📋 Checklist: