> 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/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-2-take-a-quality-snapshot.md).

# STEP 2: Take a Quality Snapshot

{% hint style="info" %}
Typically, this step is done by QA Manager/Architect or Engineering Manager.
{% endhint %}

Before implementing the Over Time Quality Improvement in your organization, it's crucial to evaluate the quality of your software.

1. Get a snapshot of your current quality by looking at the Test Gaps over the **past few weeks or months**. 
2. Examine the number of **Untested Code Changes** using the Test Gaps Report. This report highlights the methods within your codebase that have not been adequately tested.

By analyzing the number of Untested Code Changes, you gain a **crucial understanding of your current quality baseline**. This knowledge empowers you to prioritize critical areas and address them strategically in your Over Time Quality Improvement journey.

{% hint style="info" %}
**Remember:** This initial snapshot is just the beginning! As you implement changes and improve your testing practices, it's essential to take regular snapshots to track your progress and ensure continuous quality enhancement.
{% endhint %}

***

### Review The Test Gaps Analysis Report

{% content-ref url="/pages/MxC8BYFXUZSIRaspmDpE" %}
[How to Generate / Edit the Report](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/test-gaps-analysis-report/how-to-generate-edit-the-report.md)
{% endcontent-ref %}

<details>

<summary>What does the time range in the report represent?</summary>

The time range in the report captures all the builds that have been reported to SeaLights within that specified range. It's important to note that the time range does not directly correspond to when the tests were executed. This means that tests can be executed outside of the specified time range, yet their coverage will still be included in the report. The time range serves as a reference point for aggregating the relevant builds and their associated test coverage data, providing a comprehensive view of your testing efforts.

</details>

Watch the video to quickly understand the key data in the report, providing you with an overview of your current status.

{% embed url="<https://youtu.be/rysQsorHulw>" %}

With your SeaLights report in hand, dive into the crucial **"Overall Coverage Gap"** metric. This percentage reveals the **areas your tests haven't reached**, indicating potential risks. Remember, it represents the missing pieces, not the total coverage.

In addition, take note of the **total number of untested methods**. If this number is significant, exceeding, for example, 300, consider it a **red flag**. It's time to **prioritize**!&#x20;

We'll guide you through effective prioritization in the next step. For now, focus on identifying these gaps - they're the starting point for your quality improvement journey with SeaLights.

This snapshot of your code quality will serve as a **starting point** for your quality improvement **journey** with SeaLights, empowering you to **incrementally achieve your quality goals** over time. Understanding the quality figures will help you take targeted actions to address the gaps effectively.


---

# 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 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/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-2-take-a-quality-snapshot.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.