> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/user-story-coverage/use-cases-by-persona/qa-engineers/test-execution-progress-monitoring.md).

# 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/8SAjhgdk7zWspzYY6Qks)\
  \
  **Note:** If the tab is missing, the user story deployment isn't complete. Refer to the[Deployment Guide](/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.
  * **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/7NqK7NTwt2s98IKTgdOY)

</details>

<details>

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

* Use the **"Uncovered Methods Report"** to quickly review untested methods.\
  \
  ![](/files/e9xKse2RQHW9boRC6Rm2)
* **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.
  * 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 %}