> 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/work-item-full-coverage-analysis.md).

# Work Item Full Coverage Analysis

<figure><img src="https://1255034336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxSagdStwf6CJ9cI6lA68%2Fuploads%2FcMK4evI3dLTTMYp1JvpE%2FScreenshot%202026-10-30%20at%2013.12.53.png?alt=media&amp;token=732a14ef-90e7-4fde-8bc4-9a6178be501d" alt=""><figcaption></figcaption></figure>

#### What it provides

A detailed view that explains **why** a work item's coverage is what it is. It answers three questions: which child work items are lowering the result, which parts of the code are covered by which test stages, and which modified methods have no testing at all.

#### Why it matters

A coverage number tells you there is a problem. This view tells you where, so your team can act on it directly instead of guessing. The exportable lists turn findings into a concrete to-do list for developers and testers.

#### When to use it

* **When coverage is orange or red** and you need to know what is behind it.
* **Before a release,** to identify the riskiest untested changes.
* **When planning test effort,** to focus on the code that matters most.
* **When coordinating across a team,** by sharing the exported list of untested methods.

#### How teams use it

1. Start with **Work Items** to find which children have low or missing coverage.
2. Use **Coverage** to see which test stages cover which code.
3. Use **Untested Code** to get the exact methods that still need tests, then download the list.

***

### Understanding the Data&#x20;

The Full Coverage Analysis opens from the **Full Analysis** link in the work item panel. It has three tabs, each going one level deeper into why the coverage looks the way it does.

#### Tab 1. Work Items:  which work is behind the number

This tab lists the work item and everything beneath it (for an Epic, its Features, User Stories, and Tasks), with the title count at the top. For each item you see who it's assigned to, its current state, and its own coverage, colored like everywhere else.

**NA** means no code has been reported yet for that item or its children, so there's nothing to measure. Low or NA items are the first place to look when a parent's coverage is lower than expected.

#### Tab 2. Coverage: which tests cover which code

At the top you'll see the overall coverage and your metric tags, as in the work item panel.

Below is a tree of the code that was changed: application or service, then folder, then file, then method. Each row shows the combined coverage of all test stages, followed by a column for every test stage.

* At the application, folder, and file levels, the columns show a percentage, so you can see which areas are well covered.
* At the method level, the columns show a ✓ if that stage covered the method and an ✗ if it didn't.

Note that the tags at the top show your secondary metrics, while the table shows the raw data per test stage. **Download CSV** exports the full table.

#### Tab 3. Untested Code: what still needs tests

This tab lists the modified methods that no test has covered. Use the dropdown to choose what "not covered" means:

* **Any Test Stage** (default): methods not covered by any test stage.
* **A specific stage**, such as Component Tests: methods that stage didn't cover, even if other stages did.

**Download CSV** exports the list as filtered, ready to share with the team.


---

# 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/work-item-full-coverage-analysis.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.
