-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Updated test analytics doc for more details on how to read the data #15494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sfanahata
wants to merge
3
commits into
master
Choose a base branch
from
test-analytics-flaky-clarification
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -90,15 +90,28 @@ Now that you've configured your CI to upload your test results, you can inspect | |
|
|
||
| After your workflow runs, view failed tests in the [failed tests dashboard](https://sentry.io/prevent/tests/?filterBy=failedTests), or in your GitHub pull request comments. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| You can see a complete overview of your test analytics in the [test analytics dashboard](https://sentry.io/prevent/tests/). **Note**: The `All Branches`dashboard refreshes every 24 hours. | ||
| ### Reading Test Analytics Data | ||
| You can see a complete overview of your test analytics in the [test analytics dashboard](https://sentry.io/prevent/tests/). | ||
| **Note**: The `All Branches`dashboard refreshes every 24 hours. | ||
|
|
||
|  | ||
|
|
||
| - `Failed Tests`: Shows all failed tests across all branches. Because of this, the _total run time_ may be higher than the filtered time range selected. | ||
| - `Flaky Tests`: These are tests that go from fail to pass or pass to fail compared to the default branch. This analysis will only run when: | ||
| - The commit is merged | ||
| - The commit is on the default branch (commit.branch == repo.branch) | ||
| - Flake detection is enabled on your yaml (default is true) | ||
| - Either: The repo is public (regardless of plan type); Or: The repo is private, and is above free or team plan types | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @adrianviquez can you fact check this? |
||
| - `Cumulative Failures`: Shows the number of individual test failures, only on the default branch. | ||
|
|
||
| ## Permissions and Repository Tokens | ||
| When configuring Test Analytics, you'll be asked to choose your upload permissions. For GitHub Actions, you can use [OpenID Connect](https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/about-security-hardening-with-openid-connect), or generate a repository token. Using the CLI, generate a repository token. | ||
|
|
||
| You can find a list of repository tokens on the Sentry Prevent [tokens page](https://sentry.io/prevent/tokens/). | ||
|
|
||
|
|
||
| ## Read Next | ||
|
|
||
| <PageGrid /> | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.