Skip to content

QA-PW-144 — Single-browser project matrix ​

← Back to the rule catalog

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

FieldValue
Severityinfo
Confidencehigh
Tierextended
Measured FP rate14% (n=21)
Evidence levelE2
QA impactTest hygiene debt (HYGIENE)
False-positive risk (author estimate)low
Autofix availableno
Languagestypescript, javascript
Frameworksplaywright
Detection strategyLEXICAL (regex heuristic)
Introduced inv0.3.8

Why this fails in production ​

Engine-specific breakage (CSS features, date inputs, download behavior) only shows up outside chromium; a single-engine matrix ships it to users undetected.

What gets flagged (real detector output) ​

Projects cover only chromium engine — no cross-browser matrix.

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

The fix ​

Add at least one webkit/firefox project (or ...devices['Desktop Safari']) to the projects array.

Confirmed NOT to fire on the corresponding clean pattern ​

Verified against tests/fixtures/QA-PW-144/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
appsmithorg-appsmith1
calcom-cal1
dubinc-dub1
grafana-grafana1
microsoft-playwright-mcp1
nextauthjs-next-auth1
positive-fixtures13
vercel-next-js1
vitest-dev-vitest1
withastro-astro2

Released under the MIT License.