coverage-map

You can visualize test coverage gaps by reading existing test plan markdown files and pipeline-state.json artefacts to summarize which stories have automated, manual, or no coverage. This approach flags high-risk gaps for planning without running any tests.

Coverage reporting from artefacts reads test plans and pipeline state data to determine what is intended to be tested and by what method, whereas running tests executes code to verify pass or fail outcomes. The reporting approach surfaces coverage gaps for risk assessment.

Yes, you can generate per-story and per-AC coverage reports by reading existing test plan artefacts. The reports compute coverage status across Unit, Integration, E2E, and Manual test types, highlighting stories without test plans.

Yes, pipeline-state.json artefacts are required alongside test plan markdown files to compute coverage. The coverage map reads these existing artefacts to surface per-story coverage status and risk scoring without executing tests.

You can assess risk by applying the coverage map to features with test plans and pipeline state data. It produces a per-story rollup with risk scoring and gap types, flagging stories with manual or no coverage as high-risk gaps for humans to action.