Rainforest QA vs TestDriver

Quote on request

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

Quote-based. Human-executed runs are billed separately from automated ones and are the expensive component.

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 for a small number of automated tests.

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

Emerging

Rainforest QA · since 2012

Niche

TestDriver

• The human fallback covers scenarios automation genuinely cannot reach.
• Anyone on the team can author a test.
• Results in minutes, integrated into the deployment pipeline.

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

• Human runs get expensive quickly at any real frequency.
• Human testers lack product context, so results need interpretation.
• Web only.

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

Teams that need broad release-gate coverage including flows nobody wants to automate.

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