# Test Execution Progress Monitoring

Transform into a **proactive testing champion** with the User Story Coverage Report. Monitor and analyze test execution progress, **identifying roadblocks early and advocating** for comprehensive testing throughout the development cycle. Ensure no area lags behind schedule or coverage targets.

***

## Step-by-Step Tutorial

<details>

<summary><strong>1. Access User Story's Coverage</strong></summary>

* Open the releveant user story view in Jira and navigate to the "Coverage" tab.\
  ![](/files/CM4j08TkxBpaJw9rn71b)\
  \
  **Note:** If the tab is missing, the user story deployment isn't complete. Refer to the[Deployment Guide](/knowledgebase/guides/user-story-coverage/technical-overview/deployment-guide.md) for further details.

</details>

<details>

<summary><strong>2. Gauge Overall &#x26; Specific Test Type Coverage</strong></summary>

* Check the "Modified Coverage" and "Non-Unit Tests Coverage" indicators.&#x20;
  * **Green overall?** Great! But proceed if testing hasn't completed, or critical features are involved.
  * **Orange or red overall?:** Investigate further!
* **Examine individual test types:** Identify areas needing attention based on organizational standards.

![](/files/CPelXpDhYkUbGVlmDIQR)

</details>

<details>

<summary><strong>3. Deep Dive into Uncovered Methods</strong></summary>

* Use the **"Uncovered Methods Report"** to quickly review untested methods.\
  \
  ![](/files/1015Kf6lJxP7qcY3diIx)
* **Pro Tip:** Even with green overall coverage, crucial methods might lack testing. Review critically.

</details>

<details>

<summary><strong>4. Identify &#x26; Address Gaps</strong></summary>

* Start with the Uncovered Modified Methods.&#x20;
  * Review the methods completely lacking tests.
  * **Estimate missing scenarios:** Consider what testing might be missing.
* Continue with the specific test types lists.
  * Review untested methods within each test type. Pay close attention to orange (unit test only) and red (no test) methods.
  * **Estimate missing scenarios:** Consider what testing might be missing.
  * **Leverage parent subtask context:** If a method's purpose is unclear, refer to its parent subtask for broader context and understanding. This will help you formulate more relevant test scenarios.

</details>

<details>

<summary><strong>5. Collaborate &#x26; Take Action</strong></summary>

* **Discuss with developers** to understand method functionality and criticality.
* Collaborate to decide which test type is appropriate for the uncovered method.
* **Prioritize:** Address critical gaps first, ensuring comprehensive testing throughout the development cycle.

</details>

{% hint style="info" %}
**Remember:** This framework serves as a foundation. Adapt it to your specific organizational needs, testing strategies, development cycles, and resource availability.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealights.io/knowledgebase/guides/user-story-coverage/use-cases-by-persona/qa-engineers/test-execution-progress-monitoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.