> 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/developers/seamless-collaboration-with-qa.md).
# 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
1. Access the Report
* 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](/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/release-go-no-go-report/how-to-generate-edit-the-report.md) guide to create it.
2. Ensure Scope Accuracy
* Verify the report covers the current focus by checking the Scope icon at the bottom right.\
* Adjust the scope if needed using 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.
3. Monitor Coverage
* 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.
4. Identify Gaps & Drill Down
* 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.
* Opening the "Uncovered Methods Report" for direct access to untested methods.\
\
5. Collaborate & Explain
* Discuss uncovered methods with your QA team.
* Explain the functionality and criticality of each method, aiding in test type selection and prioritization.
6. Make it Routine
Integrate this collaborative review process into daily scrum meetings or weekly meetings to ensure continued awareness and proactive gap closure.
---
# 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/developers/seamless-collaboration-with-qa.md?ask=&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.