mobile-testing vs testing
mobile-testing is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
mobile-testing is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. testing is a plugin bundle for AI coding tools published by kobiton. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-18. 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 |  testing | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.9.0 Forks (GitHub): 6 Stars (GitHub): 14 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 | mobile-testingno longer listed · | testing |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 14 |
| Forks (GitHub) (differs) | 0 | 6 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (api.kobiton.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | 2 | 9 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/kobiton/automate |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
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 mobile-testing
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Agents that test your web and mobile app like real users, on every pull request.
-
RobotActions — AI-Driven Mobile + Web Test Automation
Drive real Android & iOS devices and web browsers from natural language for mobile + web QA.
-
Mobile device interaction automation via MCP
-
Drive Android & iOS mobile-app automation from your AI agent on locally connected devices.
-
tailtest automatically generates and runs tests every time Claude Code edits a file. No commands, no configuration, no reminders needed. It hooks into Claude's file write event…
-
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…
What each says it does
mobile-testing
Generate mobile testing setup with Detox
testing
Kobiton brings agentic AI to mobile quality so engineers & testers can initiate testing directly from where code is built. With our Claude Code plugin, you can initiate Appium tests and inspect results on real devices without leaving your development workflow. You can manage test execution, save apps for future testing, review test execution results, work with a range of different real devices.
How to run each
mobile-testing
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
testing As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install testing@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only testing 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: mobile-testing · What it can do: testing · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.