# Testing Effort Prioritization

The User Story Coverage Report empowers QA engineers to prioritize testing efforts effectively and **collaborate seamlessly with developers.** By combining strategic prioritization with proactive collaboration, you can achieve comprehensive testing coverage and deliver high-quality software with confidence.

{% hint style="info" %}

#### **Tips for fostering collaboration:**

* **Bridge the Gap:** Utilize the report to **proactively engage developers** in discussions. Identifying untested methods is just the beginning.
* **Seek Clarification:** Schedule regular meetings to **discuss complex methods and seek their expertise**.
* **Joint Ownership:** Foster a **collaborative spirit** to overcome challenges and ensure comprehensive testing.
  {% endhint %}

***

## Step-by-Step Tutorial

<details>

<summary><strong>1. Access the Report</strong></summary>

* Navigate to your relevant Jira project and locate the User Story Coverage report within the Sheets page.
* If unavailable, follow the [How to Generate / Edit the Report](/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/release-go-no-go-report/how-to-generate-edit-the-report.md) guide for creation.&#x20;

</details>

<details>

<summary>2. Ensure Scope Accuracy</summary>

* Verify the report covers the intended timeframe using the Scope icon at the bottom right. ![](/files/lDyvnNPA3lFiuHLqTCM9)
* Adjust the scope as needed, referring to the [How to Generate / Edit the Report](/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/release-go-no-go-report/how-to-generate-edit-the-report.md) guide.&#x20;

</details>

<details>

<summary><strong>3. Visualize and Analyze</strong></summary>

* **Simplify View:** Collapse subtasks under user stories (or your hierarchy) for better visualization. \ <img src="/files/5GhTKBBcNI3bG4FZ8v22" alt="" data-size="original">
* **Review Metrics:** Analyze both Modified Coverage and Non-Unit Tests Coverage for each user story.

</details>

<details>

<summary><strong>4. Identify and Categorize Gaps</strong></summary>

Focus your efforts on areas most likely to lack comprehensive testing. Expand these user stories to pinpoint specific subtasks lacking tests.

**Critical Non-Unit Test Gaps:**&#x20;

* Begin by prioritizing user stories where **Non-Unit Tests Coverage** is marked **red (low coverage) or orange (requires improvement)**.&#x20;
* These stories have the highest potential for missing crucial non-functional aspects like integration, usability, or performance.&#x20;
* **Verify Satisfactory Coverage:** Ensure subtasks with sufficient coverage align with your testing strategy (e.g., API testing for relevant changes).

**Address Moderate Non-Unit Test Gaps:**&#x20;

* After addressing critical gaps, move to stories with **green Non-Unit Tests Coverage**, but not 100%.&#x20;
* Analyze these stories closely, as moderate gaps could still indicate vulnerabilities.&#x20;
* **Address Specific Test Types:** Assess individual test type coverage against your standards and identify responsible subtasks.

</details>

<details>

<summary><strong>5. Craft a Testing Plan</strong></summary>

* **Categorize Gaps:** Create separate lists for:
  * Uncovered subtasks.
  * Subtasks with low coverage.
  * Subtasks lacking crucial test types (based on your strategy).
* **Assign Ownership:** Match each list item with its parent user story for context.

</details>

<details>

<summary><strong>6. Prioritize Resources</strong></summary>

**Strategic Allocation:** Follow this sequence:

* Address uncovered subtasks first (complete testing absence).
* Move to subtasks with low coverage, prioritizing based on severity and impact.
* Assign relevant individuals to cover subtasks within critical test types, focusing on sensitive code sections and critical functionality.

</details>

{% hint style="info" %}
**Remember:** This framework serves as a foundation. Adapt it to your specific organizational needs, testing strategies, 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/testing-effort-prioritization.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.