> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/work-item-coverage-insights.md).

# Work Item Coverage Insights

<figure><img src="https://1255034336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxSagdStwf6CJ9cI6lA68%2Fuploads%2FSp7Ktf3lCXwp218V3DPm%2FScreenshot%202026-10-30%20at%2009.51.30.png?alt=media&amp;token=51290e01-0456-4ade-b896-ba6ba6f0150f" alt=""><figcaption><p>Coverage in the context of a Work Item</p></figcaption></figure>

### 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&#x20;

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:

<table><thead><tr><th width="115.8671875">Color</th><th>Meaning</th></tr></thead><tbody><tr><td>Green</td><td>Healthy. Coverage meets or exceeds the Target threshold (recommended 80%)</td></tr><tr><td>Orange</td><td>Needs attention. Below Target, but not yet at risk</td></tr><tr><td>Red</td><td>At risk. Below the At-Risk threshold (recommended 50%)</td></tr><tr><td>Blue</td><td>Your project doesn't use thresholds, so no judgment is applied</td></tr></tbody></table>

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](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/work-item-coverage-insights/work-item-full-coverage-analysis.md).

{% hint style="info" icon="lightbulb-on" %}
Coverage on a parent (e.g., an Epic) includes everything beneath it. Open the **Work Items** tab of the risk analysis dialog to find which children are dragging it down.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/work-item-coverage-insights.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
