Integration: GitHub Actions
AI testing in GitHub Actions
Available
One workflow step runs the suite and reports a pass, fail or healed status per test as a check on the pull request.
Add one job step to your GitHub Actions pipeline that runs npx aitp run with the tags you want, and pass AITP_TOKEN and your test credentials from GitHub Actions's secret store.
Exit codes follow the CLI: 0 pass, 1 fail, 2 healed steps pending review. The pipeline step fails on 1 and, with ci.failOnHealedPending: true, on 2.
Add --cloud to run in hosted browsers in the EU or US region, or leave it out to run in Chromium on the CI machine.
1- name: Run E2E2 run: npx aitp run --tag smoke --cloud3 env:4 AITP_TOKEN: ${{ secrets.AITP_TOKEN }}5 TEST_EMAIL: ${{ secrets.TEST_EMAIL }}6 TEST_PASSWORD: ${{ secrets.TEST_PASSWORD }}What GitHub Actions documents
- After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. [GitHub]
Questions
How do I run end-to-end tests in GitHub Actions?
Add a step that runs npx aitp run --tag smoke --cloud with AITP_TOKEN and your test credentials as secrets. The step is shown on this page.
Can the check block a merge?
GitHub can require status checks to pass before merging into a protected branch. Making the check required is your branch protection setting; the platform does not block merges by itself.
Can I run the tests without the cloud?
Yes. Without --cloud the tests run in Chromium on the GitHub Actions runner.
Request early access
Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.