# Code Quality Ownership

SeaLights isn't just about numbers; it's about building pride in your code. This use case empowers you to **step up as a quality champion**, taking ownership through transparency and accountability. By leveraging shared SeaLights reports and insights, you'll **actively contribute to strong releases, build trust with stakeholders, and celebrate the positive impact of your work.**

***

## **Step-by-Step Tutorial**

<details>

<summary>1. <strong>Embrace Shared Visibility</strong></summary>

* Utilize SeaLights' Test Gaps Analysis to gain visibility into overall and modified test coverage and gaps, and track release progress.
* Actively explore and understand the data presented.

</details>

<details>

<summary>2. <strong>Proactively Communicate Impact</strong></summary>

* Share your testing findings and insights with team members and stakeholders, highlighting successes and potential areas for improvement.
* Explain your testing rationale and decisions, fostering understanding and trust in your approach.

</details>

<details>

<summary>3. <strong>Take Ownership of Your Code</strong></summary>

* **Actively participate in test case writing:** Understand your code's behavior by writing tests that identify and fix issues early on.
* **Proactively propose code reviews and participate in discussions:** Share your testing perspective and findings, fostering a collaborative environment.
* **Fix bugs and add tests:** When encountering a bug, prioritize adding comprehensive tests to prevent similar issues in the future. Uncovered modified code with bugs poses a higher risk than uncovered clean code.
* **Document your code:** Well-documented code makes your code easier to understand, maintain, and test for both you and others (developers and QA engineers).

</details>

<details>

<summary>4. <strong>Celebrate Quality Achievements</strong></summary>

* Acknowledge and celebrate improvements in code quality, test coverage, and defect reduction as a team accomplishment.

</details>

<details>

<summary>5. <strong>Continuous Improvement Mindset:</strong></summary>

* View challenges and setbacks as opportunities to learn and grow.
* Participate in discussions and actively contribute to identifying and implementing solutions for quality improvement.
* Seek feedback and utilize it to refine your testing skills and approach.

</details>

By embracing transparency, accountability, and a continuous improvement mindset, you'll transform from a bystander to an active quality advocate. Remember, every line of code, every test written, and every bug identified contributes to a successful release and a product you can be proud of.