Rerun tests on GitHub Actions

Learn how to rerun failed tests by integrating GitHub Actions with BrowserStack so you can quickly validate fixes.

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, make sure you have completed the main setup to rerun failed tests: Rerun failed tests with Test Reporting & Analytics.

Configure GitHub Actions integration for enabling workflow triggers

Follow these steps to configure the GitHub Actions integration for rerun triggers. Each user who wants to use reruns must complete this setup:

1. Open the CI/CD integration page and click Connect in GitHub Actions.
2. Use OAuth to sign in, or create a GitHub Personal Access Token (classic): Settings > Developer settings > Personal access tokens > Tokens (classic) > Generate new token. Set an expiry and grant only the repo (minimal: repo:status) and workflow scopes needed to trigger workflow runs. For details, see Create a personal access token.
3. Enter the token in the form and select Submit.
4. Review the token scopes and remove any you do not need to follow least‑privilege practices.
5. Check if you have the BrowserStack app installed in your repository, and install it if not present, following GitHub’s guide to installing GitHub Apps.
6. In your target repository workflow file (YAML), ensure the workflow has a workflow_dispatch trigger so BrowserStack can pass required inputs when starting a rerun.

Trigger reruns

After you complete the CI configuration, trigger reruns of failed test cases:

1. Go to the Test listing to view failed test cases.
2. Hover over the failed test name.
3. Select the rerun icon.