QA-PW-104 — trial:true click without follow-up assertion
Generated from the rule registry. Get the same detail from the CLI with
mjolnir explain QA-PW-104.
| Field | Value |
|---|---|
| Severity | warning |
| Confidence | medium |
| Tier | extended |
| Measured FP rate | 0% (n=10) |
| Evidence level | E1 |
| QA impact | False-green risk (FALSE-GREEN) |
| False-positive risk (author estimate) | medium |
| Autofix available | no |
| Languages | typescript, javascript |
| Frameworks | playwright |
| Detection strategy | LEXICAL |
| Introduced in | v0.3.0 |
Why this fails in production
Trial clicks only check actionability; any test logic assuming the click happened is verifying nothing while staying green.
What gets flagged (real detector output)
`click({ trial: true })` — a dry-run that clicks nothing.Example from this rule's own must-fire fixture: tests/fixtures/QA-PW-104/must-fire/trial-click.spec.ts
The fix
Use a real click() and assert the resulting state, or keep trial only as an explicit actionability probe with a comment.
Confirmed NOT to fire on the corresponding clean pattern
Verified against tests/fixtures/QA-PW-104/must-not-fire/real-click.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 |
|---|---|
| positive-fixtures | 10 |