Holmes vs testRigor

testRigor turns plain-English tests into automation.Holmes finds the bugs you didn't write tests for.

Both write tests in plain English, keep them working as the UI changes, and can review pull requests. testRigor covers more ground: real devices through partners, 3,000+ browser combinations, load testing and on-premise installs. Holmes adds agents that explore for bugs nobody wrote a test for, context from designs and analytics, and console and network logs with every bug.

€250 in free credits · No credit card

What Holmes adds to testRigor

  1. Agents that look for bugs nobody scripted

    testRigor runs the tests you write, or generates them from production usage and a crawler, and its Branch Validation checks a branch against the spec. Holmes agents also explore your product and test paths nobody wrote down.

  2. Context from specs, designs and analytics

    testRigor's Branch Validation reads specs from Jira and Confluence. Holmes reads the code change, the ticket, the spec in Notion or Confluence, the design in Figma and your analytics in PostHog before it decides what to test.

  3. Console and network logs with every bug

    testRigor records runs as video and keeps screenshots. Every Holmes finding comes with a recording, screenshots, console and network logs, and steps to reproduce.

  4. Prices you can see before a call

    testRigor's free Public plan makes tests and results public, and its Pay As You Go price isn't on its site. Holmes publishes its Free, Starter and Team prices, with paid plans from €199 a month.

Holmes and testRigor, side by side

Based on each product's public pages on 17 November 2026. A red cross means testRigor's pages don't describe it, not that it can't be done.

Holmes compared with testRigor
CapabilityHolmestestRigor
Testing
How tests are writtenYes: Plain-language goals. No test code to writeYes: Plain English, written by you or generated with AI; manual test cases can be imported[1][2]
Finds bugs nobody scriptedYes: Agents explore and test paths nobody wrote downPartly: Generates tests by crawling and from how real users use production; no agent that hunts for new bugs[9]
Keeps tests working when the UI changesYes: Flows repair themselves when a label or layout changesYes: No locators; optional Vision AI auto-healing, labelled fixed-by-ai[3]
Other browsersYes: Chromium, Firefox and WebKit, the engine behind SafariYes: 3,000+ browser and device combinations, including Safari and Internet Explorer[2]
Native Android appsYes: Native Android apps on an Android emulatorYes: Native and hybrid apps; emulators on paid plans[1][4]
Native iOS appsYes: Native iOS apps on iPhone and iPad simulatorsYes: Native and hybrid apps; simulators on paid plans[1][4]
Real devicesNot covered: Not covered. Android emulators and iOS simulatorsYes: Through partners such as BrowserStack and LambdaTest[2][1]
APIsYes: Every request behind a journey, checked in contextYes: API tests, with mocking of API calls[2]
AccessibilityYes: WCAG audits in a real browser, with keyboard navigationYes: Checks with Deque Axe[5]
Load testingNot covered: Not coveredYes: Reuses the same end-to-end tests[2]
Workflow
Pull requests and previewsYes: Check and comment on GitHub and Bitbucket pull requests. GitLab supportedYes: Branch Validation comments on GitHub, GitLab and Bitbucket pull requests; CLI runs against a custom URL[6][7]
Context it reads before testingYes: Reads the code change, ticket, spec (Notion, Confluence), design (Figma) and analytics (PostHog)Partly: Jira and Confluence specs for Branch Validation. Figma, Notion or Linear aren't on its integrations page[11]
Coding agents (MCP)Yes: Start runs and read findings from Claude and Cursor via MCPYes: MCP server to list, create and update tests from Claude Code or Cursor[8]
Evidence with each bugYes: Recording, screenshots, console and network logs, steps to reproducePartly: Videos and screenshots of runs; console and network logs aren't on its marketing pages[2]
Where findings goYes: Findings on the pull request, the ticket, Slack, Microsoft Teams and emailYes: Jira tickets; results to Slack, Microsoft Teams, email and test management tools[9][2]
Pricing and security
What you pay forYes: Priced on how much Holmes tests, never on seatsNote: Parallel test infrastructure; no charge per user or per execution[9]
Entry priceYes: Free plan. Paid plans from €199 ($219) a monthNote: Free Public plan, where tests and results are public; Pay As You Go price not listed; 14-day free trial[4][10]
On-premiseNot covered: Not covered. Cloud onlyYes: On the Enterprise plan[9][4]

Holmes sells QA software, so we compete with testRigor. We've tried to be fair: every statement about testRigor comes from its own public pages, linked below with the date we checked them. Products change. If something here is out of date, email support@useholmes.com and we'll fix it.

Sources

  1. testRigor, Home: With testRigor, you can use free-flowing plain English to build test automation. Checked 17 November 2026.
  2. testRigor, Features: Generate tests based on your own documented test cases using Generative AI for Testing. Checked 17 November 2026.
  3. testRigor, AI-based self-healing: If you enable Vision AI and enable Auto-Healing for rules and single commands, testRigor will be able to look on the screen for the alternative way of doing what was intended as opposed to failing. Checked 17 November 2026.
  4. testRigor, Plans: Scale your testing as needed with flexible pay-as-you-go pricing. Checked 17 November 2026.
  5. testRigor, Accessibility testing: Under the hood testRigor uses industry leading Deque Axe Devtools. Checked 17 November 2026.
  6. testRigor, Autonomous Branch Validation: Autonomous Branch Validation supports connections to GitHub, GitLab, and Bitbucket for code, along with Jira and Confluence for specifications. Checked 17 November 2026.
  7. testRigor, Command line: Override the default test suite URL with a custom URL Checked 17 November 2026.
  8. testRigor, MCP server: Create test case: create a new test case from plain-English steps Checked 17 November 2026.
  9. testRigor, FAQ: TestRigor only charges for infrastructure to execute tests for parallelizations. Checked 17 November 2026.
  10. testRigor, About: 14 Day Free Trial, Cancel Anytime Checked 17 November 2026.
  11. testRigor, Integrations Checked 17 November 2026.

Questions about Holmes and testRigor

What is the main difference between Holmes and testRigor?

Both turn plain language into tests that keep working as the UI changes. testRigor is a broad automation platform: web on 3,000+ browser combinations, iOS and Android, Windows desktop and mainframe apps, APIs, SMS and phone calls. Holmes focuses on agents that explore your product, read context from specs, designs and analytics, and report on every pull request.[1][2][4]

Do both review pull requests?

Yes. testRigor's Autonomous Branch Validation checks a deployed branch against the spec in Jira or Confluence and gives feedback on GitHub, GitLab or Bitbucket pull requests. Holmes checks and comments on GitHub and Bitbucket pull requests, supports GitLab, and tests preview deployments before you merge.[6]

Do both test mobile apps?

testRigor tests native and hybrid iOS and Android apps, on emulators and simulators on paid plans and on real devices through BrowserStack or LambdaTest. Holmes tests native Android and iOS apps on emulators and simulators; real devices are not covered.[1][4][2]

How does pricing compare?

testRigor charges for parallel test infrastructure, not for users or executions. Its free Public plan makes tests and results public, Pay As You Go and Enterprise prices are not listed on its site, and there is a 14-day free trial. Holmes has a Free plan, Starter at €199 a month for up to 3 products, and Team from €499 a month, all with unlimited users.[9][4][10]

When might testRigor be the better fit?

If you need real devices, Windows desktop or mainframe apps, Safari and Internet Explorer, load testing, SMS and phone call checks, or an on-premise install, testRigor covers those on its own pages. If you want agents that explore your product with context from your specs, designs and analytics, try Holmes.[1][2][4][9]

Further reading

Evaluating testRigor? See what Holmes finds first.

Your bugs in your inbox, 30 minutes from now.

Free, no scripts, no SDK, and no test account needed to start.