> 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/whats-new/november-2026/coverage-analysis-for-azure-devops.md).

# Coverage Analysis for Azure DevOps

SeaLights code changes coverage now appears directly in Azure DevOps (ADO). See whether the code behind a User Story, Feature, or Epic has been tested without leaving ADO, and track coverage progress for a sprint, a release, or an entire project by selecting a saved query.

<figure><img src="https://3871776571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTqMveDrJ1pB6OErwHvF0%2Fuploads%2FDCIlQDq4tvMxCBCGdqpQ%2FScreenshot%202026-10-29%20at%2014.28.31.png?alt=media&amp;token=f62651dd-37d3-4040-b2c8-a25de105f9e7" alt=""><figcaption></figcaption></figure>

### What's New

* **Coverage on every work item.** Each work item shows the percentage of its modified methods that have been tested, along with how many are covered and how many are still uncovered. Coverage rolls up from child work items, so a parent reflects everything beneath it.
* **Your own views of coverage.** Define secondary metrics, such as Unit Tests or Non-Unit Tests (everything except unit tests), and see each one as a tag next to the main result.
* **Color-coded quality signals.** Set coverage thresholds for each project, and results show as healthy, warning, or critical against your own quality bar.
* **Full Analysis.** Drill into which child work items lower coverage, which test stages cover which code, and which modified methods are still uncovered.
* **Cross-project coverage view.** Select a saved query and review coverage across its entire work item hierarchy. Add columns for your secondary metrics.
* **Snapshots for audit.** Download coverage data as CSV from Full Analysis or the cross-project view to capture a point-in-time snapshot for audit purposes.

### Why It Matters

Coverage data is most useful where decisions are made. By bringing it into the tools your team already uses to plan and track work, SeaLights removes the need to switch between systems or dig through separate reports.

Developers and testers see testing gaps before work is handed off. Leads and managers get a clear view of release readiness across Epics and Features. And because thresholds and metrics are defined per project, everyone on a team shares the same definition of "well tested". Downloadable snapshots also give you a record of coverage at a given point in time when audits require evidence.

### Get Started

* [Install and set up User Story Coverage for ADO →](/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/install-the-extension.md)
* [Learn how to read coverage on work items →](/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/work-item-coverage-insights.md)
* [Explore the cross-project coverage view →](/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/cross-project-coverage-view.md)

***

*The extension is shared privately with your Azure DevOps organization. Contact your SeaLights representative to get access.*


---

# 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/whats-new/november-2026/coverage-analysis-for-azure-devops.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.
