Holmes vs Spur
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.
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.
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.
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.
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.
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.
| Capability | Holmes | Spur |
|---|---|---|
| Testing | ||
| How tests are written | Yes: Plain-language goals. No test code to write | Yes: Plain English, no code; Playwright, Selenium, qTest and Zephyr cases can be imported[1][2] |
| Finds bugs nobody scripted | Yes: Agents explore and test paths nobody wrote down | Yes: An exploratory testing agent looks for edge cases[3] |
| Keeps tests working when the UI changes | Yes: Flows repair themselves when a label or layout changes | Yes: Intent-based tests with no selectors; Spur's team helps with edits[4][1] |
| Web browsers | Yes: Chromium, Firefox and WebKit, the engine behind Safari | Yes: Chrome, Firefox, Safari and Edge, at desktop and mobile web viewports[5][13] |
| Native Android apps | Yes: Native Android apps on an Android emulator | Yes: On cloud-hosted emulators[5][6] |
| Native iOS apps | Yes: Native iOS apps on iPhone and iPad simulators | Yes: On cloud-hosted simulators[5][6] |
| Real devices | Not covered: Not covered. Android emulators and iOS simulators | Partly: Its homepage shows Spur-owned iPhone and Android racks; its mobile FAQ says tests run on simulators and emulators[1][6] |
| APIs | Yes: Every request behind a journey, checked in context | Partly: API call steps inside UI tests, for setup and assertions[2] |
| Accessibility | Yes: WCAG audits in a real browser, with keyboard navigation | Yes: WCAG scans from axe-core, the accessibility tree and page probes[7] |
| Workflow | ||
| Pull requests and previews | Yes: Check and comment on GitHub and Bitbucket pull requests. GitLab supported | Yes: A pull request agent picks what to test from the change; runs can target deploy previews[8][9] |
| Schedules | Yes: On every deploy, on a schedule, or by webhook | Yes: Releases, pull requests, schedules or API calls; a webhook for any CI[1][9] |
| Context it reads before testing | Yes: 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 MCP | Yes: Hosted MCP server for Cursor, Claude and Copilot[11] |
| Evidence with each bug | Yes: Recording, screenshots, console and network logs, steps to reproduce | Yes: Video replay, screenshots, console and network logs, agent step logs[12] |
| Where findings go | Yes: Findings on the pull request, the ticket, Slack, Microsoft Teams and email | Yes: Jira, Linear, Azure DevOps, ClickUp, Asana and Slack[10] |
| Managed service | Not covered: Not covered. Self-serve, with guided onboarding on Team and up | Yes: 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 for | Yes: Priced on how much Holmes tests, never on seats | Note: Annual plans on test-run volume, not seats; each viewport and browser counts as a run[1][5] |
| Entry price | Yes: Free plan. Paid plans from €199 ($219) a month | Note: Not published; pricing through a demo[12] |
| Getting started | Yes: €250 in free credits, no credit card | Note: 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.
Spur is a no-code testing platform, so you write all your tests in plain English instead of code.Checked 17 November 2026.
Import existing Playwright, Selenium or other automation scripts and transform them into Spur test stepsChecked 17 November 2026.
Exploratory Testing is particularly useful for edge-case testing. It uses a "fuzzier" agentChecked 17 November 2026.
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.
Each viewport and browser combination counts as a separate test run.Checked 17 November 2026.
Tests run on cloud-hosted iOS Simulators and Android Emulators. iOS builds must be Simulator builds.Checked 17 November 2026.
Findings come from three sources (**Found by**): axe-core, the accessibility tree, and page probes.Checked 17 November 2026.
Spur reads the code change, the PR description, linked tickets, and your saved settings to decide what to test.Checked 17 November 2026.
Include it to redirect tests to a different URL (such as a deploy preview) without changing your environment settings.Checked 17 November 2026.
After you authorize Slack, Linear, Jira, ClickUp, or Asana, Spur returns you to the Integrations page.Checked 17 November 2026.
Spur MCP is the glue in your AI SDLC, it wires Cursor, Claude, and Copilot to your validation agent.Checked 17 November 2026.
Video Replay: View the entire test run across all tabsChecked 17 November 2026.
Choose which browsers to run your test in: Chrome, Firefox, Safari, or Edge.Checked 17 November 2026.
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]
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]
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]
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]
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]
Evaluating Spur? See what Holmes finds first.
Free, no scripts, no SDK, and no test account needed to start.