...

1. Scope in the scanned code based on what matters to you

   • "Clean" the irrelevant data - see How to Ignore irrelevant code

2. Create a report scheduler

   • Align with your Sprint Schedules (or schedule a Monthly Report)

3. Add your App & Branch to the Test Gap Analytics view - You can pick any configured app and branch and create a time frame for the Test Gap report - see Adding an application to the Test Gap Analytics view

4. Install the SeaLights Code Viewer Chrome Extension on your personal computer with these instructions

Test Gaps Analytics Main Use Cases

The There are three main use cases of working Test Gap Analytics are:

1. Definition of Done for Sprint Quality

2. Monthly Quality Report

3. Test Development

described below.

Definition of Done for Sprint Quality

...

1. Drill down into the relevant file by clicking the file name in the TGA report
   

   Image RemovedImage Added

2. Click on the SCM link for the given file you would want to explore further

3. You will be linked to your code repository and can access the specified file space within your SCM.

   1. You can see the TGA insights in line with your code with the SeaLights "Code Viewer", part of SeaLights Chrome Extension Suite (see the section Steps to Take Before You Start Using Test Gaps Analytics)

   2. SCM's supported by SeaLights Code Viewer– Github, BitBucket, Gitlab, TFS/TFVC

4. Use the test stage drop-down button to focus on a specific test stage

   1. e.g. In order to focus on areas which are not tested by Manual Tests → pick the "Manual Tests" value from the drop-down

5. Review the file and Quality Risks and decide which of these should be addressed within the current/upcoming Sprint

6. Control and Feedback Loop

   1. Reiterate the process in future sprints to ensure that the gaps have been actually closed by your Dev/QA team and identify if new test gaps have been created

   2. Create a monthly report which includes the relevant sprint

...