Skip to content
testcritic

Leapwork vs TestDriver

Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.

Entry price

Quote on request

Quote only

From $20 per seat/month (120 testing minutes included, then $0.14/minute)

Free tier

What drives the bill

The metric that actually scales your invoice.

Enterprise quote-based licensing, typically annual and sized by concurrent runners plus authoring seats.

The seat price is the small half of the bill: $20 per seat covers 120 testing minutes, then metering kicks in at $0.14 a minute (about $8.40 an hour). Seats are billed for every GitHub user who gets a PR review or runs a test, and a vision model driving a desktop is slower per test than a headless browser — model the minutes before committing a large suite.

Free tier

Free trial.

Free trial rather than a standing free tier; paid seats include 120 testing minutes a month.

Open source

Self-hostable

No-code authoring

Languages

Codeless
JavaScriptTypeScriptCodeless

Platforms

WebDesktopAPISAPMainframe
WebDesktop

Fits teams

Enterprise
StartupScale-up / mid-market

Adoption

Emerging

Leapwork · since 2015

Niche

TestDriver

Strengths

  • Genuinely usable by non-technical staff — the flowchart model is easier than any script-behind-a-recorder approach.
  • Covers Citrix, virtual desktop and mainframe environments that most tools cannot touch.
  • Doubles as an RPA platform, which can consolidate two budgets.
  • Tests surfaces nothing else reaches — browser extensions, packaged desktop apps, canvas and third-party OAuth screens.
  • No selectors to maintain, so a refactor that renames every class breaks nothing.
  • Runs per pull request in a disposable sandbox rather than against a shared staging environment.

Limitations

  • Flowcharts do not diff or merge, so version control is essentially unusable.
  • Complex logic becomes an unreadable sprawl of blocks.
  • Enterprise pricing with no small-team entry point.
  • A vision model is non-deterministic. Reruns of an unchanged test do not always take the same path, which makes a genuine failure harder to distinguish from a bad frame.
  • Billed by testing hours, and driving a real desktop is slow — a suite that costs pennies on Playwright can cost real money here.
  • Young product with a small community; expect to be an early reporter of your own bugs.

Best for

Enterprises where business users must own automation and Citrix or mainframe is in scope.

Teams testing extensions, desktop apps or canvas-heavy UIs, where selector-based runners simply cannot see the thing under test.

Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.