> 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.md).

# Coverage Analysis for Azure DevOps (ADO)

<figure><img src="https://1255034336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxSagdStwf6CJ9cI6lA68%2Fuploads%2Fjl6nrWo6FMsUl1Mbn8qU%2FScreenshot%202026-10-29%20at%2014.28.31.png?alt=media&amp;token=2ef26f22-aaf9-4519-bd20-bc482ca58f71" alt=""><figcaption></figcaption></figure>

User Story Coverage for Azure DevOps shows you how well the code behind each work item has been covered, right inside ADO. Coverage rolls up from child work items to their parents, so a Task, a User Story, a Feature, or an Epic each gives you the full picture, with additional views of the metrics your team cares about. Easily track coverage progress also for a sprint, a release, or an entire project by selecting a saved query.

### What you can do

* **See coverage on any work item.** Check code changes coverage, plus your team's own coverage metrics, without leaving the work item.
* **Find the gaps.** Drill into which child work items lower coverage and which modified methods are still untested, then export the list.
* **Review a whole set of work items.** Pick a saved query and see coverage across its hierarchy, add columns for your secondary metrics, and download the data.
* **Set your own quality bar.** Define coverage thresholds per project so results show as green, orange, or red.

### How it works

1. An organization admin connects ADO to SeaLights once.
2. Each project decides which test stages count toward coverage and sets its quality thresholds.
3. Coverage is calculated for work items together with all of their child items, and appears on the work items themselves and in a dedicated cross-project view.

### Get started

<table><thead><tr><th width="297.44921875">Step</th><th>Who</th><th>Guide</th></tr></thead><tbody><tr><td>1. Install the extension</td><td>ADO organization admin</td><td><a href="https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/install-the-extension.md">Install the extension</a></td></tr><tr><td>2. Connect it to SeaLights and ADO</td><td>ADO organization admin</td><td><a href="https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/organization-settings.md">Organization settings</a></td></tr><tr><td>3. Set metrics and thresholds for a project</td><td>Project admin</td><td><a href="https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/project-settings.md">Project settings</a></td></tr><tr><td>4. View coverage</td><td>Everyone</td><td><a href="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</a>, <a href="https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/cross-project-coverage-view.md">Cross-project view</a></td></tr></tbody></table>


---

# 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.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.
