Skip to content

QA-PW-122 — No trace capture on retry ​

← Back to the rule catalog

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

FieldValue
Severitywarning
Confidencehigh
Tierextended
Measured FP rate6% (n=80)
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 ​

A test that fails once and passes on retry is exactly the case you'll need evidence for later — with no trace, the flake is uninvestigable.

What gets flagged (real detector output) ​

playwright.config has no `trace` capture setting.

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

The fix ​

Add use: { trace: 'on-first-retry' } to the config.

Confirmed NOT to fire on the corresponding clean pattern ​

Verified against tests/fixtures/QA-PW-122/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
microsoft-playwright-dotnet1
microsoft-playwright-mcp1
negative-fixtures60
nextauthjs-next-auth2
positive-fixtures62
sveltejs-kit25
vercel-next-js2
vitest-dev-vitest1
withastro-astro2

Released under the MIT License.