playwright-pro vs Jarroba Tools · Test audit
playwright-pro is a plugin bundle for AI coding tools published by alirezarezvani. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Jarroba Tools · Test audit is an MCP server published by Invarato. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-05. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  playwright-pro |  Jarroba Tools · Test audit |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.9.0 Forks (GitHub): 4 073 Stars (GitHub): 29 322 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 1 284 Downloads/week (npm): 248 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 1 284 Downloads/week (npm): 248 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | playwright-pro | Jarroba Tools · Test audit |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 29 322 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 073 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-27 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@jarroba/mcp-tests) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | 1, secrets among them: 0 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/alirezarezvani/claude-skills | github.com/invarato/jarroba-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
playwright-pro
Playwright Pro turns your AI coding agent into a senior test automation engineer. Instead of generating tutorial-quality tests with brittle CSS selectors, Playwright Pro enforces battle-tested patterns from production test suites: role-based locators, web-first assertions, proper fixture architecture, and isolated test design. It doesn't reinvent Claude Code — it orchestrates it. /pw:generate uses the built-in Explore subagent for codebase analysis. /pw:migrate delegates to /batch for parallel file conversion. /pw:fix leverages /debug for trace inspection. Every skill builds on what Claude Code already does well. 55 ready-to-use test templates across 11 categories — authentication, CRUD, checkout, search, forms, dashboard, settings, onboarding, notifications, API testing, and accessibility. Each template includes TypeScript and JavaScript variants with parametrizable placeholders. Not generic stubs — real patterns like Stripe iframe handling, GraphQL mutation testing, and RBAC permission flows. 3 specialized
Jarroba Tools · Test audit
Audits tests instead of writing them: what each one really asserts. 4 tools, local.
How to run each
playwright-pro As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install playwright-pro@claude-communityJarroba Tools · Test audit As a local MCP server: npm package
claude mcp add --transport stdio jarroba-tools-tests -- npx -y @jarroba/mcp-testsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only playwright-pro asks for
BROWSERSTACK_ACCESS_KEY (secret)BROWSERSTACK_USERNAMETESTRAIL_API_KEY (secret)TESTRAIL_URLTESTRAIL_USER
Only Jarroba Tools · Test audit asks for
JARROBA_MCP_DOMAINS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: playwright-pro · What it can do: Jarroba Tools · Test audit · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.