> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tester.army/llms.txt
> Use this file to discover all available pages before exploring further.

# Automate Testing

> Choose how to automate your testing: native GitHub PR testing, CI recipes for GitLab and Bitrise, webhooks for any pipeline, or scheduled monitoring.

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 |
| [Bitrise](/mobile/bitrise) | CI recipe | Bitrise builds your mobile app and you want to run a mobile group afterward | Dashboard; optional GitHub reporting when connected |
| [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 |
| [TestRail and JUnit reporters](/integrations/testrail) | Export | You track results in TestRail or a CI test reporter that reads JUnit XML | JUnit XML per group run via the dashboard or API |

<Note>
  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.
</Note>

## 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.
* [Netlify](/integrations/netlify) sends a deploy notification webhook after each successful deploy.
* [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.

## Issue tracking

Connect [Linear](/integrations/linear), [Jira](/integrations/jira), or [ClickUp](/integrations/clickup) to export issues TesterArmy finds as tickets, with severity-mapped priority and a link back to the run evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.