> 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/code-quality-ownership.md).
# Code Quality Ownership
Take control of code quality for your assigned user stories, especially critical ones! The User Story Coverage Report empowers developers to take ownership and proactively address testing gaps. Track coverage progress seamlessly, identify uncovered code with ease, and deliver well-tested features that shine.
{% hint style="info" %}
**Remember!** Taking ownership of code quality fosters a culture of accountability and leads to higher-quality software. Utilize the User Story Coverage Report regularly to stay informed, proactive, and deliver with confidence!
{% endhint %}
***
## Step-by-Step Tutorial
1. Access Your User Story's Coverage
* Open your user story in Jira and navigate to the "Coverage" tab.\
\
\
**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.
2. Assess Overall Coverage
* Check the "Modified Coverage" and "Non-Unit Tests Coverage" indicators. Green signals sufficient testing, while orange or red suggests potential gaps.
3. Deep Dive into Subtasks
* Open the detailed coverage report to scrutinize individual subtasks.\
\
* **Pro Tip:** Even if overall coverage is green, review subtasks. Crucial functionalities might lack coverage despite good overall numbers.
4. Identify Untested Methods
* Analyze method-level coverage for each subtask. Orange or red signals insufficient testing. Prioritize addressing these methods.
5. Streamline Workflow (Optional)
* Use the "Uncovered Methods Report" to directly access and review only untested methods.
6. Focus on Critical Code
* The report will flag critical code segments red if they have not been tested by all relevant test types.
* Critical code segments are based on your commit messages that include the word "Critical".
7. Collaborate and Act
* Share your findings and any identified gaps with relevant stakeholders during your daily scrum meeting.
* Encourage immediate action to address uncovered areas and ensure comprehensive testing.
---
# 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/code-quality-ownership.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.