> 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/guides/quality-improvement/coverage-analysis-playbooks.md). # Coverage Analysis Playbooks The Coverage Analysis Playbooks are practical, scenario-based guides designed to help QA Engineers, QA Managers, and Release Managers get immediate value from Coverage Analysis, without having to figure out the right configuration from scratch. Each playbook is built around a real team scenario: a sprint in progress, an approaching release, a need to understand which services are lagging, or a desire to build a persistent quality dashboard. Every playbook walks you through the situation, explains how Coverage Analysis helps, provides a recommended configuration, and includes success metrics so you can measure improvement over time. *** ### Playbooks Scenario-based guides for common team workflows. Each playbook describes a real situation, walks you through it end to end, and includes success metrics to help you measure progress over time.

#	Playbook	Best For
1	Tracking Coverage During a Sprint	QA Engineers, QA Managers
2	Confirming Release Readiness	QA Managers, Release Managers
3	Monitoring Ongoing Quality as a Team Dashboard	QA Managers, Engineering Leads

*** ### A Note on Permissions Creating and editing Coverage Analysis views requires Admin or DevOps permissions. All other users can access, filter, and export any view that has been set up for them, no special permissions needed to use the playbooks once a view exists. If you don't have permission to create views, share the relevant playbook with your QA Manager or admin and ask them to set up the view for your team. --- # 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/guides/quality-improvement/coverage-analysis-playbooks.md?ask=&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.