> 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/use-cases-by-persona/qa-engineers/evaluating-testing-strategy.md).

# Evaluating Testing Strategy

SeaLights is your personal testing laboratory. This use case empowers you to **transform from a passive QA engineer to an active analyst**, leveraging data-driven insights to continuously evaluate and refine your testing strategy. By monitoring code coverage, defect trends, and test execution effectiveness, you'll **ensure your testing efforts remain impactful, efficient, and targeted to the areas that matter most**.

***

## **Step-by-Step Tutorial**

<details>

<summary>1. <strong>Track Coverage &#x26; Effectiveness</strong></summary>

* Utilize SeaLights' Coverage Trend report to visualize code coverage over time. &#x20;
* Monitor the impact of different test types (unit, integration, etc.) on code coverage.
* Compare escaping defect trends to coverage progress, by adding production defects to your coverage trend report.

</details>

<details>

<summary>2. <strong>Deep-Dive into Insights</strong></summary>

* Investigate apps with low coverage or high defect rates, using the Test Gaps Analysis, to understand the potential risks and impact.
* Evaluate the efficiency of existing tests, identifying repetitive or redundant efforts.
* Consider the evolving application functionality and prioritize coverage based on new features and code changes.

</details>

<details>

<summary>3. <strong>Adapt &#x26; Optimize</strong></summary>

* Adjust your testing strategy based on your findings, potentially allocating more resources to critical areas.
* Introduce new test types or techniques to address uncovered areas or improve defect detection.
* Utilize data to justify changes and communicate the impact of your optimization efforts to stakeholders.

</details>

<details>

<summary>4. <strong>Continuously Monitor &#x26; Iterate</strong></summary>

* Integrate data-driven evaluation into your regular testing process, not just a one-time activity.
* Encourage a culture of experimentation and data-driven decision-making within your testing team.

</details>

<details>

<summary>5. <strong>Share &#x26; Learn</strong></summary>

* Share your evaluation results and insights with developers and other stakeholders to foster transparency and collaborative improvement.
* Learn from past successes and challenges, continuously refining your testing approach for increased efficiency and effectiveness.

</details>

By actively monitoring, analyzing, and adapting your testing strategy with SeaLights, you'll transform your testing from a static process into a dynamic and responsive system.


---

# 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/use-cases-by-persona/qa-engineers/evaluating-testing-strategy.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.