> 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/user-story-coverage/use-cases-by-persona/qa-engineers.md).

# QA Engineers

The report empowers QA engineers to:

* **Monitor test execution progress:** Keep tabs on overall coverage progress and identify areas where testing is lagging behind.
* **Prioritize testing efforts:** Collaborate with developers to focus testing resources on areas with low coverage or critical functionality.
* **Plan testing strategy:** Leverage detailed coverage data to inform test case creation and selection, ensuring comprehensive testing coverage.

***

## Tutorials

{% content-ref url="/pages/uRnSB8ewqq1q0s1pE4C7" %}
[Test Execution Progress Monitoring](/knowledgebase/guides/user-story-coverage/use-cases-by-persona/qa-engineers/test-execution-progress-monitoring.md)
{% endcontent-ref %}

{% content-ref url="/pages/1Nzgds0vJDjkVocWPSsu" %}
[Testing Effort Prioritization](/knowledgebase/guides/user-story-coverage/use-cases-by-persona/qa-engineers/testing-effort-prioritization.md)
{% endcontent-ref %}

{% content-ref url="/pages/jgerdHSDQmAkVEygN2t3" %}
[Testing Strategy Planing](/knowledgebase/guides/user-story-coverage/use-cases-by-persona/qa-engineers/testing-strategy-planing.md)
{% endcontent-ref %}


---

# 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/user-story-coverage/use-cases-by-persona/qa-engineers.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.