Holmes vs Spur

Spur is an AI QA engineer for web and mobile apps.Holmes starts free, with its prices on the website.

Both write tests in plain English, explore past the scripted path and check pull requests. Spur already covers real devices and offers hands-on support up to full test management. Holmes adds public prices and a free start, context from specs and designs, and a plain-language summary of every release.

€250 in free credits · No credit card

What Holmes adds to Spur

  1. Public prices and a free start

    Holmes publishes its Free, Starter and Team prices, and you can set it up yourself in under ten minutes with €250 in free credits. Spur's docs point to a demo for pricing, and most teams start with a 1 to 2 week proof of concept.

  2. Context from specs, designs and analytics

    Both read the code change and linked tickets. Holmes also reads the spec in Notion or Confluence, the design in Figma and your top pages in PostHog before it decides what to test.

  3. A summary of every release

    When something ships, Holmes writes what changed in plain language, then tests the journeys the change touched, so the whole team knows what went out.

  4. A second check before you see a bug

    Holmes validates each finding in several stages, and an independent evaluator re-tests borderline issues, so the bugs that reach your team are worth reading.

Holmes and Spur, side by side

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

Holmes compared with Spur
CapabilityHolmesSpur
Testing
How tests are writtenYes: Plain-language goals. No test code to writeYes: Plain English, no code; Playwright, Selenium, qTest and Zephyr cases can be imported[1][2]
Finds bugs nobody scriptedYes: Agents explore and test paths nobody wrote downYes: An exploratory testing agent looks for edge cases[3]
Keeps tests working when the UI changesYes: Flows repair themselves when a label or layout changesYes: Intent-based tests with no selectors; Spur's team helps with edits[4][1]
Web browsersYes: Chromium, Firefox and WebKit, the engine behind SafariYes: Chrome, Firefox, Safari and Edge, at desktop and mobile web viewports[5][13]
Native Android appsYes: Native Android apps on an Android emulatorYes: On cloud-hosted emulators[5][6]
Native iOS appsYes: Native iOS apps on iPhone and iPad simulatorsYes: On cloud-hosted simulators[5][6]
Real devicesNot covered: Not covered. Android emulators and iOS simulatorsPartly: Its homepage shows Spur-owned iPhone and Android racks; its mobile FAQ says tests run on simulators and emulators[1][6]
APIsYes: Every request behind a journey, checked in contextPartly: API call steps inside UI tests, for setup and assertions[2]
AccessibilityYes: WCAG audits in a real browser, with keyboard navigationYes: WCAG scans from axe-core, the accessibility tree and page probes[7]
Workflow
Pull requests and previewsYes: Check and comment on GitHub and Bitbucket pull requests. GitLab supportedYes: A pull request agent picks what to test from the change; runs can target deploy previews[8][9]
SchedulesYes: On every deploy, on a schedule, or by webhookYes: Releases, pull requests, schedules or API calls; a webhook for any CI[1][9]
Context it reads before testingYes: Reads the code change, ticket, spec (Notion, Confluence), design (Figma) and analytics (PostHog)Partly: The code change, pull request description and linked tickets. Figma or Notion aren't on its integrations page[8][10]
Coding agents (MCP)Yes: Start runs and read findings from Claude and Cursor via MCPYes: Hosted MCP server for Cursor, Claude and Copilot[11]
Evidence with each bugYes: Recording, screenshots, console and network logs, steps to reproduceYes: Video replay, screenshots, console and network logs, agent step logs[12]
Where findings goYes: Findings on the pull request, the ticket, Slack, Microsoft Teams and emailYes: Jira, Linear, Azure DevOps, ClickUp, Asana and Slack[10]
Managed serviceNot covered: Not covered. Self-serve, with guided onboarding on Team and upYes: A Slack Connect channel per its homepage (its mobile page says Enterprise); higher tiers include full test management[1][6]
Pricing and security
What you pay forYes: Priced on how much Holmes tests, never on seatsNote: Annual plans on test-run volume, not seats; each viewport and browser counts as a run[1][5]
Entry priceYes: Free plan. Paid plans from €199 ($219) a monthNote: Not published; pricing through a demo[12]
Getting startedYes: €250 in free credits, no credit cardNote: A 1 to 2 week proof of concept on your own site[1]

Holmes sells QA software, so we compete with Spur. We've tried to be fair: every statement about Spur 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. Spur, Home: Spur is a no-code testing platform, so you write all your tests in plain English instead of code. Checked 17 November 2026.
  2. Spur docs, Index: Import existing Playwright, Selenium or other automation scripts and transform them into Spur test steps Checked 17 November 2026.
  3. Spur, Exploratory testing: Exploratory Testing is particularly useful for edge-case testing. It uses a "fuzzier" agent Checked 17 November 2026.
  4. Spur docs, Introduction: No selectors or code. You write Click on Sign In, not an XPath. The agent finds the button on the screen. Checked 17 November 2026.
  5. Spur docs, Viewports: Each viewport and browser combination counts as a separate test run. Checked 17 November 2026.
  6. Spur, Mobile QA: Tests run on cloud-hosted iOS Simulators and Android Emulators. iOS builds must be Simulator builds. Checked 17 November 2026.
  7. Spur docs, Accessibility: Findings come from three sources (**Found by**): axe-core, the accessibility tree, and page probes. Checked 17 November 2026.
  8. Spur docs, PR Agent: Spur reads the code change, the PR description, linked tickets, and your saved settings to decide what to test. Checked 17 November 2026.
  9. Spur docs, CI/CD: Include it to redirect tests to a different URL (such as a deploy preview) without changing your environment settings. Checked 17 November 2026.
  10. Spur docs, Integrations: After you authorize Slack, Linear, Jira, ClickUp, or Asana, Spur returns you to the Integrations page. Checked 17 November 2026.
  11. Spur, MCP: Spur MCP is the glue in your AI SDLC, it wires Cursor, Claude, and Copilot to your validation agent. Checked 17 November 2026.
  12. Spur docs, FAQ: Video Replay: View the entire test run across all tabs Checked 17 November 2026.
  13. Spur docs, Manual runs: Choose which browsers to run your test in: Chrome, Firefox, Safari, or Edge. Checked 17 November 2026.

Questions about Holmes and Spur

What is the main difference between Holmes and Spur?

They are close. Both write tests in plain English, explore past the scripted path and check pull requests. Spur pairs its product with hands-on help from its team. Holmes is self-serve with public prices, reads specs, designs and analytics as well as tickets, and writes a plain-language summary of every release.[1]

Do both test mobile apps?

Holmes tests native Android and iOS apps on emulators and simulators. Spur's mobile page says it tests native iOS and Android apps on cloud-hosted simulators and emulators. Its homepage also shows Spur-owned racks of iPhones and Android devices, so ask Spur which applies to your plan.[6][1]

How does pricing compare?

Spur sells annual plans based on test-run volume, not seats, and each viewport and browser combination counts as a separate run. Mobile pricing also depends on concurrent device slots. Its docs point to a demo for prices. 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.[1][5][6][12]

Who keeps the tests up to date?

Spur says intent-based tests mostly adapt on their own, and its team helps with edits; its homepage promises a dedicated Slack Connect channel, while its mobile page reserves Slack for Enterprise; higher tiers include full test management. Holmes flows repair themselves when a label or layout changes. Holmes is self-serve, with guided onboarding on Team and up.[1][6]

When might Spur be the better fit?

If you want a vendor team to manage your tests, test localized sites from many countries, or file bugs in Azure DevOps, ClickUp or Asana, Spur covers those on its own pages. If you want public prices, a free self-serve start and context from specs and designs, try Holmes.[6][1][10]

Further reading

Evaluating Spur? 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.