AI-Powered E2E Testing · Now with Record Login & IDE Integration

Your app, fully tested.
While you ship.

Give zTester a URL and two user journeys. It discovers your app, generates deep multi-page tests, validates them, and loops through repair until your target pass rate is hit — autonomously.

200+
tests in under 20 min
13–16
step journey tests
80%
target pass rate, autonomous
7
auth types supported
One call. zTester handles the rest.
$ curl -X POST https://ztester.zavecoder.com/api/v1/projects/$ID/autopilot \
  -H "Authorization: Bearer $ZTESTER_API_KEY" \
  -d '{
    "baseUrl": "https://staging.myapp.com",
    "targetPassRate": 80,
    "journeys": [
      "User signs up → verifies email → sees dashboard",
      "Admin creates invoice → sends → marks paid"
    ]
  }'
Autopilot running·discovering → validating → running → 83% ✓

The quality loop

Autonomous, not just automated

zTester doesn't just generate tests — it runs a full improvement cycle until the suite is trustworthy.

01

Context

URL, journeys, and working auth. The readiness gate ensures inputs are strong enough before proceeding.

02

Discovery

ActionExplorer clicks through your app. Journey generator stitches multi-page funnels. Tests start as drafts.

03

Validation

Each draft runs a probe execution. Only tests that pass become active — no silent broken tests.

04

Full Run

Autopilot runs the entire active suite and measures true pass rate against your target.

05

Repair

Failing tests get AI-repaired. Coverage gaps get focused rediscovery. Loops until target hit.

Autopilot session phases

readinessCheck journeys + auth gate
discoveringAI crawls + generates tests
validatingProbe each draft test
runningFull suite CI run
improvingAI repair + focused regen
completedPass rate ≥ target ✓
passRate: 83
totalTests: 297
nextAction: "ready_for_ci"

End-to-end ticket purchase — 13 steps

1.navigate/tickets
2.wait2000ms
3.click[data-testid="ticket-family"]
4.clickbutton:has-text("Continue")
5.clickbutton:has-text("Add")
6.clickbutton:has-text("Checkout")
7.waitForSelector#payment_form
8.fill#card_number
9.clickbutton:has-text("Pay Now")
10.waitForSelector.order-confirmation
11.assertText"Order Confirmed"
12.assertVisible[data-order-id]

Everything included

Built to replace human QA

Every feature exists to keep your test suite healthy without manual work.

Autopilot

Flagship

One API call orchestrates the full cycle: readiness check → source discovery → journey generation → validation → CI run → AI repair → repeat until your target pass rate is achieved.

Record Login

New

Captures a real browser session automatically for email + password or OAuth (Google, GitHub, Microsoft). Other SSO flows use a manual session-cookie paste. Credentials discarded immediately; only the session snapshot is stored.

Journey Tests

Multi-page funnels from your brief — ticket purchase, booking, onboarding. 13–16 step tests that traverse your real app from start to confirmation.

AI Self-Healing

Broken selectors are repaired automatically. The nightly quality loop archives flaky tests, heals degraded ones, and rescues stuck drafts.

Native IDE Integration

New

zTester is wired directly into zGo — run tests, record sessions, and view results without leaving your dev environment. The integration API makes it portable to any IDE via a single capabilities endpoint.

Source Discovery

Reads routes, entities, and form schemas from your GitHub or Bitbucket repo. Generates richer tests and avoids hallucinated selectors.

ActionExplorer

Clicks buttons, fills forms, and observes real state changes. Generates 5–8 step workflow tests with success toasts and validation errors.

Regression Detection

Every run is compared to the previous. Pass→fail regressions and fail→pass recoveries are surfaced immediately in dashboard and webhooks.

MCP Server

20 tools for Claude Desktop and Cursor. Bootstrap, discover, validate, run, and report failures — all via natural language.

Run from anywhere

REST API
Any HTTP client
🖥️
zGo IDE
Native integration
🤖
MCP Server
Claude · Cursor
🔁
CI/CD
GitHub Actions · GitLab
⌨️
CLI
npx @ztester/cli

Integration capabilities API

Any tool can call GET /api/v1/integration to self-discover all endpoints, auth requirements, and example flows — no docs needed.

Explore →

Stop writing tests.
Start shipping features.

Set a target pass rate. Autopilot builds the suite, heals it nightly, and tells you exactly when something breaks.