reqcov — live example reports

These are the actual reports reqcov 0.2.0 produced for the three example projects in the repository, regenerated on every push to main. Nothing to install: open one and use the filters, exactly as your team would after a pull request.

What reqcov does

reqcov is an open-source requirements traceability tool for CI. It reads requirements written in Markdown, YAML or Doorstop, finds the tests and source files that reference them, reads the JUnit XML results, and produces a traceability matrix: which requirement is covered, by which test, and whether that test passes. It runs as a CLI or as a GitHub Action and can fail the build on gaps — the kind of evidence DO-178C, ISO 26262 and IEC 62304 audits ask for.

Two of these examples fail on purpose — a requirement without a test, a test that fails — because that is what the tool is for. A green report proves nothing until you have seen it go red.

Python · pytest

examples/pytest-project

A thermostat with SYS → SRS levels, one requirement deliberately left without a test and one orphan test.

Requirements
8
Test coverage
83.3%
Uncovered
1
Failing
0

Same run, other formats: matrix.csv · coverage.json · summary.md (the pull-request comment)

C · Ceedling / Unity

examples/ceedling-unity

An embedded frame decoder with HLR → LLR levels, @implements markers in the sources and a failing Unity test propagating to its requirements.

Requirements
6
Test coverage
100.0%
Uncovered
0
Failing
2

Same run, other formats: matrix.csv · coverage.json · summary.md (the pull-request comment)

C++ · GoogleTest

examples/googletest

A ring buffer with one-line requirements and GoogleTest Suite.Name results.

Requirements
4
Test coverage
100.0%
Uncovered
0
Failing
0

Same run, other formats: matrix.csv · coverage.json · summary.md (the pull-request comment)