Update QA & Nightly Checks - Non Major

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.pitest:pitest (source)	1.15.0 -> 1.17.3
info.solidsoft.gradle.pitest:gradle-pitest-plugin (source)	1.9.11 -> 1.15.0

---

Release Notes

hcoles/pitest (org.pitest:pitest)

v1.17.3

Compare Source

v1.17.2

Compare Source

• #​1362 Exclude lambdas in methods excluded by annotation (thanks @​see-quick)

v1.17.1

Compare Source

• #​1353 Warn about future SCM goal removal
• #​1355 Upgrade ASM for java 24 support
• #​1359 Remove use of reflection based toString generator
• #​1361 Initial support for cross module tests in maven

v1.17.0

Compare Source

• #​1348 Extend transformation extension point
• #​1349 Improve powermock stability

v1.16.3

Compare Source

• #​1345 Improved delayed execution detection in static initialization code
• #​1347 Auto add standard kotlin source dirs for maven projects

v1.16.2

Compare Source

#​1340 Show covering tests for surviving mutants in html report (thanks @​vivganes)
#​1342 / #​1343 Fix misleading logging of history paths (thanks @​vivganes)
#​1344 Mutate delayed execution code in enums and singletons

v1.16.1

Compare Source

#​1329 Prevent version clashes with aggregate goal when plugins use jackson

v1.16.0

Compare Source

• #​1311 - Include unmodifiable collections stored directly to fields in the +funmodifiablecollection filter for defensive code
• #​1319 - Use environment variables from surefire config
• #​1322 - Automatically add -ea to enable assertions
• #​1321 - Expand BuildVerifier interface

Api change in #​1321 is backwards compatible, but plugins written against 1.16.0 may not work with earlier versions.

v1.15.8

Compare Source

#​1310 Filter mutations to Collections.unmodifiable*
#​1309 Replace fields in argLines imported from surefire config
#​1308 Bump maven vcs versions

The filtering for #​1310 is off by default. To activate it add the filter string +funmodifiablecollection.

#​1309 adds a new maven property parseSurefireArgLine. This is set to true by default, but surefire argline parsing can now be disabled by setting it to false.

v1.15.7

Compare Source

#​1305 Coverage not recorded for code in packages name com.sun*

A filter intended to pickup legacy JDK classes in the "com.sun.*" package was missing a ', resulting in no code coverage being registered if the code under test happened to be in a package starting with "sun".

v1.15.6

Compare Source

• #​1295 temporarily remove dynamic call tracking

Invoke dynamic call tracking for static initializer code will be reintroduced when additional logic to suppress mutation filtering for delayed execution code has been implemented.

v1.15.5

Compare Source

• #​1292 Args lines taken from surefire config do not have properties replaced

v1.15.4

Compare Source

• #​1288 - New extension point to allow custom coverage export formats
• #​1289 - Parse argline configuration from surefire configuration
• #​1274 Follow invoke dynamic calls when detecting static initializer only methods

Note, maven users who have previously needed to duplicate argline parameters between surefire and pitest's jvmArgs and argline parameters may need to adjust their configuration when upgrading. Entries supplied to surefire will now automatically be added to pitest.

v1.15.3

Compare Source

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

v1.15.2

Compare Source

• #​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.

v1.15.1

Compare Source

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

szpak/gradle-pitest-plugin (info.solidsoft.gradle.pitest:gradle-pitest-plugin)

v1.15.0

• Automatically add junit-platform-launcher dependency to testRuntimeOnly for JUnit Platform projects - #​337 - help from Björn Kautler
• Remove deprecated Project.getConvention() usage (in Gradle 8.2+) - #​343
• PIT 1.15.0 by default
• Basic regression testing with Gradle up to 8.3

Compatibility notes
Starting with PIT 1.14.0 (with pitest-junit-plugin 1.2.0+) junit-platform-launcher is no longer shaded and has to be explicitly added to avoid:
"Minion exited abnormally due to UNKNOWN_ERROR" or "NoClassDefFoundError: org.junit.platform.launcher.core.LauncherFactory".

As an experimental (incubating) feature, junit-platform-launcher is automatically added to the testRuntimeOnly configuration for the JUnit Platform projects.

PLEASE NOTE. This feature is experimental and might not work as expected in some corner cases. In that situation, just disable it with addJUnitPlatformLauncher = false and add the required dependency 'junit-platform-launcher' in a proper version to 'testRuntimeOnly' manually. More information: https://github.com/szpak/gradle-pitest-plugin/issues/337

---

Configuration

📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, Automerge - "after 8am and before 11am every first day of month" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[emily-whitley]

https://tools.hmcts.net/jira/browse/RWA-3725