QA-TEST-002 — Skipped test
Generated from the rule registry. Get the same detail from the CLI with
mjolnir explain QA-TEST-002.
| Field | Value |
|---|---|
| Severity | warning |
| Confidence | high |
| Tier | quarantine |
| Measured FP rate | 62% (n=21) |
| Evidence level | E2 |
| QA impact | False-green risk (FALSE-GREEN) |
| False-positive risk (author estimate) | medium |
| Autofix available | no |
| Languages | typescript, javascript |
| Frameworks | jest, vitest, mocha |
| Detection strategy | LEXICAL |
| Introduced in | v0.1.0 |
Why this fails in production
Skipped tests hide broken or unimplemented behavior behind a green checkmark.
What gets flagged (real detector output)
Skipped test without justification: `it.skip(`.Example from this rule's own must-fire fixture: tests/fixtures/QA-TEST-002/must-fire/justified-skip-warning.spec.ts
The fix
Fix and re-enable the test, or delete it with a tracked issue reference.
Confirmed NOT to fire on the corresponding clean pattern
Verified against tests/fixtures/QA-TEST-002/must-not-fire/clean.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 |
|---|---|
| apache-airflow | 1 |
| calcom-cal | 18 |
| cypress-io-cypress-realworld-app | 3 |
| cypress-realworld-app | 3 |
| dubinc-dub | 2 |
| getsentry-sentry | 9 |
| github-docs | 11 |
| grafana-grafana | 45 |
| keycloak-keycloak | 23 |
| nextauthjs-next-auth | 1 |
| positive-fixtures | 1 |
| sveltejs-kit | 38 |
| vercel-next-js | 230 |
| vitejs-vite | 5 |
| vitest-dev-vitest | 23 |
| withastro-astro | 32 |
| yarnpkg-berry | 3 |