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
I would like to be able to set a fail criteria based on the baseline mutation score. Basically I would like to incentivize our developers to write better unit tests by ensuring any new changes to code has better unit test coverage by ensuring the new tests end up with a better mutation score than the baseline.
Required behavior:
Set the baseline mutation score as the "break" criteria (Anything lower than baseline will break).
Do not create a new baseline if the run "breaks" due to the score being worse.
If mutation score is better continue as usual
This way our CI/CD pipelines will automatically be able stop any new (and potentially untested) code from being merged into a release.
The text was updated successfully, but these errors were encountered:
I would like to be able to set a fail criteria based on the baseline mutation score. Basically I would like to incentivize our developers to write better unit tests by ensuring any new changes to code has better unit test coverage by ensuring the new tests end up with a better mutation score than the baseline.
Required behavior:
This way our CI/CD pipelines will automatically be able stop any new (and potentially untested) code from being merged into a release.
The text was updated successfully, but these errors were encountered: