QA-PW-144 — Single-browser project matrix
Generated from the rule registry. Get the same detail from the CLI with
mjolnir explain QA-PW-144.
| Field | Value |
|---|---|
| Severity | info |
| Confidence | high |
| Tier | extended |
| Measured FP rate | 14% (n=21) |
| Evidence level | E2 |
| QA impact | Test hygiene debt (HYGIENE) |
| False-positive risk (author estimate) | low |
| Autofix available | no |
| Languages | typescript, javascript |
| Frameworks | playwright |
| Detection strategy | LEXICAL (regex heuristic) |
| Introduced in | v0.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):
| Repo | Occurrences |
|---|---|
| appsmithorg-appsmith | 1 |
| calcom-cal | 1 |
| dubinc-dub | 1 |
| grafana-grafana | 1 |
| microsoft-playwright-mcp | 1 |
| nextauthjs-next-auth | 1 |
| positive-fixtures | 13 |
| vercel-next-js | 1 |
| vitest-dev-vitest | 1 |
| withastro-astro | 2 |