Skip to main content
GitLab CI can run a TesterArmy test group after it deploys your application. This is a CI recipe, not a native GitLab repository integration. TesterArmy does not currently connect to GitLab repositories, read merge request diffs, or post GitLab commit statuses and merge request comments. Full results are available in the TesterArmy dashboard.

​
Prerequisites

  1. Create and manually run the tests you want to automate.
  2. Add them to a test group.
  3. Enable the group’s signed webhook and copy its URL.
  4. Add the URL to GitLab CI/CD variables as a masked variable named TESTERARMY_WEBHOOK_URL.
If the deployment URL is stable, create a saved environment and store its ID as TESTERARMY_ENVIRONMENT_ID. For temporary review apps, send the deployment URL as targetUrl.

​
Stable staging environment

Trigger the group after the staging deployment succeeds:
The saved environment supplies the URL and any environment-specific credential overrides.

​
GitLab review app

When the deployment job exposes a temporary review URL, pass it directly:
The review URL must be publicly reachable. Configure site access or custom headers when the deployment is protected.

​
Results and pipeline behavior

The webhook returns the queued TesterArmy run IDs. A successful HTTP response means the runs were accepted, not that every test passed.
  • Full steps, screenshots, videos, and issues appear in TesterArmy.
  • This webhook does not update a GitLab commit status or merge request comment.
  • For a merge request test report or a TestRail import, download the batch as JUnit XML from GET /api/v1/batches/{batchId}/junit and declare the file under artifacts: reports: junit:. See Export to TestRail.
  • commitSha is retained as run metadata. It only enables a GitHub Check Run when the TesterArmy project is separately connected to a GitHub repository containing that commit.
Use the API-key group-run endpoint instead when the pipeline needs richer response metadata or will poll individual run results. Open the API Reference tab for endpoint details.

​
Troubleshooting

​
401 Unauthorized

The secret-bearing webhook URL is incorrect. The plaintext secret cannot be recovered, but you can use Regenerate URL in the group’s webhook menu on the Tests tab and replace the GitLab CI/CD variable. The previous URL stops working immediately.

​
403 Forbidden

The group webhook is disabled. Switch it back On from the group’s Webhook menu on the Tests tab.

​
Tests use the wrong URL or account

Use projectEnvironmentId to select a saved environment and its credential overrides. The environment field only labels the result; it does not select a saved environment.