STEP 2: Take a Quality Snapshot

Typically, this step is done by QA Manager/Architect or Engineering Manager.

Before you embark on Release Quality Improvement, get a clear picture of your software's current state. This critical step ensures you focus your efforts effectively.

1. Once you have a testable product and have completed the initial testing cycle, it's time for a snapshot.

2. Leverage the Test Gaps Analysis report to identify Untested Code Changes. These are modified methods within your codebase that haven't been adequately tested, potentially harboring hidden risks.

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 Release Quality Improvement journey.

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.

---

Review The Test Gaps Analysis Report

How to Generate / Edit the Report

What does the time range in the report represent?

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.

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

With your SeaLights report in hand, dive into the crucial "Modified Coverage Gap" metric. This percentage reveals the gaps in coverage for recently changed code, highlighting potential areas of risk. Remember, it represents the missing pieces, not the total coverage.

Additionally, keep an eye on the total number of untested modified methods. A high number (e.g., exceeding 100) indicates significant testing gaps. Don't worry about irrelevant sections! The next step will guide you on effectively prioritizing and addressing these critical areas.

Focus your efforts strategically on these uncovered zones, ensuring your testing remains laser-focused and efficient. Remember, this snapshot is just the beginning of your SeaLights quality journey! Our ultimate goal? Deploying your product free from critical test gaps.

By understanding these key metrics, you're empowered to take targeted actions and close the coverage gaps effectively.