PR Comments
Flaky Tests provides summary analytics about tests running on Pull Requests
Last updated
Flaky Tests provides summary analytics about tests running on Pull Requests
Last updated
Flaky Tests can post comments on GitHub pull requests to provide a summary of all the tests run on this PR, across multiple CI jobs or even CI systems, as well as whether those failures are due to flakiness, the history of the failures of that test, and more.
Each GitHub comment has a full summary report, containing all tests that passed, failed, flaked, skipped, and quarantined on this PR.
Each test case also contains the full stack trace attached when opened. You can also click on the Job run link which will take you to the full CI logs.
Pull Request comments are enabled by default. If you wish to disable the comments, you can do so by navigating to the Trunk App > click on your profile > Settings > RepoName. In the Flakey Tests heading, toggle the Summary Flaky Tests Reports setting.
If you wish to set the resource owner to be a GitHub Organization, you should double check that this is allowed by navigating to your GitHub Organization > Settings > Personal access tokens > Settings. Make sure under "Fine-grained personal access tokens", you have "Allow access via fine-grained personal access tokens" selected.
Once the token is created, the Organization admin may need to approve the request for the token. This can be done by going to Github Organization > Settings > Personal access tokens > Pending requests. To confirm that the token was set, you should be able to see it under Active tokens.
If you have the and are test results on pull requests, expect to start seeing comments on your Pull Requests soon. If you prefer not to use the Trunk GitHub App, you can still set up comments on your Pull Requests by providing Trunk with a GitHub access token.
On , for trunk-analytics-user
(or whichever user you wish to use), generate a by navigating to Settings > Developer settings > Personal access token > Fine-grained tokens > Generate new token.
The resource owner should be the GitHub Organization or user that owns the appropriate repositories.
Once the token is generated, go back to the Trunk App () > click on your profile > Settings > Manage (under Organization) > Organization GitHub Token and enter the copied token into the text field, then finally press Submit.
At any point, feel free to reach out to our team .