Set Your Test Optimization Strategy

SeaLights now puts you in control of how aggressively your tests are optimized, so you can match the speed of your pipeline to the risk profile of your team.

Selecting Optimization Level

What's New

For Cross-App test stages (e.g. integration, system, and E2E environments), you can now choose from three optimization levels:

• Conservative: runs every impacted test. Best for continuous delivery or hourly deployments.

• Moderate: (recommended default) targets ~80% of the impacted test list, prioritized by risk. Best for standard weekly or bi-weekly release cycles.

• Aggressive: targets ~60%, maximizing savings for teams with high-volume code pushes or a manual QA safety net downstream.

Each level is paired with a Periodic Full Run policy, so you decide how often skipped tests get cleared (daily, weekly, monthly, or custom), keeping savings high without accumulating hidden risk.

All of this is managed from a new Test Optimization Strategy hub: a centralized view of every test stage, its current level, and last month's savings at a glance. Click into any stage for a full month-by-month savings history and performance trends.

Why It Matters

Test Optimization used to be on or off. Now it's a dial. Until now, all test stages were optimized the same way, regardless of how often they run, how much code changes, or how much risk the team can tolerate. Strategy levels change that, letting you configure each stage to match its own context, and the Test Stage Strategy Overview makes the ROI visible over time.

Get Started

• Test Optimization Strategy →

• How test recommendations are generated →