> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testsprite.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Coverage Map
> The Test Coverage view: see what's covered at a glance, edit use cases directly on the map, and review coverage gaps before a release.
## Overview
Test Coverage is the project's visual map: your product's features, the use cases under each feature, and the test cases attached to each use case. Every node is colored by its latest results, so you can see what's covered, what's passing, and where the gaps are.
Open it from the project's left nav, where it's the first item under **Workspace**.
## Reading the Map
The map flows left to right: **Project → Feature → Use Case → Test Cases**. Each use-case node aggregates the results of the tests under it:
```mermaid theme={null}
flowchart LR
P[Project] --> F[Feature
a capability of your product]
F --> U[Use Case
colored by the tests under it]
U --> T1[Test Case
passed]
U --> T2[Test Case
failed]
U --> T3[Test Case
never run]
```
| Color | Meaning |
| :- | :- |
| 🟢 Green | Every test under this use case passed |
| 🔴 Red | At least one test genuinely failed |
| 🟡 Amber | Blocked or mixed: some tests pending, blocked, or never run alongside passing ones |
| 🔵 Blue | Tests are running right now; the edges into a running node light up too, so you can trace the live path |
| ⚪ Gray | Never run yet |
While you're editing, nodes also carry session tags: **New** (added this session), **Modified** (edited this session), and **Draft** (a hand-added test case not yet saved).
### Dependency arrows
Arrows between use cases show **logical prerequisites** ("checkout depends on product search"), identified when the plan was generated. They drive the left-to-right layout. They do **not** sequence test execution: runs you launch from the map execute as a normal batch.
## Editing Directly on the Map
The map is editable inline; there's no separate edit mode:
* **Add a feature**: hover the project root node and click +.
* **Add a use case**: hover a feature node and click +, or click the trailing + on an existing use case to add one that depends on it.
* **Rename or edit a description**: click a node and edit in the detail panel on the right.
* **Delete a feature or use case**: from the same detail panel.
* **Add a test case under a use case**: the + next to "Test cases" in the detail panel, or the ✨ sparkle on a feature to have AI propose more tests for just that feature.
Edits are **staged**: a floating Save / Discard bar appears as soon as you change anything, and Cmd/Ctrl+Z undoes step by step. Nothing touches the plan until you save.
### What Save does
* **New use cases** get tests generated for them.
* **Deleted use cases** take their now-orphaned tests with them. The review dialog lists exactly what would be removed before you confirm.
* **Renames and description edits** save in one click and do *not* regenerate existing tests.
Editing pauses (with a tooltip explaining why) while tests are generating or running, and the map is read-only when you're viewing a past plan version. You can also export the whole map as a PNG.
## Workflow: Coverage-Gap Review Before a Release
Walk the feature list top to bottom against the release's requirements.
Gray means it exists but has never run. Missing means the feature or flow isn't on the map at all: add it inline with + and let Save generate its tests.
A red node on a release-critical flow is a blocker. Amber usually means an environment or auth issue to clear before you trust the run.
Run the new tests and re-check the map. The goal is a green (or consciously accepted) path for every requirement.
## Where to Go Next
Edit the tests behind each node, singly or in bulk
Let AI improve a test that isn't checking the right thing
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.