Consider adopting JUnit 5.13's `DiscoveryIssue`-reporting mechanism

[marcphilipp]

🤔 What's the problem you're trying to solve?

As @mpkorstanje pointed out in junit-team/junit5#4380 (review) there are use cases for the Cucumber JUnit engine to report warnings/errors encountered during test discovery.

✨ What's your proposed solution?

JUnit 5.13 will introduce a new mechanism for reporting issues encountered during discovery. They can have different severities. By default, any error will cause the engine descriptor to be reported as failed during test execution with a DiscoveryIssueException listing the critical discovery issues. Non-critical issues are logged. The critical severity level is configurable. Please see the JUnit User Guide for more info.

For example, in JUnit Jupiter, validations are now in place that report invalid test methods that won't get executed to avoid such issues from going unnoticed.

⛏ Have you considered any alternatives or workarounds?

No response

📚 Any additional context?

No response

[mpkorstanje]

Cheers Marc!

Once 5.13 is released we can:

• Replace the warning for the use of the cucumber.features property with an info message.
• Add an info message when the CucumberTestEngine is given a ClassSource for Maven/Gradle compatibility
• Replace the warning about the lack of features when using deprecated @Cucumber annotation.
• Replace the warning about the use of the class-path resource selector for a directory (to be introduced in [JUnit Platform] Use EngineDiscoveryRequestResolver #2835)
• Add an error for feature files with parse errors
• Add warning about deprecated cucumber.* properties
• Add info about unknown cucumber.* properties
• Add errors for all property parsing problems
• Add info message for random seed used to order scenarios