Skip to content

QA-PW-121 — Config retry/worker abuse ​

← Back to the rule catalog

Generated from the rule registry. Get the same detail from the CLI with mjolnir explain QA-PW-121.

FieldValue
Severitywarning
Confidencehigh
Tierextended
Measured FP rate0% (n=12)
Evidence levelE2
QA impactFalse-green risk (FALSE-GREEN)
False-positive risk (author estimate)low
Autofix availableno
Languagestypescript, javascript
Frameworksplaywright
Detection strategyLEXICAL (regex heuristic)
Introduced inv0.3.0

Why this fails in production ​

High retry counts convert real bugs into intermittent passes and inflate CI minutes; the suite reports green while hiding instability.

What gets flagged (real detector output) ​

retries: 4 — a flaky test gets 4 chances to pass by luck.

Example from this rule's own must-fire fixture: tests/fixtures/QA-PW-121/must-fire/playwright.config.ts

The fix ​

Keep retries <= 2 and route repeat offenders into the evidence path (explain --evidence).

Confirmed NOT to fire on the corresponding clean pattern ​

Verified against tests/fixtures/QA-PW-121/must-not-fire/playwright.config.ts — 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-fixtures12

Released under the MIT License.