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

# User Story Coverage

### Quality data where your team already works

SeaLights Coverage Analysis brings code coverage insights straight into Azure DevOps and Jira. Developers, testers, leads, and managers can see how well the code behind a work item has been tested, without switching tools or digging through separate reports.

### What you get

#### Coverage on every work item

Open any work item and see how much of the code changed for it has been tested. The number includes all of its child work items, so a Feature or Epic shows the full picture at a glance, broken down by test stage (unit, component, end-to-end, and more).

#### Coverage across a whole set of work items

Pick a saved query and get a hierarchical view of coverage for everything it returns. Leads and managers can check release readiness, spot the weakest areas, and export the data for reviews.

#### Clear, color-coded signals

Set coverage thresholds for your project, and every coverage value turns green, orange, or red according to your own quality standards, so risk is visible instantly.

#### From risk to action

Drill into the full Coverage Analysis to see which work items drag coverage down and exactly which modified methods remain untested, then export the list for the team.

### Who benefits

<table><thead><tr><th width="193.58984375">Role</th><th>Value</th></tr></thead><tbody><tr><td>Developers</td><td>Know whether their changes are tested before they hand off</td></tr><tr><td>Testers</td><td>See which test stages cover a change and where gaps remain</td></tr><tr><td>Leads and managers</td><td>Track release quality across projects and filters, and make data-driven go/no-go decisions</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.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.
