Detect flaky tests MVC

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Tests can sometimes be flaky in the sense that they fail without detecting a real failure in the code. It is time-consuming to manually detect these and run pipelines again to see if tests will succeed. We have now marked which tests are flaky so that development time will ultimately be given back to you.

Problem to solve

Tests can sometimes be flaky in the sense that they fail without detecting a real failure in the code. It is time-consuming to manually detect these and run pipelines again to see if tests will succeed. Teams end up creating processes to avoid flaky tests, but they again increase the time it takes to get code deployed.

Proposal

• Define a flaky test as a test that does not have a 100% pass or 100% fail rate over 7 days. (Similarly how we define it internally)
• Update Test Summary widget to include flaky test level 1 subtext, popover, and level 2 badge in #381799[mr-widget.png]
• Update Tests tab to include a flaky test badge with popover

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.