> 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/july-2026/coverage-analysis-built-for-every-team.-every-process..md).
# Coverage Analysis: Built for Every Team. Every Process.
No two teams work the same way, and Coverage Analysis doesn't ask them to. Pin a view to a sprint start and watch coverage grow as the sprint progresses. Lock it to a release window and get a definitive, consolidated answer before making a go/no-go decision, no last-minute report scrambling, no chasing numbers from individual teams. Roll it forward automatically (last 7 days, last 30 days, current quarter, previous week) so it stays relevant without maintenance. Zoom into the last few hours to track the immediate impact of a testing session. Scope by lab, by app, by branch, or by code label. One team's application is a single microservice. Another's is thirty. Coverage Analysis handles both, and refreshes automatically every 15 minutes so your team always has a current picture without lifting a finger.
### What's New
SeaLights now gives your team a single, unified place to see exactly how well your application is tested, across every service, every test stage, and every team, without stitching together reports or chasing down numbers from individual dashboards.
Coverage Analysis lets you:
* **See the full picture instantly.** Overall coverage across all your services, aggregated in one view, always shared with your whole team.
* **Know what matters most.** Change Coverage surfaces whether the code your team actually modified was tested, not just whether the overall numbers look healthy.
* **Catch risk before it ships.** Failing tests surface right alongside coverage data, so nothing hides in a separate report.
* **Get there without the complexity.** Scope your view by Lab and SeaLights figures out which services to include, no infrastructure expertise required.
### The Data Was Always There. Now It's All in One Place.
SeaLights has always collected rich coverage intelligence, per build, per app, per test stage. The data was there. What was missing was a way to bring it all together, sliced exactly the way each team needs to see it.
Coverage Analysis is that place. For the first time, QA Engineers, QA Managers, and Release Managers can look at the same data, across every service, every test stage, every time window, without switching between reports or manually assembling numbers. The insight that used to require deep expertise is now a few clicks away for anyone on the team.
### See Every Gap. Ship with Confidence.
Critical coverage gaps don't announce themselves, they hide in the space between services, between test stages, and between reports. Coverage Analysis brings them into the open, so your team always knows where the risks are before they become production issues. Whether you're a QA Manager tracking sprint quality, a Release Manager making a go/no-go call, or an Engineering Lead building a culture of continuous quality - the answer is always already there.
### Things to Know
**Available for customers not using Integration Build** Coverage Analysis is currently available for customers working without an Integration Build. Support for customers still using the Integration Build concept is on the roadmap and coming soon.
**Ignore Rules are applied automatically** Any Ignore Rules you have configured in SeaLights are automatically respected in Coverage Analysis. No new builds or additional configuration required.
**Data availability** Coverage Analysis includes data from mid-July 2025 (or other date specified by your SeaLights customer success manager) onwards. Data captured before that point was collected under a different ingestion mechanism and is not reflected in views.
**Coverage Analysis is based on when testing happened, not when builds were reported** Unlike other SeaLights reports where the date range refers to when builds were reported, Coverage Analysis is based on when testing actually happened. If testing occurred outside your selected range, it won't appear in the view, making it a true reflection of your testing activity within that period.
### Get Started
* [Coverage Analysis Overview →](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/coverage-analysis)
* [Coverage Analysis Playbooks →](https://docs.sealights.io/knowledgebase/guides/quality-improvement/coverage-analysis-playbooks)
* [Creating Your First View →](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/coverage-analysis/creating-and-editing-a-view)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sealights.io/knowledgebase/whats-new/july-2026/coverage-analysis-built-for-every-team.-every-process..md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.