> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.tester.army/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.tester.army/_mcp/server.

# Automate Testing

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

## Choose an automation path

| Path                                                               | Integration level | Use it when                                                                   | Results                                             |
| ------------------------------------------------------------------ | ----------------- | ----------------------------------------------------------------------------- | --------------------------------------------------- |
| [GitHub](/integrations/github)                                     | Native            | Your repository is on GitHub.com and you want PR-aware testing                | Dashboard, GitHub checks, and PR comments           |
| [GitLab CI](/integrations/gitlab-ci)                               | CI recipe         | GitLab deploys your application and can call TesterArmy afterward             | Dashboard; no native GitLab MR status or comment    |
| [Any CI or custom deployment](/integrations/custom-infrastructure) | Webhook or API    | You use Jenkins, Buildkite, GitHub Actions, a shell script, or another system | Dashboard; optional GitHub reporting when connected |
| [Scheduled monitoring](/run/production-monitoring)                 | Native schedule   | You want recurring production or staging checks                               | Dashboard 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](/run/groups).
3. Configure the target [environment](/guides/environments) 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](/integrations/vercel) works with the native GitHub flow and verifies the selected Vercel project.
* [Coolify](/integrations/coolify) sends a provider webhook after deployment.
* Other providers should call TesterArmy from their deployment pipeline using [Any CI or Custom Deployment](/integrations/custom-infrastructure).

## Notifications

Connect [Slack](/integrations/slack), [Discord](/integrations/discord), or [email](/integrations/email) after the trigger works. Notifications report completed group runs; they do not replace the full run evidence in the TesterArmy dashboard.