Test Optimization is not available in the selected site () at this time.
Join the Preview!
Flaky Test Management is in Preview. Complete the form to request access.
Request AccessOverview
The Flaky Test Management page provides a centralized view to track, triage, and remediate flaky tests across your organization. You can view every test’s status along with key impact metrics like number of pipeline failures, CI time wasted, and failure rate.
From this UI, you can act on flaky tests to mitigate their impact. Quarantine or disable problematic tests to keep known flakes from breaking builds, and create cases and Jira issues to track work toward fixes.
Change a flaky test’s status
Use the status drop-down to change how a flaky test is handled in your CI pipeline. This can help reduce CI noise while retaining traceability and control. Available statuses are:
| Status | Description |
|---|
| Active | The test is known to be flaky and is running in CI. |
| Quarantined | Keep the test running in the background, but failures don’t affect CI status or break pipelines. This is useful for isolating flaky tests without blocking merges. |
| Disabled | Skip the test entirely in CI. Use this when a test is no longer relevant or needs to be temporarily removed from the pipeline. |
| Fixed | The test has passed consistently and is no longer flaky. If supported, use the remediation flow to confirm a fix and automatically apply this status, instead of manually changing it. |
Note: Status actions have minimum version requirements for each programming language. See
Compatibility for details.
Investigate a flaky test
For more information about a specific flaky test, use these options in the actions menu at the end of each row:
- View Last Failed Test Run: Open the side panel with the details of the test’s most recent failed run.
- View related test executions: Open the Test Optimization Explorer populated with all of the test’s recent runs.
Create cases for flaky tests
For any flaky test, you can create a case and use Case Management to track any work toward remediation. Click the Create Case button or use the actions menu at the end of the row.
Confirm fixes for flaky tests
When you fix a flaky test, Test Optimization’s remediation flow can confirm the fix by retrying the test multiple times. If successful, the test’s status is automatically updated to Fixed. To enable the remediation flow:
- For the test you are fixing, click Fix this test in the Flaky Test Management UI.
- Copy the unique flaky test key that is displayed (for example,
DD_ABC123). - Include the test key in your Git commit title or message for the fix (for example,
git commit -m "DD_ABC123"). - When Datadog detects the test key in your commit, it automatically triggers the remediation flow for that test:
- Retries any tests you’re attempting to fix 20 times.
- Runs tests even if they are marked as
Disabled. - If all retries pass, updates the test’s status to
Fixed. - If any retry fails, keeps the test’s current status (
Active, Quarantined, or Disabled).
Compatibility
Flaky Test Management features have minimum version requirements for each programming language. The table below outlines the minimum versions needed to quarantine, disable, and attempt to fix flaky tests:
| Language | Quarantine & Disable | Attempt to fix |
|---|
| .NET | 3.13.0+ | 3.17.0+ |
| Go | 1.73.0+ | Not available |
| Java | 1.48.0+ | 1.50.0+ |
| JavaScript | 5.44.0+ | 5.52.0+ |
| Python | 3.3.0+ | 3.8.0+ |
| Ruby | 1.13.0+ | 1.17.0+ |
Further reading
Additional helpful documentation, links, and articles:
