CI pipelines and mobile builds

GitLab CI integration

The agents test every GitLab CI deployment once the deploy job finishes, on staging or a per-branch review app.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Response

What the job gets back

The testerarmy job posts to the group's signed webhook after the deploy job and receives the queued run IDs, while steps, videos and issues land in the TesterArmy dashboard.

GitLab CI · .gitlab-ci.yml

release / main

testerarmy needs deploy_staging

build
deploy_staging
testerarmy

TesterArmy · Runs accepted

curl --fail-with-body -X POST "$TESTERARMY_WEBHOOK_URL" -H "Content-Type: application/json" -d '{"commitSha": "'"$CI_COMMIT_SHA"'", "projectEnvironmentId": "'"$TESTERARMY_ENVIRONMENT_ID"'"}'▸

{
  "received": true,
  "status": "queued",
  "runIds": ["uuid-1", "uuid-2"],
  "count": 2
}

[02] Setup

How it works

Setup is the group's Webhook menu on the project's Tests tab. TesterArmy shows the webhook secret once, so copy the URL straight into a masked GitLab CI/CD variable.

Group the tests to automate

Create and manually run the tests to automate, add them to a test group, then switch on the group's signed webhook and copy its URL.

Store the CI/CD variables

Add the URL to GitLab CI/CD variables as a masked variable, and for a stable staging URL store a saved environment's ID alongside it.

Add the testerarmy job

Add a testerarmy job that needs the deploy job and posts the commit SHA plus the environment ID or review app URL.

Read the setup docsThe docs cover staging and review app recipes, the response format, and fixes for 401 and 403 errors.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

The same group webhook serves any other CI. Webhook runs post failure summaries to Slack, review apps behind Cloudflare Access need saved bypass headers, and issues export to Linear.

CI webhooksJenkins, Buildkite, CircleCI or a shell script triggers a group with one request.SlackGroup run summaries with a link per run land in a Slack channel.Cloudflare Zero TrustSaved bypass headers let the agents reach staging behind Cloudflare Zero Trust.LinearIssues the agents find become Linear tickets through one shared project-wide connection.

[04] FAQ

Questions

Put the flows to protect in a TesterArmy test group, enable its signed webhook, and add a testerarmy job that needs the deploy job and posts to it after each deployment.

TesterArmy does not post GitLab commit statuses or merge request comments. Results live in the dashboard, and a failed webhook run sends a summary to connected Slack or Discord, with email as fallback.

A successful response means the runs were accepted and queued, and it returns their run IDs. Pipelines that need to poll individual results use the API-key group-run endpoint instead.

Tests are plain-language steps that you create and run once by hand in TesterArmy, then add to a group. The GitLab job carries only the webhook call that triggers that group.

[05] Start on GitLab CI

Test the next GitLab deployment

Group the tests, switch on the webhook, add one job after deploy, and the next pipeline queues every enabled test in the group.