Skip to content

add a flag to have unleash return a nonzero value on failure #216

@toejough

Description

@toejough

🚀 Feature Request

Is your feature request related to a problem? Please describe

I would like to be able to use this tool in a series of checks and stop if anything is NOT COVERED or LIVED.

Describe the solution you'd like

Have gremlins unleash --fail-not-covered --fail-lived return 1 if anything is NOT COVERED or LIVED, and similar for other states.

Describe alternatives you've considered

I could pipe this into a script that searches for text, but that's fragile and prevents the nice colored report from being printed, unless I also want to build my own pattern-matching & colorizing, which I do not. Or I could run the program twice, once for the nice human output and once into the script to scan for & react to the result, which I also don't want to do.

Additional context

I tried setting the --threshold-efficacy=1.0 and --threshold-mcover=1.0 (and up to 100.0) but at Test efficacy: 85.71%
Mutator coverage: 46.67%, the RC was still 0. Am I missing something?

Metadata

Metadata

Assignees

Labels

t/to-triageA new issue or PR not yet triaged (needs to be categorised, prioritised etc.)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions