[Improve] Make mutation findings advisory - #1610
Conversation
Review statusThis PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging. Current step: Mark the PR ready. Required CI must pass before CodeRabbit starts. Review-state labels are managed by this workflow; do not edit them manually. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
1 participant
What changed
The required
mutation-diffcheck now blocks only when changed executable code exceeds the existing 500-line package limit, or when that scope cannot be calculated safely.Mutation survivors, uncovered mutants, timeout ratios, mutant-count caps, exclusion-policy findings, Stryker execution failures, summary-write failures, and report-upload failures remain visible as warning annotations, job-summary advisories, and downloadable reports without failing required CI.
Why this change was made
Mutation testing should guide test improvements without preventing otherwise healthy pull requests from advancing. Executable-line growth remains the deterministic scope-control gate.
Impact
Authors still receive the full changed-code mutation report and focused warnings, but mutation quality findings no longer withhold a passing required check. Pull requests that exceed the executable-line threshold remain blocked and must reduce scope or receive a narrow maintainer-reviewed exclusion.