Rerun tests on GitLab

Configure the GitLab CI/CD 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 GitLab. This removes the need to manually trigger pipelines.

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

Configure the GitLab integration

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

1. Go to the GitLab integration page.
2. Create a GitLab personal access token. In GitLab, go to User settings > Access tokens > Add new token, set an expiry date, and select only the minimal scope needed to trigger pipelines. The api scope is recommended. For details, see GitLab personal access tokens.
3. Enter the token in the form and click Submit.
   
4. Review the token scopes and remove any you don’t need.
5. In your target repository, confirm that the .gitlab-ci.yml file defines a job that BrowserStack can trigger.

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 GitLab