> 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/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-8-measure-defect-escape-rate.md).

# STEP 8: Measure Defect Escape Rate

The **Defect Escape Rate** is your key to **unlocking real quality improvement**. Let's explore how to use it:

#### **Got historical data?**

* Track your progress! Compare Defect Escape Rate from **release to release** to see the impact of SeaLights' new processes.

#### **Starting fresh?**

* No worries! Begin measuring **after your first SeaLights release**.
* Make it a habit: track **monthly or on your preferred schedule**.

#### **Analyzing Progress:**

* A **decreasing Defect Escape Rate** signifies **quality improvement**.
* **No significant change?** Let's dig deeper:
  * **Unaddressed Test Gaps:** Escaping defects may be linked to the test gaps you chose not to address.
  * **Low Quality Threshold:** Is your bar set too low, letting defects slip through?
  * **Test Strategy Optimization:** Focus on component tests? Time for more integration or end-to-end tests!

{% hint style="info" %}
Combine the Defect Escape Rate with other quality metrics for a holistic view.
{% endhint %}


---

# 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/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-8-measure-defect-escape-rate.md?ask=<question>&goal=<user_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.