Skip to content

QA-CS-101 — Skipped test ​

← Back to the rule catalog

Generated from the rule registry. Get the same detail from the CLI with mjolnir explain QA-CS-101.

FieldValue
Severitywarning
Confidencehigh
Tierextended
Measured FP rate0% (n=20)
Evidence levelE2
QA impactFalse-green risk (FALSE-GREEN)
False-positive risk (author estimate)low
Autofix availableno
Languagescsharp
Frameworksnunit, xunit, mstest
Detection strategyLEXICAL
Introduced inv0.3.8

Why this fails in production ​

Skipped tests hide broken or unimplemented behavior behind a green build.

What gets flagged (real detector output) ​

Skipped test detected: `[Ignore]`.

Example from this rule's own must-fire fixture: tests/fixtures/QA-CS-101/must-fire/LoginTests.cs

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-CS-101/must-not-fire/LoginTests.cs — 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
microsoft-playwright-dotnet139
SeleniumHQ-selenium26

Released under the MIT License.