You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EasyMock expected that PrometheusScrapeEndpoint.scrape(<any>) will be invoked only once but it was invoked twice.
When I execute maven with -DskipPitest, all tests pass successfully.
The following ZIP contains maven output with verbose=true for
I have created a small project that reproduces the issue. With pitest-junit5-plugin=0.10 the command mvn clean install works fine. With 0.11 and 0.14 the command fails on the basis of a failed test.
Failed to execute goal org.pitest:pitest-maven:1.6.2:mutationCoverage (default) on project pitest-junit5-plugin-issue-59: Execution default of goal org.pitest:pitest-maven:1.6.2:mutationCoverage failed: 1 tests did not pass without mutation when calculating line coverage. Mutation testing requires a green suite.
After upgrading from pitest-junit5-plugin 0.10 to 0.11, a unit test started failing.
The same problem occurs in 0.14 as well.
EasyMock expected that
PrometheusScrapeEndpoint.scrape(<any>)
will be invoked only once but it was invoked twice.When I execute maven with
-DskipPitest
, all tests pass successfully.The following ZIP contains maven output with verbose=true for
mvn.pitest-junit5-plugin-0.10.out - pass
mvn.pitest-junit5-plugin-0.11.out - fail
mvn.pitest-junit5-plugin-0.14.out - fail
mvn-out.zip
pitest-maven = 1.6.2
junit-jupiter-api = 5.7.1
The text was updated successfully, but these errors were encountered: