# Seamless Collaboration with QA

Work together with the QA team! Share your coverage insights and collaborate to address gaps effectively and focus testing efforts on what matters most. 

By fostering seamless collaboration and proactive gap identification, you and your QA team can achieve comprehensive testing, deliver high-quality software, and build a culture of shared responsibility for quality.

***

## Step-by-Step Tutorial

<details>

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

* Navigate to your relevant Jira project and open the Sheets page with the User Story Coverage report.
* If unavailable, follow the [how-to-generate-edit-the-report](https://docs.sealights.io/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/release-go-no-go-report/how-to-generate-edit-the-report "mention") guide to create it.

</details>

<details>

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

* Verify the report covers the current focus by checking the Scope icon at the bottom right.\
  ![](https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/hVTaa3QKp86pIL2448L6/image.png)&#x20;
* Adjust the scope if needed using the [how-to-generate-edit-the-report](https://docs.sealights.io/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/release-go-no-go-report/how-to-generate-edit-the-report "mention") guide.

</details>

<details>

<summary><strong>3. Monitor Coverage</strong> </summary>

* Collaboratively monitor coverage across all relevant user stories and subtasks.
* Analyze both Modified Coverage and Non-Unit Tests Coverage for each item, understanding coverage levels and potential gaps.

</details>

<details>

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

* Be alerted to low coverage (0% or very low) or specific test types lacking coverage within your scope.
* Drill down into uncovered areas by:
  * Opening the relevant user story/subtask in Jira and navigating to the "Coverage" tab.&#x20;
  * Opening the "Uncovered Methods Report" for direct access to untested methods.\
    \
    ![](https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/XPZIvgi72jL9GDfC1mBf/image.png)

</details>

<details>

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

* Discuss uncovered methods with your QA team.
* Explain the functionality and criticality of each method, aiding in test type selection and prioritization.

</details>

<details>

<summary><strong>6. Make it Routine</strong></summary>

Integrate this collaborative review process into daily scrum meetings or weekly meetings to ensure continued awareness and proactive gap closure.

</details>