pfoerd

Missleading 0% TestStrength when no covered mutations were found

1

Hi. TestStrength reports 0% with a red highlighting when the ratio is 0/0 as no covered mutations were found.  This is quite misleading as it indicates there is any...

Tested with Pitest 1.9.3. Project runs on Kotlin 1.6.10 # Issue When setting `exportLineCoverage` to `true` Pitest generates an invalid linecoverage.xml file when there are "special symbols" in test method...

[Android] activityRetainedScope is broken for multiple instances of the same Activity class

1

**Describe the bug** If there are multiple Activities of the same class on the task stacks - e.g. because one started the same Activity multiple times - all of them...

Ability to override `verbose` from command line

1

When analyzing configuration failures of Pitest it's often necessary to temporarily turn on verbose output. Changing the configuration in gradle files is possible but obviously has some drawbacks. This change...

Remove history locations from inputs/outputs

8

The [gradle docs on incremental builds](https://docs.gradle.org/current/userguide/incremental_build.html) say > don’t register properties as inputs if they don’t affect the output As the pitest history file doesn't affect the results of mutation...

Temporary enabling verbose output is very common to analyze issues when executing Pitest. Thus, it would be very useful to have a command line parameter for this like `./gradlew pitest...