Skip to content

QA-JV-102 — Hard sleep in test ​

← Back to the rule catalog

Generated from the rule registry. Get the same detail from the CLI with mjolnir explain QA-JV-102.

FieldValue
Severitywarning
Confidencehigh
Tierextended
Measured FP rate26% (n=23)
Evidence levelE2
QA impactFlaky-test risk (FLAKY-RISK)
False-positive risk (author estimate)low
Autofix availableno
Languagesjava
Frameworksjunit, testng
Detection strategyLEXICAL
Introduced inv0.3.8

Why this fails in production ​

Fixed sleeps are flaky under load and slow everywhere; Playwright locators auto-wait for actionability.

What gets flagged (real detector output) ​

`Thread.sleep()` used to wait for state.

Example from this rule's own must-fire fixture: tests/fixtures/QA-JV-102/must-fire/DashboardTest.java

The fix ​

Wait on a condition: page.locator(...).waitFor(), assertThat(locator).isVisible().

Confirmed NOT to fire on the corresponding clean pattern ​

Verified against tests/fixtures/QA-JV-102/must-not-fire/DashboardTest.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):

RepoOccurrences
appsmithorg-appsmith10
iluwatar-java-design-patterns18
junit-team-junit535
keycloak-keycloak30
microsoft-playwright-java1
positive-fixtures5
SeleniumHQ-selenium28

Released under the MIT License.