TestDrive

Autonomous QA — AI agents exercise your real product in a browser, learn its flows, and prove each change delivers what was promised

TestDrive is autonomous QA for your product. Agents drive your real application in a real browser, learn how it works as they go, and tell you — with screenshots, video, and traces — whether the thing you shipped actually does what you said it would.

A pull request that proves itself: A developer opens a PR against the checkout flow. TestDrive picks it up, signs into the preview deployment, walks the six acceptance tests that cover checkout, and posts a verdict with a video of the one that failed — before a human has looked at the diff.

Who Is This For?

You are…	TestDrive gives you…
An engineering team	Acceptance tests on every pull request, without writing and maintaining the whole suite by hand
A product owner	Evidence that delivered work matches the spec, in plain language rather than test output
A QA engineer	Generated Playwright scripts you can read, edit, and keep, plus an agent that handles the flows you haven't scripted yet
A support or CS lead	A way to report a bug from Slack and get an investigated, reproducible answer back

Key Benefits

Benefit	What It Means	Business Impact
It tests the real thing	Runs against a live URL in a browser, signed in as a real user	Catches what unit tests can't — the flow, not the function
It learns your app	Every run records what it discovered about routes, flows, and behaviors	Tests get faster and more accurate the longer you use it
It writes its own scripts	Agent runs can be promoted into Playwright specs you own	A deterministic suite without the authoring cost
It brings evidence	Screenshots, video, traces, network and console logs on every failure	Less time reproducing, more time fixing
It starts from your spec	Generate acceptance tests from a Darcy Project spec or an uploaded document	Coverage that traces back to what was actually promised

How TestDrive Works

Step	What Happens
1. Point it at your app	A workspace holds one product: its URLs, its credentials, its tests, and everything it has learned
2. Describe what must keep working	Each acceptance test is a goal and an expected outcome, written by you or generated from a spec
3. Let it figure out the how	With no script, the agent drives the browser itself. A successful path can be saved as a Playwright script
4. Run it	By hand, on every pull request, on a schedule, or from a webhook your CI fires
5. Read the evidence	Each run produces a report: what passed, what failed, and the screenshots, video, and traces to prove it

Core Concepts

Term	What it is
Workspace	One application under test, with its own URLs, credentials, tests, and knowledge
Application URL	A named target to run against — production, staging, a preview — and the domains TestDrive may touch while testing it
Acceptance test	A goal and an expected outcome. The unit of "this must keep working"
Script	A Playwright spec attached to a test, generated by Darcy or written by you
Run	One execution of a set of tests against one URL, producing a report and evidence
Knowledge	What TestDrive has learned about your app — its routes, flows, elements, and quirks

Getting Started

1

Create a workspace Open TestDrive from the navigation and click Create your first workspace. Name it after the product it will test.

2

Follow the setup guide New workspaces open a setup guide that walks the rest: application URLs, an optional linked Project, credentials, Slack triage, MCP, and your first test. Only the first is required.

3

Add an application URL Point at the environment you want tested and list the domains TestDrive is allowed to reach while it's there. See Workspaces & Application URLs.

4

Give it a way in If your app needs a login, add a credential. TestDrive learns the sign-in once and replays it. See Credentials & Sign-In.

5

Write one test Describe a single thing that must keep working — "a signed-in user can add an item to the cart and check out." See Tests & Scripts.

6

Run it Start a manual run, read the report, and then decide what should trigger it automatically. See Running Tests.

Availability

TestDrive is enabled per organization and per plan, and opening it needs TestDrive permission. If it isn't in your navigation, it isn't turned on for your account — talk to your administrator.

Next Steps

Goal	Documentation
Set up the workspace and its targets	Workspaces & Application URLs
Let TestDrive sign in as a real user	Credentials & Sign-In
Write tests, or generate them from a spec	Tests & Scripts
Run on PRs, schedules, and webhooks	Running Tests
Read a report and its evidence	Results & Evidence
Understand what TestDrive has learned	Application Knowledge
Use it from chat, Slack, and your editor	TestDrive with Darcy