coverage-matrix.json is what coverage-matrix writes, in the inner view, over the repository's
doc-source.json and
ui-tests.json:
- three entities,
US-001,FUNC-001andFUNC-002, in that order; US-001: three plain rows, two covered and one not, 66.7;FUNC-001:FUNC-001-01covered over its three aspects, one scenario each;FUNC-001-02not covered;FUNC-001-03, keywordrule, partially covered, 1/3; 44.4;FUNC-002has no counted criterion and no percentage;- six counted criteria at the root, three covered, one partially covered and two not covered, 55.6;
- two planned criteria, one for
1.1.0and one in the backlog; - the documentation input's two warnings, forwarded.
test_service.py masks only metadata.generated_at in its comparison, and compares the release view with it too,
which differs only in document.view. To refresh the golden after an intended change, run coverage-matrix over
that fixture pair with no GITHUB_* variable set, compare every other field, and review the output's own stats and
warnings before replacing the file.