Casely vs TesterArmy
Casely is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
Casely is a plugin bundle for AI coding tools published by John Wayne. 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-10-27. 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 johnwayneeee/casely-qa-skill | Removed on 2026-10-26 Version: 2.4.0 Forks (GitHub): 0 Stars (GitHub): 11 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 5 Stars (GitHub): 72 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 | Caselyno longer listed · | TesterArmy |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 11 | 72 |
| Forks (GitHub) (differs) | 0 | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.atlassian.com/v2/mcp) | Remote server (tester.army/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/johnwayneeee/casely-qa-skill | github.com/tester-army/cli |
| Changes in the last 7 days (differs) | 8 | 0 |
| First seen (differs) | 2026-10-23 | 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 Casely
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
English skills: evidence-disciplined testing framework, Playwright test review, test cases, Jira bug reports
-
Create and manage test cases, test runs and results in Testiny from your AI assistant.
-
Use TestDino inside Claude Code through the hosted remote MCP server to inspect test runs, debug failing test cases, manage manual tests, and run TestDino audits.
-
QA process setup with AAA test cases, P0-P4 bug tracking, metrics reports, OWASP security testing and third-party handoffs. Use for test planning, approved-batch execution and…
-
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
-
Natural-language end-to-end tests for any software surface, powered by getlark.ai
What each says it does
Casely
Attach requirements or name a Jira issue, add an example of your team's test cases, approve one plan, get a TestRail-ready Excel or CSV file back, plus a runnable Postman collection when the spec describes an API, and bug reports from a trace ID.
TesterArmy
Agents that test your web and mobile app like real users, on every pull request.
How to run each
Casely
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: Casely · 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.