Dashboard

Learn to find flaky tests and understand their impact using the Flaky Tests dashboard

Trunk Flaky Tests detect flaky tests by analyzing test results. The health of your tests is displayed in the Flaky Tests dashboard.

Key Repo Metrics

Key repo metrics

Trunk Flaky Test provides key repo metrics based on the detected health status of your tests. You'll find metrics for the following information at the top of the Flaky Test dashboard.

Metric	Description
Flaky tests	Number of flaky test cases in your repo.
Broken tests	Number of broken test cases in your repo.
PRs blocked by failed tests	PRs that have been blocked by failed tests in CI.
PRs rescued by quarantining	This figure is available if you have quarantining enabled. This shows the PRs with CI jobs containing quarantined flaky tests that would have failed if all flaky tests had not been quarantined.
Engineering hours saved	Estimated engineering hours saved based on the study The Cost of Interrupted Work, where each context switch to debug a flaky test costs 23 minutes of focused productivity.

These numbers are important for understanding the overall health of your repo’s tests, how flaky and broken tests impact your developer productivity, and the developer hours saved from quarantining tests. You can also view the trends in these numbers in the trend charts.

Tests Cases Overview

You can view a table of all your test cases and their current status in Trunk Flaky Tests.

Filters can also be set on the table to narrow test results down by test status, quarantine setting, ticket status, or by the name, file, or suite name of the test case.

The table is sorted by default by the number of PRs impacted by the case, which is the best way to measure the impact of a flaky test. You can click on each test case to view the test case’s details.

Column	Description
Tests	The file path and name of the test case.
Status	The health status of the test case.
Failure Rate	The percentage of CI runs failed due to this broken or flaky test case.
PRs Impacted	The number of PRs that have been affected by this test case failing in CI.
Last Run	The most recent timestamp for an upload test run.

Test Case Details

You can click on any of the test cases listed on the Flaky Test dashboard to access the test case’s details. On a test's details page, you can find:

• The test's current status

• Visualizations and a timeline detailing the test's health history

• A table of unique failure types for this test

This is in addition to information like ticket status and the current codeowner.

Code Owners

If you have a codeowners file configured in your repos, you will see who owns each flaky test in the test details view. We support code owners for GitHub and GitLabs repos.

You can find the code owners of each test on the top right of the test details screen.

This information will also be provided when creating a ticket with the Jira integration or webhooks.

Failure Types

The Failure Types table shows the history of past test runs grouped by unique failure types.

The Failure Type is a summary of the stack trace of the test run. You can click on the failure type to see a list of test runs labeled by branch, PR, Author, CI Job link, commit hash, duration, and time.

You can click on any of these test runs to see the detailed stack trace:

You can flip through the stack traces of similar failures across different test runs by clicking the left and right arrow buttons. You can also see other similar failures on this and other tests.

Test History

Tests may transition between flaky, broken, and healthy states multiple times over their lifetime. You can see previous changes in the detected health status of a test in Test History, as well as an explanation for why it was detected to have a new state.