Holmes vs mabl
Both use AI agents to write tests from plain language and keep them working as the UI changes. mabl is an established enterprise platform with four browsers, load testing and permanent audit evidence. Holmes adds public prices with a Free plan, context from specs, designs and analytics, and a plain-language summary of every release.
mabl's pricing is quote-only, with a 14-day free trial. Holmes has a Free plan and publishes its Starter and Team prices, from €199 a month.
mabl writes tests from a described flow or a Jira ticket. Holmes also reads the code change, the spec in Notion or Confluence, the design in Figma and your analytics 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.
Every Holmes finding comes with a recording of the run, screenshots, console and network logs, and steps to reproduce. mabl keeps screenshots, DOM snapshots and network logs for every step; video isn't described on its pages.
Based on each product's public pages on 17 November 2026. A red cross means mabl's pages don't describe it, not that it can't be done.
| Capability | Holmes | mabl |
|---|---|---|
| Testing | ||
| How tests are written | Yes: Plain-language goals. No test code to write | Yes: Describe a flow or paste a Jira ticket; mabl authors the test[1] |
| Finds bugs nobody scripted | Yes: Agents explore and test paths nobody wrote down | Partly: Agents can author tests from exploring the app[2] |
| Keeps tests working when the UI changes | Yes: Flows repair themselves when a label or layout changes | Yes: Auto-healing updates tests, with recovery mid-run[3][1] |
| Other browsers | Yes: Chromium, Firefox and WebKit, the engine behind Safari | Yes: Chrome, Firefox, Safari (WebKit) and Edge[4] |
| Native Android apps | Yes: Native Android apps on an Android emulator | Yes: Cloud emulators; mobile cloud runs are a paid add-on[5][6][13] |
| Native iOS apps | Yes: Native iOS apps on iPhone and iPad simulators | Yes: Cloud simulators; mobile cloud runs are a paid add-on[5][6][13] |
| Real devices | Not covered: Not covered. Android emulators and iOS simulators | Not described: Cloud emulators and simulators. Real devices aren't on its pages[13] |
| APIs | Yes: Every request behind a journey, checked in context | Yes: API tests in CI, with Postman import[7] |
| Accessibility | Yes: WCAG audits in a real browser, with keyboard navigation | Yes: WCAG checks added to existing UI tests[8] |
| Load testing | Not covered: Not covered | Yes: Browser and API load, reusing functional tests[9] |
| Visual testing | Partly: Compares the Figma design with what shipped. No pixel-diff baselines | Yes: Visual assertions[6] |
| Workflow | ||
| Pull requests and previews | Yes: Check and comment on GitHub and Bitbucket pull requests. GitLab supported | Yes: Status checks and inline comments on GitHub pull requests; runs on deployments via GitHub Actions[1][10] |
| Context it reads before testing | Yes: Reads the code change, ticket, spec (Notion, Confluence), design (Figma) and analytics (PostHog) | Partly: Jira tickets and Atlassian Rovo. Figma, Notion or Linear aren't on its pages[1] |
| Coding agents (MCP) | Yes: Start runs and read findings from Claude and Cursor via MCP | Yes: MCP server and a local Chrome debugger for coding agents[11] |
| Evidence with each bug | Yes: Recording, screenshots, console and network logs, steps to reproduce | Yes: Screenshots, DOM snapshots and network logs for every step, kept permanently[12] |
| Where findings go | Yes: Findings on the pull request, the ticket, Slack, Microsoft Teams and email | Yes: Jira defects with failure analysis; Slack and Microsoft Teams[1][6] |
| Pricing and security | ||
| What you pay for | Yes: Priced on how much Holmes tests, never on seats | Note: Credits for cloud runs, from 500 a month; unlimited local and CI runs[6] |
| Users | Yes: Unlimited users on every plan | Note: Unlimited participant licenses[6] |
| Entry price | Yes: Free plan. Paid plans from €199 ($219) a month | Note: Quote only; 14-day free trial[6] |
Holmes sells QA software, so we compete with mabl. We've tried to be fair: every statement about mabl 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.
Describe a flow, paste a Jira ticket, or connect via Atlassian Rovo and generate tests directly from Jira. mabl authors the test.Checked 17 November 2026.
Tests are authored from requirements, user flows, or application exploration. Humans set direction while agents do the work.Checked 17 November 2026.
mabl's agentic tester uses multiple AI technologies to autonomously update your tests, eliminating up to 95% of test maintenanceChecked 17 November 2026.
Create a single, robust test and run it reliably across Chrome, Firefox, Safari (WebKit), and Edge.Checked 17 November 2026.
mabl builds and maintains mobile tests across iOS and Android, without the need for a device lab or platform-specific scripting.Checked 17 November 2026.
mabl provides a starting point of 500 credits per month for cloud test runs, shared across browser and mobile UI and API testing as well as performance and accessibility testing.Checked 17 November 2026.
Import your Postman collections and utilize mabl’s automated API testing to run them in your CI pipeline on every commit.Checked 17 November 2026.
Easily add accessibility checks to your existing end-to-end UI tests, expanding coverage for WCAG standards across your entire user journey without creating new tests.Checked 17 November 2026.
Reuse existing tests to validate application speed and stability for both browser and API load.Checked 17 November 2026.
Trigger mabl tests when initiating new deployments via GitHub actionsChecked 17 November 2026.
With the local debugger for agents, they can investigate failures and reproduce them live in a Chrome session to confirm the fix, all inside their coding agent.Checked 17 November 2026.
Every test step retains screenshots, DOM snapshots, network logs, and decision rationales, timestamped by infrastructure outside your control, and kept permanently, pass or fail.Checked 17 November 2026.
Test across emulators and simulators simultaneously in the cloud, getting results in minutes.Checked 17 November 2026.
Both use AI agents to author and maintain tests. mabl is a broad enterprise platform: web on four browsers, iOS and Android as an add-on, APIs, accessibility, load testing and audit evidence for regulated teams. Holmes is self-serve with public pricing, reads specs, designs and analytics before it tests, and writes a summary of every release.[4][6][9][12]
mabl tests iOS and Android apps on cloud emulators and simulators, with unlimited parallel cloud runs as a paid add-on. Real devices aren't described on its pages. Holmes tests native Android and iOS apps on emulators and simulators.[5][6][13]
mabl's pricing is quote-only. Cloud runs use credits, starting at 500 a month and shared across test types, with unlimited local and CI runs and 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.[6]
Yes. mabl reuses functional tests to check browser and API speed and stability under load. Holmes does not cover performance or load testing.[9]
If you need Safari and Edge, load testing, permanent step-by-step evidence for audits, or live support in Japanese, mabl covers those on its own pages. If you want public prices with a Free plan, context from specs, designs and analytics, and a summary of every release, try Holmes.[5][4][9][12][1][6]
Evaluating mabl? See what Holmes finds first.
Free, no scripts, no SDK, and no test account needed to start.