The product

One platform, from the first crawl to the merge gate.

QAce is not a record-and-replay recorder with an AI label. It is an agent that understands your app, writes and runs the tests, explains every failure, and holds the line in CI.

The agent

It drives the browser like a person.

A real cursor moves, clicks, types, and reads the result. A calibrated LLM judge scores each step with a confidence, so a pass means pass.

  • Self-healSelectors relocate by role, text, and context when the DOM shifts, instead of failing on a renamed class.
  • JudgeEvery assertion gets a scored verdict with reasoning, not a brittle string match.
  • VisibleA screen-edge pulse shows the agent is in control. Watch it work, step by step.
step 04 · self-healconfidence 0.96
selector .btn-primary not foundretry
relocated by role “button” + text “Pay”heal
clicked · order total updated180mspass
Coverage

It maps the whole site, not the happy path.

QAce crawls every reachable page, records each interactive element, and keeps a coverage ledger of what is tested and what is not.

  • CrawlAn uncapped whole-site crawl builds a workflow map of pages, buttons, forms, and links.
  • LedgerA living record of tested vs untested flows, so gaps are visible before they bite.
  • PlanA prioritized suite covering happy paths and the edge cases scripts never reach.
coverage ledger38 pages
/checkout · 6 flowscovered
/account · 4 flowscovered
/returns · 0 flowsgap
Code-aware

It reads your repo, then traces the failure to the line.

QAce indexes your codebase for routes, components, and API calls. When a test fails, the report points at the code most likely responsible.

  • IndexRoutes and components are mapped so tests are grounded in how the app is actually built.
  • TraceFailures link to the suspect file and function, not just a screenshot.
  • HandoffEvery report opens with a paste-ready prompt for your coding agent: repro, hypothesis, and where to look.
failure · root-causerun #4187
card decline shows no errorfail
src/checkout/PayForm.tsx:142suspect
error branch never renders toastwhy
What it checks

Far more than “did the page load.”

Turn any category on per project. QAce writes the right kind of test for each.

T1

Functional flows

End-to-end user journeys: sign up, search, add to cart, check out, and every branch in between.

T2

Visual regression

Pixel and layout diffs that catch the shift a functional test would sail right past.

T3

Accessibility (WCAG)

Contrast, labels, roles, and keyboard paths, checked as part of the same run.

T4

Performance

Core Web Vitals plus console and network errors surfaced against every step.

T5

Destructive & exploratory

Turn the agent loose to hunt boundary bugs, double-submits, and broken flows your scripts never cover.

T6

API & mobile

Pure API tests, and native mobile via Appium. One platform, one report.

Where it runs

The same agent, wherever you work.

Author and run tests from the browser, your editor, or CI. They all read the same plan and report to the same place.

S1

Browser overlay

One script tag mounts an in-page panel that maps the app, proposes tests, and runs them live. No server infrastructure required.

S2

Chrome extension

Point it at any site you can open, with no code changes. Ideal for apps you cannot inject a script into.

S3

VS Code extension

A cockpit inside your editor: generate tests, run them, and read failures next to the code that caused them.

S4

Zero-dependency CLI

Wire QAce into any pipeline. JUnit output for your CI dashboard, a status badge for your README.

Reports

Every plan, run, and report leaves the building.

Read a run as a story of steps with scored verdicts, or export the whole thing. Test plans, coverage, and site maps download as CSV, Excel, or PDF, straight from the dashboard.

dashboard · test plan · export
checkout suite · 24 testscsv · xlsx · pdf
qace-test-plan.csvready
qace-coverage.xlsxready
qace-crawl-map.pdfready
The gate

A red status blocks the merge.

QAce runs the suite on every pull request and reports back where your team already looks.

  • PR commentA sticky comment with pass and fail counts, updated on every push.
  • Commit statusA healthy or unhealthy check that can require green before merge.
  • CI nativeJUnit for your dashboard, a badge for your README, exit codes for your pipeline.
github · pull request #218qace/e2e
23 passinghealthy
1 failing · checkoutblocked
Merge blocked until the gate is green
Security & governance

Built for teams that answer to auditors.

Identity & access

SSO and OIDC, SCIM provisioning, MFA, and scoped API keys with rotation. Session and editor keys cannot be rotated, only manual keys can.

Secrets vault

An encrypted vault keeps true secrets server-side. The in-page agent never sees them; reference them by name and QAce resolves them at run time.

Audit & data rights

An immutable audit log of every action, plus GDPR export and delete on request.

Your infrastructure

Run in the cloud, or self-host the whole platform. Object storage is S3-compatible and swappable.

Ready when you are

See it map your app in minutes.

Free to start. Sign up, paste a URL, and watch the first plan write itself.