Closed mkutz closed 2 years ago
Please:
verbose
mode in the plugin configuration - it should give a reason why it failed,pitest
task with --info
and paste a PIT execution command line (especially the classpath - can be redacted). It might be caused by the JUnit 4/5 misconfiguration.I wonder, if it started to fail unexpectedly or you are configuring it for a new project?
Yeah, OK. That was a trivial. I'm using JUnit 5. Followed this and it worked immediately.
I tried to add it to a new project. So it never worked.
Given that JUnit 5 becomes more and more popular, I'd suggest to make that a bit more prominent in the README.md.
Anyway thanks for the quick reply and the good work in general!
I'm trying to add PIT in my Gradle project, but get an exception when running
./gradlew pitest
:Here's the full stacktrace