testing-expert vs TesterArmy
testing-expert is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
testing-expert is a plugin bundle for AI coding tools published by C0ntr0lledCha0s. No marketplace we read lists it any more. TesterArmy is an MCP server published by tester-army. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-02. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  TesterArmy | |
|---|---|---|
| Community marketplace c0ntr0lledcha0s/claude-code-plugin-automations | Removed on 2026-10-18 Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 6 Stars (GitHub): 74 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 | testing-expertno longer listed · | TesterArmy |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 3 | 74 |
| Forks (GitHub) (differs) | 1 | 6 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (tester.army/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 7 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/c0ntr0lledcha0s/claude-code-plugin-automations | github.com/tester-army/cli |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of testing-expert
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Test-quality skills for Claude Code. AI-driven mutation testing, where Claude acts as the mutation engine to find weak tests, and agentic testing, where Claude drives the running…
-
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…
-
10 curated QA skills: Claude Code QA, autonomous QA agent, E2E testing (Playwright, Cypress), API testing (REST + Playwright request), pytest patterns, Jest unit testing, and k6…
-
Use this agent when code changes have been made and you need to write new tests, run existing tests, analyze failures, and fix them while maintaining test integrity. This agent…
-
Comprehensive testing toolkit for test strategy, coverage analysis, and test data generation. Includes test strategist agent for planning optimal testing approaches.
-
pw
Production-grade Playwright testing toolkit. 9 skills, 3 agents, 55 templates, plus optional (manually enabled) TestRail/BrowserStack integrations. Generate tests, fix flaky…
What each says it does
testing-expert
Expert plugin for quality code reviews focused on testing. Provides comprehensive expertise for Jest, Playwright, and test quality analysis with automated test review, coverage analysis, and test suggestions. Includes cheatsheets, templates, and validation scripts.
TesterArmy
Agents that test your web and mobile app like real users, on every pull request.
How to run each
testing-expert
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
TesterArmy As a remote MCP server
claude mcp add --transport http testerarmy https://tester.army/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only TesterArmy has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: testing-expert · What it can do: TesterArmy · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.