Runs in CI
Run plain-English tests in CI
One CLI command runs a suite in CI and reports a pass, fail or healed status per test as a check on the pull request.
One CLI command runs a suite in CI and reports a pass, fail or healed status per test as a check on the pull request. The job needs the AITP_TOKEN secret and the command npx aitp run --tag smoke --cloud.
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 it does not do
Does not block merges by itself; the branch protection rule is the team's decision.
When it applies
- The team wants an end-to-end gate on every pull request that a non-QA reviewer can read.
- Release cadence rose and manual regression passes no longer fit.
- Coding agents open pull requests and each one needs a check before review.
Questions
Can end-to-end tests be a required status check?
Yes, if your CI host supports required checks. The platform reports the check; making it required is a branch protection rule your team sets. The platform does not block merges by itself.
Which CI systems are supported?
GitHub Actions, GitLab CI and CircleCI. Jenkins is in beta. Any system that can run npx can run the command.
What exit codes does the CLI return?
0 pass, 1 fail, 2 healed steps pending review.
Where do the tests run from CI?
With --cloud they run in hosted browsers in the EU or US region. Without it they run on the CI machine in Chromium.
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.