report

Documentation

Overview

Command gen turns `go test -json` output into the use-case coverage report: a per-scenario JSON + Markdown file and an aggregate matrix. It deliberately reuses harness.Registry as the source of truth for rows, so "pending" (a use case with no test yet) is distinguishable from "skipped" (a test that ran but the scenario didn't satisfy its capabilities) — the distinction the plan promised, without a real code-coverage engine.

go test -tags=integration -json ./suite/... | \
  go run ./report -scenario single-node -out reports

On spot reclaim the run is inconclusive, not failed:

go run ./report -scenario cluster-hetero -inconclusive -out reports