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
  • Release Quality Improvement
  • Over Time Quality Improvement
  • Key considerations for successful SeaLights implementation

Was this helpful?

  1. Quality Improvement
  2. Challenges & Approach Comparison

Quality Improvement Approaches

SeaLights' main quality improvement approaches empowers teams to build and maintain a culture of continuous quality improvement. Each approach has distinct benefits and can be tailored to suit your organization's goals and resources effectively.

Release Quality Improvement ensures stable releases, while Over Time Quality Improvement lays the foundation for future reliability and maintainability.

While both approaches leverage SeaLights data and insights, it's important to remember that implementation requires thoughtful planning and process adjustments.


Release Quality Improvement

  • Focuses on ensuring code changes for product deployment are adequately covered by tests.

  • Uses Code Changes Coverage as a KPI and quality gate for releases.

  • Ensures releases meet quality standards before going live.

Over Time Quality Improvement

  • Takes a long-term view, focusing on gradual improvement of overall code coverage.

  • Identifies untested code changes but doesn't block immediate releases.

  • Aims to steadily increase coverage over time, leading to long-term quality enhancement.


Key considerations for successful SeaLights implementation

  • Defining processes: Establish best practices for analyzing coverage gaps, writing new tests based on identified gaps, and determining appropriate test quantities and types.

  • Setting KPIs: Implement new KPIs within existing processes to track progress towards quality objectives.

  • Determining quality gates: Define clear criteria for go/no-go release decisions, including desired coverage levels and acceptable risk thresholds.

  • Planning and checkpointing: Even with the "over time" approach, plan a timeline with defined checkpoints, set specific coverage goals, prioritize areas for improvement, and establish clear release criteria.

SeaLights empowers data-driven decision-making, but it's your organization's commitment to continuous improvement that unlocks the full potential of this powerful solution. Remember, the data provided by SeaLights is just the starting point. Building a culture of quality requires ongoing effort, planning, and the creation and maintenance of new processes and KPIs.

By actively engaging in these considerations, your organization can leverage SeaLights as a catalyst for achieving continuous quality improvement, faster releases, and enhanced software reliability.

No matter your goals or resources, SeaLights provides the tailored tools and insights to achieve exceptional software quality.

PreviousThe ChallengesNextChoosing the Right Approach

Was this helpful?