Flaky tests are tests that exhibit both a passing and failing status across multiple test runs for the same commit. If you commit some code and run it through CI, and a test fails, and you run it through CI again and the test passes, that test is unreliable as proof of quality code.
Flaky tests introduce risk and unpredictability into your CI system and into your end product. When people have to remember which tests are flaky, they lose trust in their test results, and a tremendous amount of time and resources are wasted on pipeline retries.
Go to the Test Service page to see the Flaky Tests table for a given test service and branch. You can see all of the tests that are flaky in the time frame you have selected.
The app helps you prioritize flaky tests by providing the following information about them:
Once you identify a flaky test you want to fix, click on the test to see links to view the most recent failed test run or the first flaky test run.
If a flaky test has not failed in the past 30 days, it is automatically removed from the table. You can also manually remove a flaky test by clicking on the trash icon that appears when you hover over the test row. It is added again if it re-exhibits flaky behavior.
On the Tests page, select the Branches view.
Filter the table to see branches, services, or commits of interest to you.
Look at the New Flaky column to see the number of new flaky tests that were introduced by the latest commit. These are tests that exhibit flaky behavior and didn’t previously exist in the Flaky Tests table.