QA-PW-117 — describe.serial without justification
Generated from the rule registry. Get the same detail from the CLI with
mjolnir explain QA-PW-117.
| Field | Value |
|---|---|
| Severity | warning |
| Confidence | high |
| Tier | core |
| Measured FP rate | 0% (n=35) |
| 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 |
| Introduced in | v0.3.0 |
Why this fails in production
Serial mode turns any single failure into a cascade for everything after it — it should be an explicit, documented trade-off.
What gets flagged (real detector output)
`test.describe.serial` without a justification comment.Example from this rule's own must-fire fixture: tests/fixtures/QA-PW-117/must-fire/serial.spec.ts
The fix
Add a comment explaining why order matters, or refactor tests to be independent.
Confirmed NOT to fire on the corresponding clean pattern
Verified against tests/fixtures/QA-PW-117/must-not-fire/justified.spec.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 |
|---|---|
| keycloak-keycloak | 98 |
| positive-fixtures | 4 |
| sveltejs-kit | 1 |