-
Notifications
You must be signed in to change notification settings - Fork 35
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
Using cargo mutagen in CI pipeline #188
Comments
Hi, what are your requirements for |
I meant a similar thing like the 2nd point of this issue Given this said, my posted issue is duplicated as it is a part of the abovementioned issue, so we can close this if you feel so too. |
Is this something like a |
What I meant is having different exit codes for the This pit for java seems to be related to the target files, but to be honest I never really used this tool within the java ecosystem.... |
So |
The existence of equivalent mutations makes killing all mutations infeasible. Other mutation testing tools (and also coverage tools) typically use ratio-based thresholds. |
@llogiq yes, exactly. If the ratio-based threshold is not reached, then we could return an error code, so the CI pipeline can be stopped. |
Hey!
I wonder what the options are to use mutagen in CI pipelines. I could not find any support about it such as GitHub actions or so.
The simplest I could do is to run
cargo mutagen
in a CI pipeline task and based on the result I could stop or continue the pipeline run. What would be the easiest way to achieve this, what do you think?Of course, I am also up to create/submit a PR and change the code regarding, if there is not yet a solution for it.
Thank you!
The text was updated successfully, but these errors were encountered: