Test ManagementCoverageTraceability Matrix Tab

Traceability Matrix Tab

The Traceability Matrix Tab of the Coverage screen.

This tab maps the full chain Source Document -> Content Sections -> Test Cases. A view toggle at the top-right switches between Detailed View (document-grouped, the default) and List (one row per requirement).

Traceability Matrix tab in Detailed View: summary cards and one collapsible card per source document with its coverage percentage

Reading the summary cards

Four cards sit above both views:

Traceability summary cards: Requirements, Linked Test Cases, Links and Requirement Coverage with a covered count

Card	Meaning
Requirements	Number of active and draft requirements in the matrix.
Linked Test Cases	Number of distinct test cases linked to at least one requirement.
Links	Total requirement<->test-case links (shown in brand color). A test case linked to two requirements counts twice.
Requirement Coverage	Requirements with at least one linked test case, as a percent of all requirements, with an “N/M covered” line beneath. This is the same population the Coverage Dashboard uses.

Detailed View

Detailed View lists each source document as a collapsible card. The card header shows the source title, the attached file name (when there is one), the count of generated test cases, any manually-linked count (amber), and a coverage percent (requirements of this source that have tests ÷ all its requirements) with a colored progress bar:

Coverage %	Color
80% and above	Green (emerald)
50% to 79%	Amber
Below 50%	Red

Expanding a source card renders the Requirement x Strategy heatmap (the DocumentRequirementMatrix). The expanded card repeats the source title with a summary line (requirements · test cases · generated, plus any manually linked count) and an Export CSV button. Rows are requirements; columns are the test-design strategies that occur in this source’s tests, abbreviated in the header — HP happy-path, NEG negative, BND boundary, EQ equivalence, ERR error-handling, SEC security, PRF performance, A11Y accessibility, CMP compatibility, INT integration, DV data-validation. Hover a column header for the full name.

A source card expanded into the Requirement by Strategy heatmap: search, sort, Uncovered only, priority chips, and rows with Tests, Last Gen and HP and NEG columns

Cell appearance	Meaning
Green checkmark + a number	That requirement has that many test cases for this strategy.
Dim hollow circle	No tests for this strategy on this requirement (a gap).
Last Gen column	Relative time since the requirement’s tests were last generated (e.g. “3h ago”).
Tests column	Total test cases for that requirement row.
Row label	Requirement ID and title, the source quote when it adds to the title, and small per-priority counts (for example `c:2` = two critical tests, `h:1` = one high) plus persona tags.

A legend under the table reads covered, no tests and click a row to expand and see all test cases.

Heatmap controls (above the table): a Search box (matches requirement title, source quote, requirement id, or test-case titles); a sort dropdown (Recently generated / Least covered first / Highest priority first / Most tests first / Fewest tests first); an Uncovered only checkbox (shows only requirements that have at least one strategy with zero tests); Per-persona columns checkbox (adds one column per persona, only offered when the source has persona data); Priority filter chips (critical/high/medium/low — a requirement matches when any of its tests has a selected priority); and Persona filter chips (only when the source has persona data). A “Showing X of Y requirements” line and a Clear filters link (shown while a filter is active) round it out.

Heatmap filtered by the high priority chip, showing 1 of 3 requirements and a Clear filters link

Drill-down. Click any row label (the chevron) to expand it inline. The expansion shows one card per strategy listing every test case (id, title, priority badge, persona badge); each test links to /test-cases?tcId=<id>. A special amber Manually Linked row appears at the bottom when the source has test cases attached by hand from the Requirements tab — those carry no strategy/persona metadata, so their taxonomy columns read “(no taxonomy data)”.

Requirement REQ-2 expanded inline into happy-path and negative strategy cards, each listing its test case with a priority badge

List View

List View flattens everything to one row per requirement with these columns: Requirement (priority badge + title + id), Linked Test Cases (color-coded chips with the ID and a shortened title), Count, Result, and Coverage. A legend at the top decodes the chip colors.

Signal	Color	Meaning
Test-case chip / Passed	Green (emerald)	Latest execution of that test passed (shown with a check).
Test-case chip / Failed	Red	Latest execution failed (shown with an X).
Test-case chip / Not Run	Gray	Never executed (shown with a dot).
Row tint — green	Emerald wash	Requirement is Fully Covered (has tests and all of them are automated).
Row tint — red	Red wash	Requirement has no test cases linked (a hard gap).
Coverage badge	Green / Amber / Red	Fully Covered / Partially Covered / Not Covered.

The Result column rolls the linked tests into one verdict: Failed if any linked test failed, Passed only if every linked test passed (and there is at least one), otherwise Not Run. Coverage measures linking and automation, not results: Not Covered when no tests are linked, Fully Covered when every linked test is automated (mapped to a script or marked automated), and Partially Covered when some linked tests are still manual. Hover a test-case chip to see its ID, full title and latest result.

Coverage overview — the screen and its tabs.