Use the Repositories page to gain insights into test trends in your repositories or debug issues by investigating individual commits.
Test performance and trends
The Repositories view displays aggregated health metrics for the default branch of each repository. This view is useful for gaining a high-level overview of test performance and trends across your organization’s repositories.
Use the Repositories page to:
See the total number of flaky tests in each repo.
Track whether tests are becoming more or less unreliable over time.
See the test status for the most recent commit in each repo.
See how many A test service is a group of tests associated with a project or repo. It contains all the individual tests for your code, optionally organized into test suites, which are like folders for your tests.Glossarys are associated with each repo.
To filter the list down to only repositories that you have committed to, toggle My Repositories and enter the email address associated with your GitHub account. You can enter multiple email addresses. Edit your address later by clicking Edit Authors.
Investigate a repository
Select a repository to gain granular insights into its test performance. Use the Branch, Test Service, and Env drop-downs to filter for the desired data. Selecting the wildcard (*) filter gives you an aggregated view across that category.
The page for a specific repository gives you access to:
Latest Commit: Test status and performance for the latest commit.
Commits: A list of recent commits and their test statistics.
Test Services: A summary of any test services you’ve added to the repo.
Flaky Tests: Insights into flaky tests in the repo.
Test Regressions: Insights into A test run is marked as a regression when its duration is both five times the mean and greater than the max duration for the same test in the default branch. Additionally, the test run must have a minimum duration of 500ms to be considered a regression.Glossarys.
Test Performance: See which tests have become faster or slower over time.
Common Error Types: See the most common error types in the repo.
All Test Runs: Explore all test runs in the repo.
Repository settings
The Test Optimization settings page gives you an overview of the features enabled on each of your repos together with any overrides you’ve applied. Select a repo to configure the following repository capabilities:
GitHub Comments: Show summaries of your test results directly in pull requests.
Auto Test Retries: Retry failing tests to avoid failing your build due to flaky tests.
Select the test service you want to apply an override to and expand it to view the available settings.
Toggle the desired settings.
You can view the number of overrides in effect on each repo from the settings page.
Debugging commits
Use the Branches view to investigate and debug issues introduced by individual commits.
The Branches view table shows the most recent update to each of your branches. For each branch, the table includes:
The associated repository, branch, test service and environment
Counters for failed, new flaky, skipped, and passed tests
A counter for regressions
The total time for test runs
When the branch was last updated
To filter the list down to only branches that you have committed to, toggle My Branches and enter the email address associated with your GitHub account. You can enter multiple email addresses. Edit your address later by clicking Edit Authors.
Debugging
To debug a commit, select a branch to open the Commit Overview page. The commit overview lists details such as the pull request where the commit was introduced, as well as modified files, test status, and test performance.
From this page, you can also access:
Failed Tests: A list of failed tests. Select a test for details and traces.
New Flaky Tests: A list of new flaky tests introduced in the commit.
Test Regressions: Insights into A test run is marked as a regression when its duration is both five times the mean and greater than the max duration for the same test in the default branch. Additionally, the test run must have a minimum duration of 500ms to be considered a regression.Glossarys introduced by the commit.
Test Performance: See how the commit affects test performance.
Related Pipeline Executions: See the CI pipeline executions for the commit.
All Test Runs: Explore all test runs for the commit.
Further reading
Additional helpful documentation, links, and articles:
