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
  • Centralized Insights: Code Coverage Data Hub for Go/No-Go Decisions
  • The Value of Non-Unit Tests Coverage
  • Scannable Insights at a Glance

Was this helpful?

  1. User Story Coverage
  2. User Story Coverage Report Overview

Release Go / No Go Report

PreviousUser Story Coverage Report OverviewNextHow to Generate / Edit the Report

Was this helpful?

SeaLights provides a holistic view of the project's code coverage, including insights into the testing of individual user stories across various testing stages.

  • Holistic quality view: The report provides a comprehensive overview of the testing process, enabling you to track the progress of individual user stories across various stages.

  • Data-driven coverage metrics: SeaLights delivers clear and data-driven metrics, aggregated across all testing stages. You can also distinguish between unit tests and other test types.

  • Release with confidence: With the insights provided by the report, you can eliminate guesswork and make informed decisions about the release of user stories and features.

Primary Users

Ideally suited for managers to make informed release decisions for projects, features, and user stories.


Centralized Insights: Code Coverage Data Hub for Go/No-Go Decisions

The Release Go / No-Go Report serves as a centralized hub for gathering and analyzing code coverage data, providing a holistic view of the project's overall code coverage status. It seamlessly integrates information from user stories, their corresponding code changes, and the associated code coverage metrics, offering granular insights at the level of each user story and its code changes.

The Value of Non-Unit Tests Coverage

Going beyond simple overall coverage percentages, the report delves into non-unit test coverage metrics, which are crucial for comprehensive testing. Non-unit tests, such as integration, functional, and end-to-end tests, play a vital role in verifying the functionality and behavior of software. This granularity is crucial, as high overall coverage percentages based solely on unit tests can sometimes paint an incomplete and misleading picture of the true code coverage landscape.

This granular analysis is particularly valuable for identifying potential hotspots where undetected defects may lurk. By focusing on non-unit tests, which often target more complex functionalities, teams can proactively address these areas and enhance the overall quality of the software.

Scannable Insights at a Glance

To facilitate rapid evaluation of code coverage within our User Story Coverage Report, we implemented intuitive color indicators:

  • Red: Attention needed, coverage less than 20%

  • Orange: Room for improvement, coverage between 20% and 70%.

  • Green: Well-covered, exceeding 70% coverage.

These color indicators can be customized to suit specific project requirements. Additionally, methods marked as critical will appear red if they have not been tested by any test type, or orange if they have not been tested by any non-unit test type.

A glimpse of Release Go / No-Go report
A typical workflow with the addition of SeaLights
Drawing