Skip to content

QA-CS-109 — Retry masks test failures ​

← Back to the rule catalog

Generated from the rule registry. Get the same detail from the CLI with mjolnir explain QA-CS-109.

FieldValue
Severitywarning
Confidencemedium
Tierextended
Measured FP rate0% (n=10)
Evidence levelE1
QA impactFlaky-test risk (FLAKY-RISK)
False-positive risk (author estimate)medium
Autofix availableno
Languagescsharp
Frameworksnunit, xunit, mstest
Detection strategyLEXICAL
Introduced inv0.4.0

Why this fails in production ​

Retrying until a test passes hides intermittent failures — the reported result no longer reflects whether the suite is actually reliable.

What gets flagged (real detector output) ​

NUnit `[Retry(3)]` automatically re-runs a failing test.

Example from this rule's own must-fire fixture: tests/fixtures/QA-CS-109/must-fire/FlakyTests.cs

The fix ​

Remove the [Retry] attribute; fix the flake root cause, or quarantine the test explicitly.

Confirmed NOT to fire on the corresponding clean pattern ​

Verified against tests/fixtures/QA-CS-109/must-not-fire/FlakyTests.cs — a legitimate, similar-looking pattern this rule correctly leaves alone.

Corpus-measured false-positive risk ​

Real occurrence counts from npm run corpus:audit against actively-maintained OSS repos — reproduce yourself, don't just trust this table (see the false-positive audit):

RepoOccurrences
positive-fixtures6

Released under the MIT License.