QA-JV-101 — Disabled test
Generated from the rule registry. Get the same detail from the CLI with
mjolnir explain QA-JV-101.
| Field | Value |
|---|---|
| Severity | warning |
| Confidence | high |
| Tier | core |
| Measured FP rate | 0% (n=35) |
| Evidence level | E2 |
| QA impact | False-green risk (FALSE-GREEN) |
| False-positive risk (author estimate) | low |
| Autofix available | no |
| Languages | java |
| Frameworks | junit, testng |
| Detection strategy | LEXICAL |
| Introduced in | v0.3.8 |
Why this fails in production
Disabled tests hide broken or unimplemented behavior behind a green build.
What gets flagged (real detector output)
Disabled test detected: `@Disabled`.Example from this rule's own must-fire fixture: tests/fixtures/QA-JV-101/must-fire/LoginTest.java
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-JV-101/must-not-fire/LoginTest.java — 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 |
|---|---|
| appsmithorg-appsmith | 11 |
| iluwatar-java-design-patterns | 2 |
| junit-team-junit5 | 77 |
| keycloak-keycloak | 69 |
| microsoft-playwright-java | 8 |
| positive-fixtures | 3 |
| SeleniumHQ-selenium | 316 |