-
Notifications
You must be signed in to change notification settings - Fork 16
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
Gradle plugin run mutates a test class #56
Comments
This was referenced Nov 22, 2022
I have the very same issue. Though I understand that it works when you run ./gradlew pitest as gradle-pitest-plugin has a default value for testSourceSets of sourceSets.test. Now is it possible to have the same for pit-idea-plugin? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am still trying to understand what is the expected behavior of the PIT and how all of the pieces are connected.
In my kotlin-mutation-testing project I am experiencing strange behaviour:
When I run tests using the cmd
./gradlew pitest
then Pit Test Coverage Report shows a single class being found (ApplicationService.kt
)(ok)However, when I run pitest using gradle-pitest-plugin (Pit Runner) the Pit Test Coverage Report contains two classes (
ApplicationService.kt
- ok andApplicationServiceTest.kt
- not ok)The text was updated successfully, but these errors were encountered: