Rerun tests on GitHub Actions

Configure the GitHub Actions integration so you can rerun failed tests from the Test Reporting & Analytics dashboard.

BrowserStack Test Reporting & Analytics lets you rerun failed tests directly from the dashboard after you integrate GitHub Actions. This removes the need to manually trigger workflow runs.

Before you proceed, complete the main setup to rerun failed tests: Rerun failed tests with Test Reporting & Analytics.

Configure the GitHub Actions integration

Each user who wants to trigger reruns must complete this setup:

1. Go to the CI/CD integration page and click Connect under GitHub Actions.
2. Sign in with OAuth, or create a GitHub personal access token (classic). To create a token, do the following in GitHub:
   • Go to Settings > Developer settings > Personal access tokens > Tokens (classic) > Generate new token.
   • Set an expiry.
   • Grant only the repo and workflow scopes needed to trigger workflow runs.
3. Enter the token in the form and click Submit.
4. Review the token scopes and remove any you don’t need.
5. Confirm that the BrowserStack app is installed in your repository. If the app isn’t installed, see GitHub’s guide to installing GitHub Apps.
6. In your target repository workflow file, confirm that the workflow has a workflow_dispatch trigger so that BrowserStack can pass the required inputs during a rerun.

Trigger reruns

After you complete the CI configuration, follow these steps to rerun failed test cases:

1. Go to the Test listing to view failed test cases.
2. Hover over the failed test name to display the action icons.
   
3. Click the rerun icon to open the rerun options.
   
   

Related topics

• View build reports in GitHub Actions