TestDriver

AI QA engineer that runs every pull request in a real desktop sandbox

Intermediate
Screenshot of TestDriver, AI QA engineer that runs every pull request in a real desktop sandbox

What is TestDriver?

TestDriver is an AI QA engineer for GitHub that runs each pull request in a real desktop sandbox, generates end-to-end Vitest tests, self-heals when the UI changes, and opens a PR with the new coverage.

TestDriver is an AI-driven end-to-end testing service built around GitHub pull requests. Instead of only reading a diff, it launches the application in a real desktop sandbox, interacts with the interface the way a person would, and reports whether the changed behavior actually works. Tagging @testdriverai in any GitHub repo triggers the agent, which then writes UI tests and flags regressions before code is merged. The workflow starts with a vision agent that reads the pull request diff to understand what changed. It then generates tests from that content, clicking, typing and reading the screen without relying on selectors or DOM access. Once a test passes, the agent opens a separate pull request containing the generated test file, so the team reviews and approves coverage like any other code change. The tests are plain Vitest files, which means they run locally and in existing CI pipelines across web, desktop and browser extension targets on real virtual machines. Maintenance is handled through self-healing. When a cached element no longer matches because the layout or styling moved, the tool asks the AI to locate it again, updates the cache and continues. For failures, the dashboard offers video replays, network logs with headers and payloads, CPU and memory metrics, and a step-by-step action log. Pass rates, flaky tests and failure trends are tracked over time, and results can be exported as JUnit XML for other reporters. The product suits engineering teams that host code on GitHub and want automated QA on every change, particularly those testing apps they cannot easily instrument: third-party web apps, Chrome extensions, native desktop applications, VS Code extensions, canvas and video content, and OAuth flows. Compared with AI code review tools, it executes the app rather than inspecting text. Compared with Playwright-based agents or screenshot diffing, it covers desktop and mobile-style flows and adapts to UI changes. Pricing is per seat plus metered testing minutes, with a custom pilot for enterprise needs.

How do you use TestDriver?

  1. 1Start a Pro trial
    Begin the free 14-day Pro trial from the checkout page and connect your GitHub account to the console.
    TestDriver — Start a Pro trial
  2. 2Connect a repository
    Use the setup flow to link a GitHub repo so TestDriver can see pull requests, or create a first test manually from the homepage button.
    TestDriver — Connect a repository
  3. 3Tag the bot on a pull request
    Mention @testdriverai in a pull request. The agent reads the diff, runs the app in a sandbox, and generates tests for the change.
  4. 4Review the generated test PR
    Open the pull request the agent creates with the new Vitest file, check the diff, and approve it to add the coverage to your repo.
  5. 5Wire tests into CI and watch results
    Run the Vitest tests in your existing pipeline, then use replays, logs, and pass-rate trends to debug failures and spot flaky tests.

Pros and cons

Pros

  • Runs the actual application in a real sandbox, catching runtime and visual bugs that diff-only reviewers missAI
  • Generated tests are plain Vitest files, so they work locally and in existing CI pipelinesAI
  • Self-healing re-locates moved elements instead of failing on every layout or style changeAI
  • Video replays, network logs, and action timelines make failed runs quick to diagnoseAI
  • Covers web, desktop, Chrome extensions, and VS Code extensions without needing source accessAI

Cons

  • Built around GitHub; teams on other source hosts get no stated support for the PR workflowAI
  • Metered testing minutes at $0.14 each add variable cost on top of the per-seat feeAI
  • Seats bill automatically for every GitHub user who gets a PR review or runs a test, which can inflate costAI
  • Only 120 testing minutes are included with Pro, which heavy suites may exhaust quicklyAI
  • Unlimited minutes and custom agents require an enterprise pilot at a separate priceAI

How much does TestDriver cost?

Free trial

Pro includes a 14-day free trial, started from the checkout page.

Learn more

Pricing

Pro is $20 per seat per month with 120 testing minutes included, plus $0.14 per additional testing minute. Seats bill for each GitHub user who gets a PR review or runs a test. Enterprise is a $995 30-day pilot.

Learn more

Support

Enterprise pilot includes expert setup and support, enhanced security, and custom code review agents. Support for other plans is not detailed on the homepage.

Learn more

Integrations

Works inside GitHub by tagging @testdriverai, runs as plain Vitest in existing CI pipelines, and exports results to JUnit XML for other reporters.

Features

Automatic PR testing in a real desktop sandbox, AI vision test generation without selectors, tests contributed back as a new PR, plain Vitest output for CI, self-healing element lookup, video replays with network logs, CPU and memory metrics, regression trends, and JUnit XML export.

Frequently asked questions about TestDriver

  • How much does TestDriver cost?
    Pro is $20 per seat per month with 120 testing minutes included, plus $0.14 per additional testing minute. Seats bill for each GitHub user who gets a PR review or runs a test. Enterprise is a $995 30-day pilot.
  • Does TestDriver offer a free trial?
    Pro includes a 14-day free trial, started from the checkout page.
  • How do you use TestDriver?
    The walkthrough on this page covers 5 steps: 1. Start a Pro trial 2. Connect a repository 3. Tag the bot on a pull request 4. Review the generated test PR 5. Wire tests into CI and watch results.
  • What platforms does TestDriver support?
    TestDriver is available on Web App, Windows and MacOS.
  • What does TestDriver integrate with?
    Works inside GitHub by tagging @testdriverai, runs as plain Vitest in existing CI pipelines, and exports results to JUnit XML for other reporters.
  • What are the limitations of TestDriver?
    Built around GitHub; teams on other source hosts get no stated support for the PR workflow. Metered testing minutes at $0.14 each add variable cost on top of the per-seat fee. Seats bill automatically for every GitHub user who gets a PR review or runs a test, which can inflate cost.

Status

StatusActive
Views0
Outbound clicks0
Added10/8/2026

Platforms

Web AppWindowsMacOS

Pricing

SubscriptionFree Trial

Categories