Automate Testing

Automate Testing

View as Markdown

Run a test manually first, then connect the trigger that matches your delivery workflow.

Choose an automation path

PathIntegration levelUse it whenResults
GitHubNativeYour repository is on GitHub.com and you want PR-aware testingDashboard, GitHub checks, and PR comments
GitLab CICI recipeGitLab deploys your application and can call TesterArmy afterwardDashboard; no native GitLab MR status or comment
Any CI or custom deploymentWebhook or APIYou use Jenkins, Buildkite, GitHub Actions, a shell script, or another systemDashboard; optional GitHub reporting when connected
Scheduled monitoringNative scheduleYou want recurring production or staging checksDashboard and configured notifications

GitHub is a native source-control integration. GitLab and other CI systems trigger TesterArmy through a signed group webhook, API, or CLI; they are not native repository integrations.

Before automating

  1. Create and manually run at least one test.
  2. Add the tests to a focused group.
  3. Configure the target environment and test accounts.
  4. Confirm the deployment URL is reachable from the public internet.
  5. Store webhook URLs and API keys as CI secrets.

Preview deployment providers

  • Vercel works with the native GitHub flow and verifies the selected Vercel project.
  • Coolify sends a provider webhook after deployment.
  • Other providers should call TesterArmy from their deployment pipeline using Any CI or Custom Deployment.

Notifications

Connect Slack, Discord, or email after the trigger works. Notifications report completed group runs; they do not replace the full run evidence in the TesterArmy dashboard.