Repository navigation
ci(stryker): set mutation score break threshold to 60 - #261
Merged
Merged
Conversation
thresholds.break was 0, so the mutation workflow stayed green regardless of the score (74.73% in run 40488203974). Set it to the existing 'low' value (60), about 15 points below the current baseline to absorb score swings caused by failing initial tests. Stryker requires break <= low, which holds.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #261 +/- ##
=======================================
Coverage 89.69% 89.69%
=======================================
Files 31 31
Lines 728 728
Branches 85 85
=======================================
Hits 653 653
Misses 67 67
Partials 8 8 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
stryker-config.jsonhasthresholds: high 80, low 60, break 0. Run 40488203974 (workflow_dispatch) ended withThe final mutation score is 74.73 %and conclusion success, although the initial test run warned about failing tests (up to 30 in some warnings). With break 0 the workflow can never fail on score, so a regression is only visible on the dashboard.Root cause
The break threshold was never set.
Change
thresholds.break: 0 -> 60 (equal tolow; Stryker requiresbreak <= low). The floor is about 15 points below the current 74.73% baseline because that baseline is depressed and noisy (failing initial tests).Before / After
Final mutation score is below threshold break. Crashing..., Stryker step failed, upload step skipped: https://github.com/dailydevops/projectbuilders/actions/runs/40815422940Risk / what this does not change
if: always(), so the HTML artifact is skipped on such a run. The dashboard reporter runs inside Stryker and is unaffected.