CI pipelines and mobile builds

Test every deploy with TesterArmy

TesterArmy tests every deployment after Jenkins, Buildkite, CircleCI or a shell script posts one request to the group's signed webhook.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Response

What the webhook returns

The pipeline's last job posts the commit SHA and the deployed URL to the group's signed webhook, and TesterArmy answers with the queued run IDs and a count.

Pipeline · deploy, then test

deploy / main

any CI that can send an HTTP request

build
deploy
testerarmy

TesterArmy · Runs accepted

curl --fail-with-body -X POST "$TESTERARMY_WEBHOOK_URL" -H "Content-Type: application/json" -d '{"commitSha": "'"$COMMIT_SHA"'", "targetUrl": "'"$DEPLOY_URL"'", "environment": "staging"}'▸

{
  "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 Tests tab. The deployed URL must be public, because TesterArmy blocks localhost, private IP ranges and internal hostnames.

Verify a test group

Create a test group to run on each deploy and verify it once by hand before the pipeline calls it.

Turn on the webhook

Switch the group's webhook On in the Tests tab, copy the URL while the secret is visible, and store it as a masked CI secret.

Post after each deploy

After deployment the pipeline posts the commit SHA with a saved environment ID or the deployed URL, and TesterArmy queues every enabled test in the group.

Read the setup docsEnable the webhook, pick a saved environment or target URL, call it from any shell, plus troubleshooting.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

GitLab CI has its own webhook recipe. Slack and Discord receive the failure summary after a webhook batch, and Cloudflare Zero Trust bypass headers let the agents reach protected staging.

GitLab CIA signed group webhook runs a test group after GitLab CI deploys.SlackGroup run summaries with a link per run land in a Slack channel.DiscordGroup run summaries with a link per run land in a Discord channel.Cloudflare Zero TrustSaved bypass headers let the agents reach staging behind Cloudflare Zero Trust.

[04] FAQ

Questions

Any CI that can send an HTTP request posts to the group's signed webhook after deploy. TesterArmy then queues every enabled test in the group against the deployed URL and reports in the dashboard.

A staging environment on any infrastructure works when its URL is reachable from the public internet. TesterArmy blocks localhost, private IP ranges and internal hostnames. A saved environment supplies the URL and credential overrides.

The signed webhook creates a GitHub check best effort when commitSha belongs to the repository connected through the GitHub App. It accepts no pull request number, so comments need the API-key runs endpoint with prNumber.

A successful response means TesterArmy accepted the runs and returned their IDs. It does not mean the tests passed. Use curl --fail-with-body so an authentication, validation or usage-limit response fails the CI job.

[05] Start from any CI

Test the next deploy from any pipeline

Switch on the group's webhook, add one request after deploy, and the first deployment comes back with queued runs and results in the dashboard.