Best Practices

SeaLights best practices for how to measure the impact of changes to your applications and improve the quality of what is delivered. This assumes that you already have completed the steps to integrate SeaLights with your CI (Build Scanner) and testing frameworks (Test Listeners).

 

Videos

STEP 1. IDENTIFY NEW/MODIFIED CODE

The first “Line of Defense” in implementing a Software Quality Intelligence process involves putting in place a consistent methodology that will enable you to capture code coverage across all test stages (unit, component, functional, integration, sanity, API, user acceptance, manual, etc.) and start the process of identifying quality risks.

STEP 2. ANALYZE COVERAGE DATA

The second “Line of Defense” in implementing a Software Quality Intelligence process involves applying the measurements gathered in the “Identify” phase to drive improved quality across all applications and services that are being reported to SeaLights through the following SeaLights features:

  • Using the Code Viewer to view coverage data

  • Analyzing Quality Risks

STEP 3. DEFINE QUALITY POLICIES

The third “Line of Defense” in implementing a Software Quality Intelligence process involves defining Quality Policies based on risk levels and automatic gates to accelerate processes.

STEP 4. PERFORM A RETROSPECTIVE ANALYSIS

In the “Report” phase of implementing a Software Quality Intelligence process we provide the ability to produce sprint retrospectives to aid in the planning process for subsequent sprints with Test Gap Analytics (TGA) Reports.

In the “Trend Reporting” phase of implementing a Software Quality Intelligence process we take a high-level look at how quality risks associated with application code have developed over time with the SeaLights Quality Analytics Coverage Trend Reports.

STEP 6. OPTIMIZING EFFICIENCY/ VELOCITY

In the “Optimization” phase of implementing a Software Quality Intelligence process we use SeaLights’s capability to provide visibility into actual test execution time and test coverage requirements to reduce test cycles and improve test effectiveness.