Since cucumber/cucumber-jvm#3023 you can work around this problem by upgrading to Cucumber v7.26 and setting cucumber.junit-platform.discovery.as-root-engine to false in junit-platform.properties. This should ensure Cucumber only discovers tests when called by another engine (e.g. the JUnit Platform Suite Engine) and bypass SBTs discovery issues.
Originally posted by @mpkorstanje in #142
I tried setting the above and using cucumber 7.26.0 but still maven test summary is:
[INFO] Tests run: 0 , Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 168.7 s -- in runners. Test
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] --- 0;32msurefire:3.5.3:test (run-test)
configuration
cucumber 7.26.0
junit-platform 5.13.3
maven surefire/failsafe 3.5.3
Junit5 tests run successfully when run via IDE and via maven, only issue is that maven test summary is always zero count