Skip to content

QA-PW-104 — trial:true click without follow-up assertion ​

← Back to the rule catalog

Generated from the rule registry. Get the same detail from the CLI with mjolnir explain QA-PW-104.

FieldValue
Severitywarning
Confidencemedium
Tierextended
Measured FP rate0% (n=10)
Evidence levelE1
QA impactFalse-green risk (FALSE-GREEN)
False-positive risk (author estimate)medium
Autofix availableno
Languagestypescript, javascript
Frameworksplaywright
Detection strategyLEXICAL
Introduced inv0.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):

RepoOccurrences
positive-fixtures10

Released under the MIT License.