JUnitPlatformTestFramework#getDetector returns null and there is no way to provide one that I can see. I want to scan the whole classpath for tests matching my criteria. I can do this directly with the JUnit5 API programmatically, but the Gradle JUnitPlatformTestFramework stops my test request from even getting to JUnit runtime with this early check. What’s the reasoning for not allowing us to scan the classpath for tests with JUnit Platform. Seems to work for TestNG and legacy JUnit.
We have a package of shared tests that are expected to pass across several modules and are packaged as a test-fixture.
Update :
It looks to me like an oversight in this commit? Add filtering and tagging support · gradle/gradle@c0edf21 · GitHub The doc update says it just passes all tests, but that’s not true - it passes a filecollection of the test src dir. The scanners for JUnit4 and TestNG scan the implementation classpath