Work Item Coverage Insights

What it provides
A panel on the work item that tells you, at a glance, how much of the code changed for this work item has been covered. The result includes all of its child work items, so a User Story, Feature, or Epic reflects everything beneath it. Next to it, it shows your team's additional coverage metrics (for example, unit tests versus everything except unit tests), and colors every result against your project's quality bar.
Why it matters
Instant answer, no context switching. You see test coverage where you already track the work, instead of hunting through separate reports.
Roll-up for parents. Leads can judge a whole Feature or Epic from one place.
Shared quality language. Green, orange, and red mean the same thing to everyone on the project.
When to use it
Before handing off or closing a work item: is the change actually tested?
In sprint reviews and refinement: quickly spot stories with weak testing.
For release readiness: check coverage on Features and Epics and decide what needs more testing.
When coverage looks low: open the risk analysis to see which child items or methods are responsible.
Example
A tester opens a User Story that is about to be moved to Done. The panel shows 72% in orange. Unit Tests cover 70% of the changed code, but End-to-End tests cover only 5%. Since end-to-end coverage is by far the weakest, she decides to focus there first. She opens the full analysis to see exactly which methods no end-to-end test covers, and asks for tests to be added before sign-off.
Understanding the Data
Open any work item that is within your project's scope and you'll find the coverage panel SeaLights Coverage Analysis on the work item form.
The coverage result
The headline number is the percentage of modified methods (the methods changed as part of this work) that have been covered. It covers the work item itself and all of its child work items.
Under the percentage you'll see how many methods were tested out of the total, and how many are still untested, so you know not just how well covered the work is but how much is left to do.
What the colors mean
The color shows how the result compares to your project's quality bar:
Green
Healthy. Coverage meets or exceeds the Target threshold (recommended 80%)
Orange
Needs attention. Below Target, but not yet at risk
Red
At risk. Below the At-Risk threshold (recommended 50%)
Blue
Your project doesn't use thresholds, so no judgment is applied
The same colors are used everywhere coverage appears.
Metric tags
Below the bar, tags show your team's additional views of coverage, one per secondary metric defined in the project settings. A metric can be a single test stage (for example, Unit Tests) or a group of stages (for example, everything except unit tests). Each tag shows the metric's name and its coverage, using the same colors. If no secondary metrics are defined, no tags are shown.
How coverage rolls up
A parent work item includes everything beneath it. An Epic's result reflects its Features, User Stories, and Tasks together. If a parent looks low, the Work Items tab of the full analysis shows which children are responsible.
How current is the data
The panel shows when the data was last updated ("Data as of" followed by the date and time), so you know how recent the results are.
When coverage data isn't available
You may open a work item and not see coverage numbers. This is expected when no code has been reported yet. Coverage appears once code changes are linked to the work item (or to one of its child items) and reported to SeaLights.
Going deeper
Select Full Analysis to see which child items, test stages, and methods are behind the result. See Work Item Full Coverage Analysis.
Last updated
Was this helpful?

