-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with JUnit5 5.10.0-M1 #94
Comments
This isn't quite as straightforward as "a shading issue". There's a discussion of the problem here And a fix for maven users here 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
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.
The text was updated successfully, but these errors were encountered: