Overview

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:

Track evolution of flaky tests

Track the evolution of the number of flaky tests with the test_optimization.test_management.flaky_tests out-of-the-box metric. The metric is enriched with the tags below to help you investigate the counts in more detail.

• repository_id
• branch
• flaky_status
• test_codeowners

The branch tag only exists when the test has flaked in the default branch of the repository during the last 30 days. This helps you discard flaky tests that have only exhibited flakiness in feature branches, as these may not be relevant. You can configure the default branch of your repositories under Repository Settings.

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:

1. For the test you are fixing, click Fix this test in the Flaky Test Management UI.
2. Copy the unique flaky test key that is displayed (for example, DD_ABC123).
3. Include the test key in your Git commit title or message for the fix (for example, git commit -m "DD_ABC123").
4. 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

To use Flaky Test Management features, you must use Datadog’s native instrumentation for your test framework. The table below outlines the minimum versions of each Datadog tracing library required to quarantine, disable, and attempt to fix flaky tests. Click a language name for setup information:

Further reading

추가 유용한 문서, 링크 및 기사:

Learn about Test OptimizationDOCUMENTATION Learn about working with flaky testsDOCUMENTATION Flaky Tests OverviewKNOWLEDGE CENTER