STEP 5: Analyze Test Gaps

Typically, this step is done by QA Manager and the related Engineering Manager / Dev Team Lead / Tech Architect.

Tackle Test Gaps, Achieve "0 Critical": A New Era in Quality Control

Traditionally, Test Analysis meant finding code problems for developers to fix and retesting with existing tests. But with "Test Gaps," the game changes! SeaLights introduces a paradigm shift in your quality workflow with the "0 Critical Test Gaps" KPI. This powerful metric empowers you to:

1. Identify & Address Missing Tests: During Test Analysis, analyze Untested Code Changes within your targeted code subset. This proactive approach minimizes the risk of escaped defects.

2. Expand Responsibilities: Beyond identifying fixable code issues, QA, Automation Engineers, and other team members join forces and actively create new tests or modify existing ones to cover critical areas impacted by code changes. This continuous ownership across teams fosters a culture of collective quality.

3. Prioritize Effectively: Conduct Test Gaps Analysis after each major test cycle using relevant code labels to prioritize critical gaps for immediate action. Data-driven decisions.

The ultimate goal is to deploy the product without any critical test gaps and achieve the 0 critical Test Gaps KPI. This ensures readiness for the go/no-go decision and aligns with the Code Changes Coverage KPI.

By striving for zero critical test gaps, you can achieve comprehensive test coverage and significantly reduce the risk of critical defects in your software.

Can code labels be added to an existing Test Gaps report?

No, it is not possible to add code labels to an existing Test Gaps report. Once a report is created, it cannot be edited to include additional code labels. The only editable aspect of an existing report is the date/build range.

If you have added a new code label and wish to capture data related to the code change associated with that label, you will need to create a new report. This ensures that the report reflects the specific data and coverage related to the code changes associated with the newly added code label.

Please note that generating the TGA report may take a few minutes to complete. To ensure a smooth and efficient experience, we recommend preparing the report data in advance if you plan to use it during a meeting. This preparation will help you make the most out of your meeting time and ensure a productive discussion centered around the test gaps identified in the report.