QA-PY-002 — Skipped test
Generated from the rule registry. Get the same detail from the CLI with
mjolnir explain QA-PY-002.
| Field | Value |
|---|---|
| Severity | warning |
| Confidence | high |
| Tier | extended |
| Measured FP rate | 12% (n=25) |
| Evidence level | E2 |
| QA impact | False-green risk (FALSE-GREEN) |
| False-positive risk (author estimate) | low |
| Autofix available | no |
| Languages | python |
| Frameworks | pytest |
| Detection strategy | LEXICAL |
| Introduced in | v0.3.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 detected: `@pytest.mark.skip`.Example from this rule's own must-fire fixture: tests/fixtures/QA-PY-002/must-fire/skipped.py
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-PY-002/must-not-fire/clean.py — 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 | 13 |
| getsentry-sentry | 153 |
| pallets-click | 1 |
| psf-requests | 2 |
| pytest-dev-pytest | 19 |
| reflex-dev-reflex | 3 |
| streamlit-streamlit | 5 |