You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keeping in sync with new options in PIT is good, but to allow users to manually use new switched before there are available in GPP, there could a property to be set by the user passing the values directly to PIT (e.g. --dry-run). It would be even easier to use for generic parameters which don't require getting values from Gradle build.
Just a rough idea to consider. Please comment, if you were in that situation.
The text was updated successfully, but these errors were encountered:
I think it would be great!
If I understand correctly, this would allow, for example, parameters like --targetClasses or --targetTests to be included in the execution command?
I have an IntelliJ plugin (https://plugins.jetbrains.com/plugin/23649-pitest-helper) to launch PITest analysis on certain classes or packages and I am solving this problem using Gradle project properties to overwrite params, like the Maven plugin. In the plugin's README it is described how: https://github.com/cquilezg/pitest-helper?tab=readme-ov-file#gradle-project
If this functionality is included, it would no longer be necessary.
Keeping in sync with new options in PIT is good, but to allow users to manually use new switched before there are available in GPP, there could a property to be set by the user passing the values directly to PIT (e.g.
--dry-run
). It would be even easier to use for generic parameters which don't require getting values from Gradle build.Just a rough idea to consider. Please comment, if you were in that situation.
The text was updated successfully, but these errors were encountered: