search

szpak / gradle-pitest-plugin

Gradle plugin for PIT Mutation Testing
http://gradle-pitest-plugin.solidsoft.info/
212 stars 57 forks source link

Handle testPlugin deprecation (PIT 1.6.7) #277

Closed szpak closed 2 years ago

szpak commented 3 years ago

As of 1.6.7 it is no longer used - support for multiple test engines is provided in PIT and there are automatically detected on a classpath.

The parameter should be deprecated (could be still useful for using with lower PIT versions - e.g. for regression testing reasons) and documentation for JUnit 5 plugin support should be revised.

szpak commented 2 years ago

Postponed to 1.7.1 to do not confuse people with both JUnit Platform 1.8.0 compatibility and (not related) testPlugin deprecation.

szpak commented 2 years ago

Henry kindly reminded about that in #306. The current plan is to release 1.7.1 "soon" and deprecate the testPlugin parameter in the Gradle plugin (to print a warning) and at the same time stop passing it to PIT (to do not generate error with further PIT versions, once it is removed). 1.7.0 will be the minimal required version.

szpak commented 2 years ago

It suddenly came to me that GPP is usually aware which PIT version is used. As a result, we could just pass the parameter if PIT is <1.7.0 (to keep compatibility with the ower PIT versions - although they shouldn't be used anyway).

szpak commented 2 years ago

With just released GPP 1.7.4, --testPlugin should not be send for PIT 1.6.7+.