> 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/prioritizing-test-efforts.md).
# Prioritizing Test Efforts
SeaLights isn't just a testing tool; it's your secret weapon for prioritizing testing efforts like a pro. This use case equips you to **identify critical areas of your software that demand the most attention, ensuring you maximize the impact of your testing resources**. By leveraging data-driven insights and strategic planning, you'll **optimize testing efficiency, minimize risks, and deliver high-quality software with confidence.**
***
## **Step-by-Step Tutorial**
1. Gather Data & Understand Context
* Utilize SeaLights' Test Gap Analysis report to analyze code coverage, testing gaps, and risk assessments.
* Consider business priorities, upcoming releases, and potential impact of different areas on user experience.
2. Identify Critical Areas
* Prioritize areas with low code coverage, high defect history, or involvement in core functionalities.
* Consider the potential impact of issues in each area on user experience, business goals, or compliance.
3. Strategize Your Test Plan
* Allocate more testing resources (time, testers, automation) to critical areas based on their priority.
* Define diverse testing types (functional, performance, security) to ensure comprehensive coverage.
* Utilize SeaLights' downloadable reports to organize and prioritize your test plan.
4. Continuously Monitor & Adapt
* Track test execution progress and monitor defect detection rates in critical areas.
* Analyze new data and adjust your testing strategy as needed, prioritizing newly identified risks or areas requiring additional attention.
* Leverage Test Gaps Analysis and Coveragee Trend reports to communicate testing progress and rationale to stakeholders.
5. Celebrate & Share Success
* Highlight the positive impact of your prioritized testing efforts on code quality and risk mitigation.
* Share your learnings and best practices with your team to foster a culture of data-driven prioritization.
By following these steps you'll transform your testing from a guessing game into a strategic endeavor, delivering maximum value and ensuring the quality and success of your software.
---
# 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/prioritizing-test-efforts.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.