Reflect vs TestDriver

Free tier available

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

Now sold on a credit model — Premium 5,000 credits a month, Advanced 20,000, Enterprise 40,000, all with unlimited users — and SmartBear does not publish the prices, so you need a quote. Credits are consumed by test runs, so concurrency and suite size drive the bill.

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.

14-day trial.

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

Emerging

SmartBear (formerly Reflect Software) · since 2019

Niche

TestDriver

• Nothing to install; a non-technical colleague can record a regression test in ten minutes.
• Handles file uploads, iframes and email verification, which trip up many no-code tools.
• Transparent published pricing, which is rare in this segment.

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

• Cloud-only, so testing a private environment requires network work.
• Not suited to very large suites or heavy conditional logic.
• Small vendor — check longevity if this becomes critical infrastructure.

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

Startups that need ten critical journeys covered without owning a framework.

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