Three new monitor types — new-test, skipped-test, and slow-test — are now available in Flaky Tests detection. They apply labels based on lifecycle events or performance characteristics, without changing whether a test is marked flaky or broken. The monitors page is now split into two sections to reflect this:Documentation Index
Fetch the complete documentation index at: https://trunk-4cab4936-sam-gutentag-changelog-flaky-tests-stable-br.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
- Health classification monitors — Pass-on-Retry, Failure Rate, and Failure Count. These determine whether a test is healthy, flaky, or broken, and their status flows through the dashboard, CI annotations, and notifications.
- Lifecycle and performance monitors — the three new ones below. They only apply labels and do not contribute to a test’s health status.
- New Test Monitor — labels test cases the first time they appear and keeps the label on for a configurable number of days. Useful for giving brand-new tests a grace period before treating their failures as signal.
- Skipped Test Monitor — labels tests that accumulate a configured number of skipped runs within a time window. Useful for surfacing tests that someone marked as
.skiporxtestand never re-enabled. - Slow Test Monitor — labels tests whose average duration exceeds a configured threshold. Useful for enforcing duration budgets and catching performance regressions before they hit
main.