# User Story Coverage Mechanism

While traditional reports often rely solely on unit test coverage percentages, SeaLights digs deeper. Here's what sets it apart:

### <img src="/files/PrwkoHhCG2WTr5DKolWf" alt="" data-size="line"> **Beyond Unit Tests**

**Unveiling the Untested:** SeaLights dives into **non-unit test coverage**, revealing areas beyond basic functionality that might require attention, tracking any type of tests anywhere in the pipeline: regression, end-to-end, integration, functional, system, API, performance, component and manual tests. This comprehensive view helps minimize undetected defects and ensures true code quality.&#x20;

### <img src="/files/PrwkoHhCG2WTr5DKolWf" alt="" data-size="line"> **Dynamic Code Analysis**

**Tracking Code Changes:** Unlike static analysis, SeaLights tracks **modified code coverage across builds**. This helps identify potential regressions introduced by changes, providing valuable insights for deployment readiness.

### <img src="/files/PrwkoHhCG2WTr5DKolWf" alt="" data-size="line"> **Contextualized Decisions**

**Bridging the Gap:** SeaLights uses user story information from Jira, linking coverage data directly to specific features. This context empowers informed go/no-go decisions based on each user story's unique needs and testing requirements.

<img src="/files/jzuIHyi0kI7x3STw2lZ1" alt="" class="gitbook-drawing">

In short, SeaLights goes beyond simply reporting numbers. It empowers you to understand what, why, and where when it comes to your code coverage, ultimately leading to more informed testing decisions and higher quality software.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/user-story-coverage-mechanism.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.