Just to give you a heads up of a few other issues you are likely to
encounter.
1) Mutation testing does not scale well. Analysis times will increase
sharply as the size of your code base increases.
For the moment the best way to deal with this is to reduce the scope of
the analysis using one or all of the following.
a) Target only specific portions of your codebase (using the class
filters)
b) Limit the mutation operators used
c) Limit the number of mutations per class
Tweaking the number of threads used may also help.
2) Equivalent mutants. In my experience using PIT the prevalence of
these has been greatly over stated in the academic literature. I'm not
sure if this is is due to PIT's mutation operators (which are designed
to try and reduce the number of equivalent mutations generated), or I've
just been lucky with the code bases I've mutated. You will definitely
encounter some however.
3) Issue 24 - http://code.google.com/p/pitestrunner/issues/detail?id=24
As PIT is developed we'll be looking to make improvements in all of
these areas.
Cheers
Henry
[ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.1:sonar (default-cli) on project see: Can not execute SonarQube analysis: Unable to execute Sonar: Parameter 'directory' is not a directory -> [Help 1]
[ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Can not execute Sonar Embedded error: fail All tests did not pass without mutation when calculating line coverage. Mutation testing requires a green suite. See http://pitest.org for more details.
Sometimes we have not-green suite but we:1) don't want to avoid Sonar analyzing of the project - the most critical...2) in the ideal case it would be cool to have it possible pitest plugin itself working in not-a-green-suite (so only for green tests probably).
--
You received this message because you are subscribed to the Google Groups "PIT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pitusers+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "PIT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pitusers+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hello
Have you tried version 0.4 . It should fix the issue you have encountered.
Regards
Alex
We are facing resource crunch issue in the continous integration pipe after configuring pitest. Pitest build is running for a longer duration (almost 16hrs) and other builds are getting slow due to lack of resource.Is there any possible solutions available to make the pitest build faster.