Rerun tests on GitLab

Learn how to rerun failed tests by integrating GitLab CI/CD with BrowserStack so you can quickly validate fixes.

BrowserStack Test Reporting & Analytics lets you rerun failed tests directly from the dashboard after you integrate GitLab. This removes the need to manually trigger pipelines.

Before you proceed, make sure you have completed the main setup to rerun failed tests: Rerun failed tests with Test Reporting & Analytics.

Configure GitLab integration to enable pipeline triggers

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

1. Open the integration page: Configure GitLab integration.
2. Create a GitLab personal access token (PAT): In GitLab, go to User > Preferences > Access Tokens > Add new token. Set an expiry date and select only the minimal scope (recommended: api) required for triggering pipelines. For details, see GitLab docs on personal access tokens.
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. In your target repository .gitlab-ci.yml, ensure a job can be triggered.

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.