Skip to content

QA-PW-124 — No smoke/regression project split ​

← Back to the rule catalog

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

FieldValue
Severityinfo
Confidencehigh
Tierextended
Measured FP rate7% (n=15)
Evidence levelE1
QA impactTest hygiene debt (HYGIENE)
False-positive risk (author estimate)low
Autofix availableno
Languagestypescript, javascript
Frameworksplaywright
Detection strategyLEXICAL (regex heuristic over playwright.config.* (adapter-gated))
Introduced inv0.3.0

Why this fails in production ​

Without a fast smoke project, every commit runs the whole suite — PR feedback slows down and people start skipping CI.

What gets flagged (real detector output) ​

Projects defined without a smoke/regression split.

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

The fix ​

Add a smoke project (testIgnore filter on critical paths) alongside the full regression project.

Confirmed NOT to fire on the corresponding clean pattern ​

Verified against tests/fixtures/QA-PW-124/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
github-docs1
grafana-grafana1
hashicorp-vault1
microsoft-playwright-mcp1
negative-fixtures12
nextauthjs-next-auth1
positive-fixtures14
vitest-dev-vitest1

Released under the MIT License.