From 64dc318e5932157508e93b4deeeac8c7fa4316cc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20St=C3=BChmer?= Date: Thu, 29 Oct 2026 05:01:33 +0100 Subject: [PATCH] ci(stryker): align mutation score thresholds with measured baseline The thresholds were high 90 / low 80 / break 0, while the scheduled run (stryker-config.json, Roslyn5_6 project) scores about 60 percent. With break 0 the run can never fail, even on a collapse of the score, and the dashboard badge is permanently red. Set high 75 / low 60 / break 55: break sits a few points below the measured score to absorb run-to-run variance (compile errors, flaky coverage), so a real regression fails the run. Only the config used by the scheduled run is changed; the roslyn4_4, roslyn4_14 and roslyn5_6 variants are manual-dispatch only and have no measured baseline. --- stryker-config.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/stryker-config.json b/stryker-config.json index 036dc0e..fc77069 100644 --- a/stryker-config.json +++ b/stryker-config.json @@ -10,9 +10,9 @@ "mutation-level": "Complete", "reporters": ["dashboard", "html", "progress", "cleartext"], "thresholds": { - "high": 90, - "low": 80, - "break": 0 + "high": 75, + "low": 60, + "break": 55 }, "project-info": { "name": "github.com/dailydevops/analyzer",