Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for custom parameters passed to PIT #369

Open
szpak opened this issue Dec 13, 2024 · 1 comment
Open

Support for custom parameters passed to PIT #369

szpak opened this issue Dec 13, 2024 · 1 comment

Comments

@szpak
Copy link
Owner

szpak commented Dec 13, 2024

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.

@cquilezg
Copy link

Hi,

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants