> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/coverage-and-quality-insights/user-story-coverage/user-story-coverage-mechanism.md).

# 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/s2eE8oSQfXeYxs8G72YZ" 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.

### <img src="/files/s2eE8oSQfXeYxs8G72YZ" 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/s2eE8oSQfXeYxs8G72YZ" 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/b9Zb3gwYoxMxpghJXEBu" 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.