- Different recovery periods by branch. Run a 3-day recovery monitor on
mainfor fast feedback and a 14-day monitor onrelease/*for builds where resolving tests too quickly would be disruptive. - Different actions by scope. Classify tests as flaky on stable branches while only applying labels on PR branches.
- Targeted detection. Scope one monitor tightly to a branch pattern where pass-on-retry noise is high, while leaving a broader monitor in place for everything else.
June
Flaky Tests: Multiple Pass-on-Retry Monitors Per Repository
You can now create more than one pass-on-retry monitor per repository, each with independent settings.
You can now create more than one pass-on-retry monitor per repository.
Previously, each repository was limited to a single pass-on-retry monitor. Now you can add multiple monitors, each with its own branch scope, recovery period, and action. This lets you apply different detection settings to different parts of your test suite.
Common uses:
Merge Queue: Enable or Disable PR State Labels
Previous
Flaky Tests: Test Collections Have Quarantining On by Default
Next