Skip to content

QA-CI-005 — Report consumed but never generated ​

← Back to the rule catalog

Generated from the rule registry. Get the same detail from the CLI with mjolnir explain QA-CI-005.

FieldValue
Severityerror
Confidencehigh
Tierquarantine
Measured FP rate8% (n=13)
Evidence levelE2
QA impactBlocks release confidence (BLOCKS-RELEASE)
False-positive risk (author estimate)low
Autofix availableno
Languagesyaml
Frameworksgithub-actions
Detection strategyLEXICAL
Introduced inv0.1.0

Why this fails in production ​

Some report-processing steps (coverage upload, JUnit summary annotation, artifact publishing) read a file the test run was supposed to generate. If the test step crashed before ever writing that file — a config error, an OOM, a timeout that killed the process — the report step can still run and, depending on the tool, either silently no-op or report "0 tests found" without failing the job. The workflow ends green with a report that quietly represents nothing.

What gets flagged (real detector output) ​

Job `test` consumes a coverage artifact that no step generates.

Example from this rule's own must-fire fixture: tests/fixtures/QA-CI-005/must-fire/no-coverage.yml

The fix ​

Add a step that runs tests with --coverage (or generate the report) before this consumption step.

Confirmed NOT to fire on the corresponding clean pattern ​

Verified against tests/fixtures/QA-CI-005/must-not-fire/with-coverage.yml — 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
apache-airflow8
nextauthjs-next-auth2
positive-fixtures22
streamlit-streamlit2

Released under the MIT License.