ChipChat News
Loading…

TestDriver

TestDriver is an AI QA engineer that runs your app in a sandbox on every pull request, tests it with computer vision like a real user and contributes passing Vitest tests back to the repo.

TestDriver website screenshot
Image: testdriver.ai

What is TestDriver?

TestDriver is an AI QA agent that tests software by actually running it. When a pull request is opened, TestDriver reads the change, launches the application in a real sandboxed desktop, interacts with it like a user and reports whether the new behaviour works. When a test passes, it can open a new pull request containing the generated test code so the coverage stays in your repository.

It is built for engineering teams that want end-to-end testing without writing and maintaining brittle selector-based scripts. Because it uses computer vision rather than the DOM, it can test web apps, Chrome extensions, VS Code extensions, desktop applications and content like canvases, PDFs and embedded media.

Key Features of TestDriver

Pull request reviews by running the app

Mention @testdriverai in GitHub or let it run automatically, and the agent generates and executes end-to-end tests based on what the pull request changed.

Vision-based interaction

TestDriver finds elements by describing them, such as "upload button", then clicks, types and checks what appears on screen, so tests do not depend on CSS selectors.

Self-healing tests

When a layout changes and a cached element no longer matches, the AI locates it again and updates the cache, reducing failures caused by cosmetic UI changes.

Plain Vitest output for CI

Generated tests are ordinary Vitest files, so they run locally and in your existing CI pipeline on real virtual machines.

Debugging tools

Failed runs come with video replays, network logs, request details, CPU and memory profiles and a step-by-step action log.

TestDriver Pricing

TestDriver has a cloud Pro plan billed per seat plus metered testing time, and a self-hosted Enterprise plan. A seat is any GitHub user who receives a TestDriver review or runs a test in the billing period. The Pro trial lasts 14 days or 120 testing minutes, whichever comes first; a card is added at checkout but not charged during the trial.

Charges are non-refundable on Pro, while Enterprise is covered by a 30-day money-back guarantee according to the pricing FAQ.

Prices checked on October 27, 2026; check the official pricing page for current plans.

Who Should Use TestDriver?

  • Engineering teams that want automatic end-to-end checks on every pull request.
  • Teams whose UI changes often and whose selector-based tests keep breaking.
  • Developers of Chrome or VS Code extensions and desktop apps that are hard to test.
  • QA teams testing third-party web apps they do not control.

Is TestDriver Worth It?

TestDriver addresses a real pain point: end-to-end tests that are slow to write and break with every redesign. Running the actual app on each pull request, then contributing the passing test back to the repo, is a strong workflow, and the vision approach opens up targets that browser-only tools cannot handle.

Costs need watching, though. Testing minutes are metered at $0.14 each after the trial, seats are billed for every GitHub user who triggers a review, and Windows and Mac desktop targets are reserved for the self-hosted Enterprise plan. AI-generated tests should also be reviewed before merging. For teams that value automated, user-level testing, TestDriver is worth a trial. See the official TestDriver pricing page for full details.