LogoLogo
Product
  • Knowledge Base
  • What's New
  • Guides
  • Welcome!
  • Intro to SeaLights
    • What is SeaLights
      • Glossary
      • Working in Conjunction with Your Quality / Coverage Tools
        • SeaLights vs SonarQube
        • SeaLights vs JaCoCo
    • Technical Overview
      • Test Stage Cycle
    • FAQ
  • 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
  • What's New
    • What's New Highlights
    • 2024
      • July 2024
        • New Dashboard Design
        • New Coverage Report
        • Test Optimization - Build Breakdown Improvements
      • August 2024
        • New Navigation Bar
        • Enhanced Code Changes Calculation in TGA Report
      • September 2024
        • Executive Summary Report for Multi-Branch Environments
      • October 2024
        • Enhanced TIA Settings
        • Test Optimization Timeline
        • Test Optimization - Application Under Test
        • Saved Views on Dashboard
        • Group Coverage Trend Report for All Branches
      • November 2024
      • December 2024
        • Simplified TGA Report Creation
    • 2025
      • January 2025
      • February 2025
        • Introducing Test Stage Cycles
      • March 2025
        • Introducing Our New Tricentis-SeaLights Logo!
        • Enhanced Security & Control with SeaLights Tokens
        • Component Level Coverage For All Test Stages
        • Quality Gates - Flexible Failure Criteria
        • Test Gaps: Coverage Focus
  • Features
    • Coverage Dashboard
    • Coverage Report
    • Test Gaps Report
      • Code Changes Calculation
        • Hidden Changes Detection
    • Test Optimization - Savings Breakdown
      • TIA Configuration
    • Settings
      • Token Access & Management
      • Quality Gates
Powered by GitBook
On this page
  • Test Stage Cycles: A New Approach to Test Execution
  • Key Benefits
  • How Test Stage Cycles Work
  • Test Stage Cycle Calculation
  • Value for Customers

Was this helpful?

  1. Intro to SeaLights
  2. Technical Overview

Test Stage Cycle

Test Stage Cycles: A New Approach to Test Execution

SeaLights recognizes the complexities and inefficiencies often associated with traditional testing practices. To address these challenges, we have introduced Test Stage Cycles.

Test Stage Cycles represent the execution of a collection of tests from the same test stage against a specific lab, independent of the Application Under Test (AUT). This concept introduces a level of abstraction that decouples test execution from the build itself, providing greater flexibility and value for customers, with more efficient test re-runs and targeted recommendations.

Key Benefits

  • Faster Value Realization: By separating test execution from the build process, customers can more quickly realize the benefits of SeaLights, including improved test efficiency and recommendations.

  • Reduced Onboarding Effort: In the future, Test Stage Cycles will further simplify the onboarding process, requiring less effort and coordination from multiple teams.

How Test Stage Cycles Work

  1. Test Stage Definition: Define test stages within your SeaLights project.

  2. Data Collection: SeaLights collects data on test execution, coverage (of the applications running on the same lab), and other relevant metrics.

  3. Analysis and Recommendations: The system analyzes the data to provide recommendations for future test cycles, focusing on failed tests and recommended tests that were not executed (assuming the builds of the apps running on the lab didn't change).

Test Stage Cycle Calculation

Test Stage Cycles are automatically calculated based on the following criteria:

  • Explicit Definition (via API): If customers use the SeaLights API to explicitly define a Test Stage Cycle, the start and end points are determined by these API calls.

  • Implicit Calculation: In the absence of explicit API calls, Test Stage Cycles are calculated automatically based on:

    • Deployments: A new Test Stage Cycle is created when a deployment occurs, capturing all test executions initiated after the deployment.

    • Timeout: If no test executions are open within a specified timeout period, the current open Test Stage Cycle will be closed and a new one will be created as soon as a new execution will be started.

This approach ensures that Test Stage Cycles accurately reflect the actual test execution patterns within your environment, allowing for granular analysis and optimization.

Value for Customers

  • Optimized Re-Runs: Reduce the time and effort required for re-runs by focusing on relevant tests. When re-running the same test stage, Test Stage Cycles enable SeaLights to provide more targeted recommendations, focusing only on failed tests and recommended tests that were not previously executed.

  • Granular Analysis: Analyze coverage data and test execution data at the Test Stage Cycle level, gaining deeper insights into test execution performance.

Test Stage Cycles provide a powerful mechanism for managing and analyzing test execution within SeaLights. By understanding the concept of Test Stage Cycles and leveraging their benefits, customers can optimize their testing processes and achieve greater efficiency and effectiveness.

PreviousTechnical OverviewNextFAQ

Last updated 1 month ago

Was this helpful?