# AI Testing Platform

> Tests written in plain English, run in CI, healed when the UI changes, triaged when they fail.

An AI testing platform for teams that ship faster than they can write and maintain test code. Stage: early-access. Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged.

## Capabilities

- [Tests in plain English](https://ai-testing-platform.com/product/plain-english-tests/): A test is a list of steps in plain English in a YAML file; the platform resolves each step against the live page at run time.
- [Runs in CI](https://ai-testing-platform.com/product/ci-integration/): 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.
- [Heals locator and layout changes](https://ai-testing-platform.com/product/self-healing/): When a step no longer resolves because an element moved, was renamed or restyled, the platform re-resolves it, marks the test as healed and records the change for review.
- [Triages failures](https://ai-testing-platform.com/product/failure-triage/): A failed test gets a triage card with the failing step, the page state, the diff from the last passing run and a classification: app bug, test issue, environment.
- [Learns your product (Beta)](https://ai-testing-platform.com/product/learns-your-product/): Builds a map of flows from session recordings, product docs and the codebase to propose tests and resolve ambiguous steps.
- [Finds coverage gaps (Beta)](https://ai-testing-platform.com/product/coverage-gaps/): Compares the flow map with the suite and lists flows without a test, ranked by how often the flow changed in the codebase.
- [Parallel hosted runs](https://ai-testing-platform.com/product/parallel-runs/): Runs tests in parallel on hosted browsers in the selected region with traces kept for the plan's retention window.
- [API steps (Beta)](https://ai-testing-platform.com/product/api-tests/): A step can call an HTTP endpoint and assert on the response, mixed with UI steps in the same test.

Planned items are listed only at https://ai-testing-platform.com/roadmap/.

## Integrations

- [GitHub Actions](https://ai-testing-platform.com/integrations/github-actions/)
- [GitLab CI](https://ai-testing-platform.com/integrations/gitlab-ci/)
- [CircleCI](https://ai-testing-platform.com/integrations/circleci/)
- [Jenkins (Beta)](https://ai-testing-platform.com/integrations/jenkins/)
- [Playwright export](https://ai-testing-platform.com/integrations/playwright/)
- [Jira (Beta)](https://ai-testing-platform.com/integrations/jira/)
- [Linear (Beta)](https://ai-testing-platform.com/integrations/linear/)
- [Slack](https://ai-testing-platform.com/integrations/slack/)
- [Vercel preview deployments (Beta)](https://ai-testing-platform.com/integrations/vercel-previews/)

## Test spec format

File: tests/<name>.test.yaml

```yaml
name: Checkout with a saved card
url: https://app.example.com
tags: [checkout, smoke]
env:
  EMAIL: ${TEST_EMAIL}
  PASSWORD: ${TEST_PASSWORD}
steps:
  - Log in with EMAIL and PASSWORD
  - Open the cart
  - Click "Checkout"
  - Choose the saved card ending in 4242
  - Click "Place order"
  - assert: The order confirmation page shows an order number
  - api:
      get: /api/orders/latest
      expect:
        status: 200
        body.status: confirmed
```

Fields: name (required), url (required), tags (optional list), env (optional map, values from environment), steps (required list). A step is either a plain-English string, assert: <plain English>, or api: with get|post|put|delete, optional body, and expect with status and dot-path body checks. API steps are in beta.

## CLI

```
npx aitp init    # creates aitp.config.yaml and tests/
npx aitp run    # runs all tests locally in Chromium
npx aitp run tests/checkout.test.yaml
npx aitp run --tag smoke --cloud    # runs in hosted browsers
npx aitp run --cloud --region eu
npx aitp heal --review    # lists healed steps since the last run for approval
npx aitp report --last    # opens the last run report
```

Flags: --tag, --cloud, --region eu|us, --browser chromium|firefox|webkit, --headed, --review, --last.
Exit codes: 0 pass, 1 fail, 2 healed steps pending review.
Report file: .aitp/last-run.json

## Config (aitp.config.yaml)

```yaml
project: my-app
baseUrl: https://staging.example.com
browsers: [chromium]
retention: 30d
heal:
  auto: locator, layout     # what is healed without a human
  review: text, order       # what waits for review
ci:
  failOnHealedPending: true
```

## CI step

```yaml
- name: Run E2E
  run: npx aitp run --tag smoke --cloud
  env:
    AITP_TOKEN: ${{ secrets.AITP_TOKEN }}
    TEST_EMAIL: ${{ secrets.TEST_EMAIL }}
    TEST_PASSWORD: ${{ secrets.TEST_PASSWORD }}
```

## Agent setup

```
npx aitp init
npx aitp run
```
Agent reads `tests/*.test.yaml`, writes new specs in the same format, runs `npx aitp run`, and reads the report at `.aitp/last-run.json`.

## Pricing

- Free: $0 per month. Solo developers and evaluation. Includes 3 tests, 200 cloud runs per month, local runs unlimited, 7-day trace retention, community support. Limits: 1 project, 1 user, chromium only.
- Team: $390 per month. One product team. Includes 100 tests, 5,000 cloud runs per month, 3 browsers, healing with review, triage, 30-day retention, 10 users. Limits: 3 projects, 4 parallel runs.
- Scale: $1,290 per month. Several teams, higher run volume. Includes 500 tests, 25,000 cloud runs per month, 12 parallel runs, learns-your-product and coverage gaps (beta), 90-day retention, SSO, 40 users. Limits: 10 projects.
- Enterprise: quoted. Self-hosted runners, custom retention, procurement requirements. Includes everything in Scale, self-hosted runners, custom region, DPA, security review, dedicated contact. Limits: by contract.

Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged.

## What the platform cannot do

The platform runs the tests that were written and reports what passed, failed or was healed. It does not prove that an application has no bugs. Healing applies to locator and layout changes; a changed behaviour fails the test and waits for a human decision. The platform does not replace exploratory testing, accessibility review or security testing.

## Links

- Docs: https://ai-testing-platform.com/docs/
- How it works: https://ai-testing-platform.com/how-it-works/
- Setup for coding agents: https://ai-testing-platform.com/for-agents/
- Pricing: https://ai-testing-platform.com/pricing/
- Security: https://ai-testing-platform.com/security/
- Full text for models: https://ai-testing-platform.com/llms-full.txt
- Contact: hello@ai-testing-platform.com