Holmes vs Rainforest QA

Rainforest QA pairs no-code AI tests with human testers.Holmes automates the exploring, on every pull request.

Both draft tests from plain English and repair them with AI. Rainforest is strong where people help: crowd testers, human exploratory testing, a test writing service, and a wide browser matrix on virtual machines. Holmes adds AI agents that explore on their own, automated mobile and API testing, and checks on every pull request.

€250 in free credits · No credit card

What Holmes adds to Rainforest QA

  1. Agents that explore on their own

    Rainforest's exploratory testing is run by human testers, and its AI Test Planner maps paths to propose a test plan. Holmes agents explore your product and test paths nobody wrote down.

  2. Mobile apps and APIs, automated

    Rainforest's docs say native iOS and Android apps are tested by people, not with automation, and API testing isn't on its pages. Holmes runs native Android and iOS apps on emulators and simulators and checks every request behind a journey.

  3. Results on every pull request

    Holmes checks and comments on GitHub and Bitbucket pull requests, GitLab included, and tests preview deployments before you merge. Rainforest runs from CI and on schedules; pull request checks aren't described on its pages.

  4. Prices you can see before a call

    Holmes publishes its Free, Starter and Team prices, with €250 in free credits to start. Rainforest's pricing page leads to a sales conversation.

Holmes and Rainforest QA, side by side

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

Holmes compared with Rainforest QA
CapabilityHolmesRainforest QA
Testing
How tests are writtenYes: Plain-language goals. No test code to writeYes: Plain-English prompts draft steps you edit in a no-code visual editor[1][2]
Finds bugs nobody scriptedYes: Agents explore and test paths nobody wrote downPartly: Exploratory testing by human testers; AI agents map paths to propose a test plan[3][4]
Keeps tests working when the UI changesYes: Flows repair themselves when a label or layout changesYes: AI regenerates failing steps and updates the test; branching lets you approve changes[5][6]
Other browsersYes: Chromium, Firefox and WebKit, the engine behind SafariYes: Chrome, Safari, Edge, Firefox, Brave and IE 11 on Windows and macOS virtual machines[7]
Native Android appsYes: Native Android apps on an Android emulatorPartly: By human testers on simulators; automation covers the web[8][9]
Native iOS appsYes: Native iOS apps on iPhone and iPad simulatorsPartly: By human testers on simulators; automation covers the web[8][9]
APIsYes: Every request behind a journey, checked in contextNot described: Not on its pages. API testing
AccessibilityYes: WCAG audits in a real browser, with keyboard navigationNot described: Not on its pages. WCAG audits
Visual testingPartly: Compares the Figma design with what shipped. No pixel-diff baselinesPartly: Steps match on screenshots, so visual changes fail a test; no baseline comparison described[10]
Workflow
Pull requests and previewsYes: Check and comment on GitHub and Bitbucket pull requests. GitLab supportedNot described: Not on its pages. Pull request checks or preview deployments
SchedulesYes: On every deploy, on a schedule, or by webhookYes: On demand, on a schedule, or from the CLI, CircleCI and GitHub Actions[11][1]
Context it reads before testingYes: Reads the code change, ticket, spec (Notion, Confluence), design (Figma) and analytics (PostHog)Not described: Not on its pages. Specs, designs or analytics
Coding agents (MCP)Yes: Start runs and read findings from Claude and Cursor via MCPYes: MCP server for Claude Code, Cursor and Windsurf[12]
Evidence with each bugYes: Recording, screenshots, console and network logs, steps to reproduceYes: AI failure explanations, repro steps, video, HTTP and browser logs[10]
Where findings goYes: Findings on the pull request, the ticket, Slack, Microsoft Teams and emailYes: Email, Slack and Microsoft Teams; Jira tickets created on failure[10][13]
Pricing and security
Entry priceYes: Free plan. Paid plans from €199 ($219) a monthNote: Not listed; the pricing page leads to a sales call[14]
Getting startedYes: €250 in free credits, no credit cardYes: Free trial[1]
Managed serviceNot covered: Not covered. Self-serve, with guided onboarding on Team and upYes: Test Writing Service, a crowd Tester Community and exploratory testers[15][8]
Where it runsYes: EU company (Ghent, Belgium), GDPR compliantNote: Google Cloud; test virtual machines at Hetzner and LeaseWeb[16]

Holmes sells QA software, so we compete with Rainforest QA. We've tried to be fair: every statement about Rainforest QA 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. Rainforest QA, Home: Use our visual editor to tweak AI-drafted steps, add assertions, or insert logic with no specialized skills needed. Checked 17 November 2026.
  2. Rainforest QA, AI-accelerated testing: Use plain-English prompts to generate automated test scripts in seconds. Checked 17 November 2026.
  3. Rainforest QA docs, Exploratory testing: When you start using exploratory, Rainforest recruits 4 dedicated testers and with each successive run, they're able to gain familiarity with your application and improve their ability to identify issues. Checked 17 November 2026.
  4. Rainforest QA docs, AI Test Planner: We deploy 7 agents that attempt to navigate as many accessible paths as they can discover. Checked 17 November 2026.
  5. Rainforest QA docs, Self-healing tests: If regenerated test steps successfully self-heal, then Rainforest automatically updates your test to the new, passing state, saving you time on test maintenance. Checked 17 November 2026.
  6. Rainforest QA docs, Approving self-healing updates: By default, all tests will be self-healed automatically. Checked 17 November 2026.
  7. Rainforest QA docs, Supported platforms: Rainforest desktop web platforms are virtual machines (VMs) on which web regression tests can be run. Checked 17 November 2026.
  8. Rainforest QA docs, Human-powered testing: Rainforest only supports testing of native iOS and Android phone and tablet applications using humans, not with automation. Checked 17 November 2026.
  9. Rainforest QA docs, Getting started FAQ: Moreover, mobile device support includes simulators for Apple and Android devices. Checked 17 November 2026.
  10. Rainforest QA, No-code test automation: Get AI-generated explanations of test failures, repro steps, video recordings, HTTP logs, browser logs, and more debugging insights. Checked 17 November 2026.
  11. Rainforest QA, Platform: Run automated tests on-demand or on a schedule, or hook right into your CI tool. Checked 17 November 2026.
  12. Rainforest QA docs, MCP: Rainforest's MCP server lets you generate and run tests directly from AI-powered coding tools like Claude Code, Cursor, or Windsurf Checked 17 November 2026.
  13. Rainforest QA docs, Jira integration: Rainforest supports using Jira to automatically create a ticket when a test fails. Checked 17 November 2026.
  14. Rainforest QA, Talk to sales: See how Rainforest fits your team Checked 17 November 2026.
  15. Rainforest QA docs, Test Writing Service: Rainforest’s Test Writing Service (TWS) offloads the tasks of writing and maintaining tests and puts them in the hands of our QA experts. You are allowed up to 20 tests at a time. Checked 17 November 2026.
  16. Rainforest QA, Security: Our main application, API, and databases are powered by Google Cloud Platform (GCP). Checked 17 November 2026.

Questions about Holmes and Rainforest QA

What is the main difference between Holmes and Rainforest QA?

Rainforest combines no-code automation with human testing: crowd testers, exploratory testers and a test writing service. Its automation runs web tests on Windows and macOS virtual machines. Holmes is self-serve and automated end to end: AI agents test web apps, mobile apps and APIs from plain-language goals, explore on their own, and report on every pull request.[8][15][7]

Does Rainforest use people or AI?

Both. AI drafts and self-heals tests, and its Tester Community of trained human testers runs plain-text tests on demand. Exploratory testing uses 4 dedicated testers. Holmes uses AI agents only, with no crowd or managed team.[5][8][3]

Do both test mobile apps?

Rainforest's docs say native iOS and Android apps are tested by human testers on simulators, not with automation. Holmes tests native Android and iOS apps automatically, on emulators and simulators.[8][9]

How does pricing compare?

Rainforest offers a free trial, but its site shows no prices; the pricing page leads to a sales conversation. 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 and priced on how much Holmes tests.[1][14]

When might Rainforest QA be the better fit?

If you want human testers in the loop, a team to write tests for you, Safari, Edge, Brave or Internet Explorer 11 on virtual machines, or tests that reach beyond the browser window, Rainforest covers those on its own pages. If you want AI agents that explore on their own, automated mobile and API testing, and results on every pull request, try Holmes.[8][15][7][10]

Further reading

Evaluating Rainforest QA? 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.