-
Notifications
You must be signed in to change notification settings - Fork 58
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
PITest suddenly breaks #340
Comments
When running from gradle, 1.2.0 of pitest-junit5-plugin may need the junit-platform-launcher to be added to pitest's classpath. See https://github.com/pitest/pitest-junit5-plugin Your original "pitest needs a green suite" message means one or more tests are failing when run via pitest. To understand why, the first step is to enable pitest's verbose logging and identify which tests have failed. |
@Ledmington As Henry said, that should help. The feature to automatically add junit-platform-launcher is already tracked. |
Hello, sorry for the late answer... I honestly forgot about this issue.
in my |
@Ledmington I've released the SNAPSHOT version which automatically adds that dependency 1.14.0 (see #353). You can see how to use the SNAPSHOT version in that PR: https://github.com/rahulsom/pitest-junit-compat/pull/2/files Could you check, if it works in your project? The implementation for Gradle is somehow tricky and there might be some corner cases :-/. |
Hello, I am using PITest in my project along with many parameterized tests and I noticed that when launching the tests with
gradlew.bat test
everything passes, but when I rungradlew.bat pitest
I getPitest needs a green suite
. I tried upgrading it to the following configuration and now it doesn't even start.This is the error I receive
The text was updated successfully, but these errors were encountered: