> 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/value-proposition/quality-use-cases/quality-improvement-and-test-gaps.md). # Quality Improvement & Test Gaps This section explores SeaLights' quality improvement approaches and showcases SeaLights' power in identifying and addressing test gaps to proactively boost code quality and build a more reliable product. Watch the following videos to gain the knowledge to leverage SeaLights' full suite of quality improvement tools and reports. * [Quality Improvement & Test Gaps - Overview](#quality-improvement-and-test-gaps-overview) * [Quality Improvement: Within a Release vs Outside Releases](#quality-improvement-within-a-release-vs-outside-releases) * [Test Gaps for User Story](#test-gaps-for-user-story) * [Test Gaps for Component](#test-gaps-for-component) * [Quality Trends](#quality-trends) *** ### Quality Improvement & Test Gaps - Overview {% embed url="" %} ### Quality Improvement: Within a Release vs Outside Releases {% embed url="" %} ### Test Gaps for User Story Video is coming soon... ### Test Gaps for Component Video is coming soon... ### Quality Trends Video is coming soon... --- # 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/value-proposition/quality-use-cases/quality-improvement-and-test-gaps.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.