Orphan Detection Tab
The Orphan Detection Tab of the Coverage screen.
This tab is the gap list — “Find unlinked items that may need attention.” It has three sections, each with a count badge (colored when non-zero) and an all-clear empty state when there is nothing to fix.
Orphan test cases
Section titled “Orphan test cases”Test cases not linked to any requirement. Columns: Title (with mono id), Type (colored badge), Priority badge, Created date. Empty state: “No orphan test cases — All test cases are linked to requirements.”
Requirements without coverage
Section titled “Requirements without coverage”This section merges two related problems in one table:
| Status pill | Meaning |
|---|---|
| Not Mapped (amber) | A test file found in the project directory that no test case claims. Columns: Script Path, File Name, Framework, Status. |
| Orphaned (red) | A previously-mapped script whose test case no longer exists — a broken link. Shown on a faint red row tint. |
Empty state (only when both lists are empty): “No unmapped scripts — All test scripts in the project are mapped to test cases.”
Orphan sources
Section titled “Orphan sources”Sources with no generated or manually-linked test cases. Columns: Title, Type (with an emoji label: Requirement, NLP, JIRA, or Document), Created. Empty state: “No orphan sources — All sources have been used for test generation.”
Related
Section titled “Related”- Coverage overview — the screen and its tabs.