1.15.3

• #1271 - Double check thread status before marking minion as dead

1.15.2

• #1268 - Filter Lombok NonNull checks
• #1267 - Expand test api to allow reporting of errors during test scanning

#1267 will ensure that previously hidden errors encountered by the JUnit5 plugin will now be reported. This is a backwards compatible api change. It will have no effect until the JUnit5 plugin is updated to use the expanded api. The updated plugin will not be compatible with earlier versions of pitest.

1.15.1

• #1260 Upgrade to ASM 9.6 for Java 22 support
• #1261 Do not error on pitest history files < 1.15.0

1.15.0

• #1253 suppress coverage stats when history test reduction enabled
• #1252 add extrafeatures param for maven to allow features to be added on commandline without overwriting existing list
• #1251 expand history interfaces (breaking change)
• #1250 improve error message when failing to parse feature strings
• #1248 performance tweak - delay test class identification
• #1247 legacy code removal

#1251 updates several existing interfaces. Plugins (eg the arcmutate kotlin plugin) using these interfaces must also be updated when upgrading.

1.14.4

• #1246 Priotitise previous killing test when using history files

1.14.3

• #1239 Support comma seperated excludedGroups (thanks @johnathana)
• #1243 Explictly order classpath in history file to ensure consitency between runs
• #1245 Prevent confusing logging of dummy incremental analysis runs

1.14.2

#1221 - Unified percentage calculate (thanks @Vampire)
#1218 - Thread safety for results collection when tests run in parallel (thanks @Vampire)
#1225 - Prevent error when non archive files included on classpath
#1229 - Mutate Iterables to emptyList
#1227/1232 - Fix MethodMutator interface to depend on abstract types

1.14.1

• #1215 Apply coverage rewrites when aggregating reports
• #1219 Ensure try with resources filtering applied first (thanks @Vampire)

1.14.0

• #1213 Filter equivalent divide by -1 maths mutants
• #1212 Auto add junit-platform-launcher

#1212 Largely resolves the issue of keeping the pitest-junit5-plugin version in sync with the junit5 version for maven users.

When used with 1.2.0 of the pitest-junit5-plugin, pitest will now automatically select a version of junit-platform-launcher which is compatible with the version of junit5 used by the system under test.

Issues remain for gradle users who may still encounter api compatibilities when using 1.2.0 of the pitest-junit5-plugin. These can however now be resolved by manually adding the correct version of junit-platform-launcher to the classpath.

It is hoped that a future version of the pitest gradle plugin will implement a fix similar to the pitest-maven solution.

1.13.2

• #638 Ensure % shows as 100 when all mutants killed (thanks @Vampire)
• #1197 Show start up info when logging set to VERBOSE_NO_SPINNER (thanks @Vampire)
• #1198 Logging improvements (thanks @Vampire)
• #1200 Warn if parallel test execution enabled during coverage collection (thanks @Vampire)
• #1199 Switch to System.nanoTime for test timings (thanks @Vampire)
• #1207 Support for removal of class level annotations