Add cucumber.junit-platform.discovery.as-root-engine
#3023
Merged
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?
The SBT JUpiter Interface assumes that all tests are classes but does discovery on the classpath root. As a result, it turns feature names into class selectors. Which doesn't quite work.
Setting
cucumber.junit-platform.discovery.as-root-engine
tofalse
injunit-platform.properties
should ensure Cucumber only discovers tests when called by another engine (e.g. the JUnit Platform Suite Engine) and by pass this behaviour.🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
Does this work?
📋 Checklist: