TestDriver vs Testsigma

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

Free tier available

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.

Pro and Enterprise cloud plans use custom pricing. Request a quote for your team's platform coverage and execution needs. The community edition is free to self-host, with infrastructure and maintenance managed by your team.

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

Apache-2.0 community edition, self-hosted — the GitHub repo is still actively maintained.

Niche

TestDriver

Established

Testsigma Inc. · since 2019

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

• An open-source community edition adds a self-hosted option alongside the managed cloud.
• Natural-language steps are readable by product owners.
• Web, mobile and API in one authoring model.

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

• Structured natural-language steps use a defined syntax; plan time to learn it during onboarding.
• The community and cloud editions differ in feature coverage; check the edition against your requirements.

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

QA teams that want readable web, mobile and API automation, with a choice of managed cloud or self-hosted deployment.