// ci/cd test automation

Block bad deploys with one CI step.

One API call from your pipeline runs the selected generated suites on cloud workers, with evidence and a machine-readable result for your CI workflow.

// the flow

PR merge → tested → evidence in your workflow.

You merge a PR

The merge fires your CI workflow as usual.

CI calls AegisRunner

A single trigger-token API call. We pick up the new commit and start a run.

We run the suite

Generated Playwright tests + audits (a11y, SEO, security, perf) run in parallel on cloud workers.

PR gets the verdict

Pass/fail comment on the PR with deep links into the failure trace. CI gate blocks merge on red.

// integrations

Pipeline-agnostic — works with what you already use.

GitHub Actions

Trigger token + PR comment with results.

GitLab CI

Same trigger token, drop into .gitlab-ci.yml.

Vercel

Deploy hook — every preview deploy gets a scan.

Netlify

Build-success webhook fires the suite.

Custom webhooks

HMAC-SHA256-signed payloads for your own pipeline.

Anywhere via curl

`curl -X POST /api/v1/trigger` — works from anything.

// one call from your ci

It really is one step.

.github/workflows/aegis.yml

- name: Regression test via AegisRunner
  run: |
    curl -X POST https://app.aegisrunner.com/api/v1/projects/$PROJECT_ID/trigger \
         -H "Authorization: Bearer $AEGIS_TOKEN" \
         -H "Content-Type: application/json" \
         -d '{"branch":"${{ github.ref_name }}","wait":true}' \
         --fail

that's it. exit code = build verdict.

// faq

Frequently asked

How fast does a CI run finish?

Runtime depends on case count, browsers, authentication, devices and your plan concurrency. The run page shows progress and duration so your CI timeout can be set from observed data.

Does AegisRunner block deploys on a failure?

You choose. The trigger-token endpoint returns the run result; your CI can fail the job on red. We also post a PR comment with the verdict so reviewers see it without leaving GitHub.

What about parallel runs / concurrency?

Included on every paid plan. Pro runs 5 parallel test workers per project; Business runs 10. No per-minute fees, no per-test pricing.

Can the same suite run locally?

Yes on Pro and Business. The exported suite is plain TypeScript and runs with `npx playwright test` against your own browsers.

Can CI trigger mobile app tests too?

Yes. Mobile suites — generated from your uploaded .apk or .ipa — run from the same trigger token as web suites, and every mobile case executes on a real iOS or Android device. Teams typically fire the web suite on every deploy and the mobile suite on release candidates, since real-device runs take a few minutes per case.

Wire it up in five minutes

Start free CI/CD setup guide