-
Notifications
You must be signed in to change notification settings - Fork 58
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
Skip Pitest task execution test when source set is empty #294
Comments
It sounds sensible. Currently the plugin is applied only on subprojects with the Java plugin, but no test source in fact could lead to that behavior. Nevertheless, in a corner case, there could be only some test content attached from some other subprojects (e.g. with the acceptance tests). gradle-pitest-plugin/src/main/groovy/info/solidsoft/gradle/pitest/PitestPlugin.groovy Lines 175 to 182 in c54467b
Do you think that checking if |
Btw, it is slightly related to #292 (in terms of behavior). |
The I was thinking that it should be sufficient to check if |
Yes, Maybe, but source sets were always somehow specific for me and it would have to be verified :-). |
It is of course true that the test classpath can contain the test cases, imported from another project. I'm not sure if that is a sufficiently common case... Using Gradle |
Any plans of when this would be available. So far I have to exclude certain modules from running the pitest task. |
For a regular Gradle
test
task from the Java plugin, if there is no test source, it will just be skipped indicatingNO-SOURCE
. In contrast, Pitest tasks will fail withCoverage generation minion exited abnormally
. I propose that the Pitest tasks should behave similarly as thetest
task. As for backwards compatibility, this would cause e.g. CI builds that are currently failing to pass instead, but I have a hard time seeing that as a problem.The current workaround I use is pretty hard-coded (and deals with configuration caching, hence it looks a little weird):
The text was updated successfully, but these errors were encountered: