TestDriver vs Katalon Studio

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

From $84 per seat/month (Professional, billed annually; $184 month-to-month)

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.

The seat price is only part of it: CI execution needs add-ons priced separately — Runtime Engine at $145/licence/month and cross-browser or mobile device sessions at $158/session/month — so a parallel CI setup costs several times the headline seat figure.

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

Free plan covers local authoring and execution for web, mobile and API.

Niche

TestDriver

Widely used

Katalon, Inc. · since 2016

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

• One tool spanning web, API, mobile and desktop, which avoids stitching four frameworks together.
• Manual testers become productive in days rather than months.
• Built-in reporting and test management reduce the number of separate purchases.

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

• Record-and-playback suites become brittle at scale unless someone refactors them into keywords and objects.
• Proprietary project format makes migrating away expensive — real lock-in.
• Heavy desktop IDE; version control and code review are awkward compared to plain-text tests.

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

QA teams without dedicated automation engineers that need coverage across several platforms.