Robot Framework vs TestDriver

Free and open source

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

Free and open source. You pay in engineering time and CI minutes.

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.

Everything, self-hosted

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

Widely used

Robot Framework Foundation · since 2008

Niche

TestDriver

• Non-developers can read and often write the tests, which matters in QA-led organisations.
• Extends far beyond browsers: databases, SSH, serial, network equipment.
• Extremely stable and well-supported in regulated and telecom environments.

• 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.

• The keyword abstraction fights you once logic gets complex; you end up writing Python behind the keywords anyway.
• Verbose syntax and whitespace-sensitive files that are awkward to review in a diff.
• Feels dated next to modern JavaScript tooling, and hiring is harder.

• 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.

QA-led and regulated organisations where readability by non-programmers is a requirement.

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