Skip to content

QA-TEST-002 — Skipped test ​

← Back to the rule catalog

Generated from the rule registry. Get the same detail from the CLI with mjolnir explain QA-TEST-002.

FieldValue
Severitywarning
Confidencehigh
Tierquarantine
Measured FP rate62% (n=21)
Evidence levelE2
QA impactFalse-green risk (FALSE-GREEN)
False-positive risk (author estimate)medium
Autofix availableno
Languagestypescript, javascript
Frameworksjest, vitest, mocha
Detection strategyLEXICAL
Introduced inv0.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):

RepoOccurrences
apache-airflow1
calcom-cal18
cypress-io-cypress-realworld-app3
cypress-realworld-app3
dubinc-dub2
getsentry-sentry9
github-docs11
grafana-grafana45
keycloak-keycloak23
nextauthjs-next-auth1
positive-fixtures1
sveltejs-kit38
vercel-next-js230
vitejs-vite5
vitest-dev-vitest23
withastro-astro32
yarnpkg-berry3

Released under the MIT License.