Introducing Test Stage Cycles
Last updated
Was this helpful?
Last updated
Was this helpful?
SeaLights is excited to announce a new concept: Test Stage Cycles. This new feature revolutionizes how we manage and analyze test execution, empowering you to achieve greater efficiency and insight.
Test Stage Cycles represent the execution of a set of tests from the same test stage, independent of the specific build. By decoupling test execution from the build process, Test Stage Cycles enable more granular analysis and optimized test re-runs.
Learn how Test Stage Cycle work.
The Coverage Dashboard now offers a granular view of Test Stage Cycles data, for each build and test stage. You can now view detailed information about each test stage cycle, including the number of tests, pass/fail rates, and execution times.
The Savings Breakdown page now offers a Test Stage Cycles view, providing a detailed breakdown at the Test Stage Cycle level.
Note: The choice of view (Test Cycles or Build) is independent of the TIA recommendation mode. You can switch between these views regardless of whether TIA recommendations are based on builds or Test Stage Cycles.
Build View: Each build card now displays the number of associated Test Stage Cycles, providing a quick overview of the test activity within that build.
Test Stage Cycle View: Each Test Stage Cycle is represented by an individual card, allowing you to drill down into specific test executions. View details about each test within a Test Stage Cycle, including its status, code changes, and recommendations.
The associated build is clearly indicated on each Test Stage Cycle card, providing context for the test execution.
A new tab is available when on a Build View. For each given build you can now see the list of Test Stage Cycles with their status, number of tests and test overview.
The Build View now includes a new tab that provides detailed information about the Test Stage Cycles associated with a specific build. This allows you to see the status of each Test Stage Cycle, including whether it's completed or still running, and gain insights into the number of tests executed within each Test Stage Cycle.
The charts within the Savings Breakdown have been updated to provide more granular insights at the Test Stage Cycle level. When viewing data in Test Stage Cycle mode, charts will display information specific to individual test stage cycles.
You can now choose whether to base TIA recommendations on builds or Test Cycles.
Build Based Recommendations: If multiple test runs are associated with the same build, they will share the same set of recommended tests. This approach may lead to redundant test executions, especially for frequently re-run builds (e.g. re-running passed tests, even though no code changes were made).
Test Cycle Based Recommendations: Recommendations are generated for each Test Stage Cycle, focusing on tests that failed or were not executed in previous runs within the same build. This approach optimizes test execution by avoiding unnecessary test re-runs.
By leveraging Test Stage Cycles and the enhanced features in the Savings Breakdown, you can optimize your testing processes, reduce costs, and improve software quality.
