LogoLogo
Product
  • Knowledge Base
  • What's New
  • Guides
  • User Story Coverage
    • Getting Started
    • User Story Challenges & Solution
      • Typical Implementation
      • The Challenges
      • The Solution
    • User Story Coverage Report Overview
      • Release Go / No Go Report
        • How to Generate / Edit the Report
      • User Story Quality Overview
        • How to Generate the User Story View
      • User Story Coverage Analysis
        • How to Generate the Analysis View
      • Uncovered Methods View
        • How to Generate the View
      • Customization
      • Integration
    • Use Cases by Persona
      • Managers
        • Informed Go/No Go Decisions Making
        • Effective Resources Prioritization
        • Overall Progress Monitoring
      • Developers
        • Code Quality Ownership
        • Seamless Collaboration with QA
        • Code Review Facilitator
      • QA Engineers
        • Test Execution Progress Monitoring
        • Testing Effort Prioritization
        • Testing Strategy Planing
    • Technical Overview
      • User Story Coverage Mechanism
      • Technical Architecture
      • Deployment Guide
        • US1_getResults.sh
        • US2_createReport.sh
        • US_UpdateConfluence.sh
  • Test Optimization
    • Getting Started
    • Test Execution Challenges & Solution
      • The Challenges
      • Test Optimization Solution
      • Test Optimization Main Advantages
    • Test Optimization Overview
      • Automated Test Optimization
      • Manual Test Optimization
      • Test Optimization for Pull Request
      • Test Selection Policies
        • Full Run Policy
        • No Code Changes Policy
        • Common Code Policy
        • Fastest Path to 100% Coverage Policy
      • Integrations
    • Use Cases by Persona
      • Managers
        • Fast Delivery
        • Resource Optimization
        • Thorough Testing in Tight Schedule
      • Developers
        • Exploring Only Relevant Test Failures
        • Faster Feedback Loop
        • Shift Left Testing
      • QA Engineers & Manual Testers
        • Faster & Focused Manual Testing
        • Optimizing Test Suite
        • Having Stable Product for Testing
    • Technical Overview
      • Test Optimization Mechanism
        • Associating Code With Tests
          • Statistical modeling
          • One-to-One Mapping
          • Calibration
        • Detecting Modified Code
        • Generating Test Recommendations
      • Technical Architecture
      • Deployment Guide
  • Quality Improvement
    • Getting Started
    • Challenges & Approach Comparison
      • The Challenges
      • Quality Improvement Approaches
      • Choosing the Right Approach
    • Quality Improvement Solution Overview
      • Test Gaps Analysis Report
        • How to Generate / Edit the Report
      • Coverage Trend Report
        • How to Generate / Edit the Report
      • Proof of Testing Report
        • How to Generate / Edit the Report
      • Release Quality Improvement Guide
        • STEP 1: Deploy SeaLights
        • STEP 2: Take a Quality Snapshot
        • STEP 3: Prioritize Code Areas
          • Add Code Labels
          • Ignore Irrelevant Code
          • Perform a Deep CSV Analysis
        • STEP 4: Set Baseline & Threshold
        • STEP 5: Analyze Test Gaps
        • STEP 6: Write Tests
        • Step 7: Make a Go / No Go Decision Based on Quality Gate
        • STEP 8: Measure Defect Escape Rate
      • Over Time Quality Improvement Guide
        • STEP 1: Deploy SeaLights
        • STEP 2: Take a Quality Snapshot
        • STEP 3: Prioritize code areas
          • Add Code Labels
          • Ignore Irrelevant Code
          • Perform a Deep CSV Analysis
        • STEP 4: Set Baseline & Goal
        • STEP 5: Set timeline
        • STEP 6: Write tests
        • STEP 7: Monitor progress
        • STEP 8: Measure Defect Escape Rate
    • Use Cases by Persona
      • Managers
        • Effective Prioritization & Budget Allocation
        • Tracking Progress & Measuring Impact
        • Data-Driven Release Decisions
        • Transparency & Communication
      • Developers
        • Mastering Code Coverage
        • Seamless Collaboration with QA
        • Code Quality Ownership
      • QA Engineers
        • Prioritizing Test Efforts
        • Contributing to Release Informed Decisions
        • Seamless Collaboration with Developers
        • Evaluating Testing Strategy
    • Technical Overview
      • Solution Mechanism
      • Technical Architecture
      • Deployment Guide
  • Value Proposition
    • Overview
    • Quality Use Cases
      • Go/No Go Decisions
      • Quality Improvement & Test Gaps
      • Governance & Quality Gates
      • Compliance & Proof of Testing
    • Test Optimization Use Cases
      • Reduce Costs & Infrastructure
      • Shorten Release Cycles
      • Reduce Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. Quality Improvement
  2. Quality Improvement Solution Overview
  3. Release Quality Improvement Guide

STEP 2: Take a Quality Snapshot

PreviousSTEP 1: Deploy SeaLightsNextSTEP 3: Prioritize Code Areas

Was this helpful?

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

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.

How to Generate / Edit the Report