coverage-report

name	coverage-report
description	How to run coverage tooling per language and interpret results against thresholds. Used by .NET Test Reviewer and React Test Reviewer. Use when this capability is needed.
metadata	{"author":"ecogs-sys"}

Coverage Report

.NET coverage

Run

dotnet test --collect:"XPlat Code Coverage" --results-directory coverage/

Generate readable summary

Install reportgenerator into a local tool path (coverage/.tools) — do NOT install globally with -g, that pollutes the user's machine.

dotnet tool install dotnet-reportgenerator-globaltool --tool-path coverage/.tools 2>/dev/null || true
coverage/.tools/reportgenerator \
  -reports:"coverage/**/coverage.cobertura.xml" \
  -targetdir:"coverage/report" \
  -reporttypes:"TextSummary"
cat coverage/report/Summary.txt

Reading the output

Line coverage: 85.3% (227 of 266)
Branch coverage: 72.1%

Thresholds

Default: 80% line coverage, 90% on critical paths. Per-story override: check story's coverage_threshold field.

React coverage

Run

npm test -- --run --coverage

Output (Vitest + v8)

----------|---------|----------|---------|---------|
File      | % Stmts | % Branch | % Funcs | % Lines |
----------|---------|----------|---------|---------|
All files |   85.00 |    72.00 |   88.00 |   85.00 |

Thresholds

Default: 80% statement coverage, 90% on critical paths.

Decision tree

All tests pass?
  No  → Are tests correct?
        Yes → BACK_TO_ENGINEER (production bug)
        No  → BACK_TO_TEST_ENGINEER (test bug)
  Yes → Coverage ≥ threshold?
        Yes → DONE
        No  → BACK_TO_TEST_ENGINEER (add tests for uncovered paths)

---

Source: ecogs-sys/Agentic.SDLC — distributed by TomeVault.