Integration: GitLab CI

AI testing in GitLab CI

Available

A GitLab CI job runs the same CLI command as any other CI system and passes AITP_TOKEN from a CI/CD variable.

Add one job step to your GitLab CI pipeline that runs npx aitp run with the tags you want, and pass AITP_TOKEN and your test credentials from GitLab CI'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.

CI job command

# AITP_TOKEN and test credentials come from GitLab CI secrets$npx aitp run --tag smoke --cloud

What GitLab CI documents

You can configure your GitLab project to require a complete and successful pipeline before merge (the Pipelines must succeed merge check). [GitLab]

Questions

How do I run the tests in GitLab CI?

Run npx aitp run --tag smoke --cloud in a job, with AITP_TOKEN and test credentials as masked CI/CD variables.

Can a failed run stop a merge request?

GitLab projects can require a successful pipeline before merge. That is a project setting your team controls.

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.

Request early access See how it works