Closed davidburstrom closed 12 months ago
This isn't quite as straightforward as "a shading issue". There's a discussion of the problem here
https://github.com/hcoles/pitest/pull/1209
And a fix for maven users here
https://github.com/hcoles/pitest/pull/1212
I'll release this and a new version of the junit-5-plugin shortly. Gradle users will need to manually add platform-launcher to their test classpath until a fix similar to the maven soloution can be added to the gradle plugin.
This is fixed by the combination of 1.2.0 of the junit5 plugin and pitest 1.14.0.
If you are using gradle, you will need to also ensure that junit-platform-launcher v 1.10.0-M1 is included on the test runtime classpath.
wow.. tested it works now.. with all the changes..
curious in 5.9.2 this dependency was not needed now with 10.x this is needed
testRuntimeOnly("org.junit.platform:junit-platform-launcher")
what changes in 10.x made such explicit need as my junit test cases work even without this dependency even on 10.x but not pitest.
Using pitest-junit5-plugin version 1.1.2 and JUnit 5 version 5.10.0-M1, test discovery fails with the attached stacktrace. It works if JUnit 5 version 5.9.2 is used. Seems like a shading issue.