Ext Ops Panel
Open dashboard
Comparison

testdino vs qa-test-strategy

testdino is a plugin bundle for AI coding tools published by TestDino. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). qa-test-strategy is a plugin bundle for AI coding tools published by Seth Ford. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-12. 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

Where each is published
Marketplacetestdinoqa-test-strategy
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 357
Stars (GitHub): 4 869
Not marked · First seen
Not listed
Community marketplace sethdford/claude-skills Not listed Listed
Version: 1.0.0
Forks (GitHub): 9
Stars (GitHub): 48
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

testdino vs qa-test-strategy
Facttestdinoqa-test-strategy
Marketplaces that list it11
Stars (GitHub) (differs)4 869 (better)48 (worse)
Forks (GitHub) (differs)357 (better)9 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.testdino.com)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)813
LicenceMITMIT
Repository (differs)github.com/anthropics/claude-plugins-communitygithub.com/sethdford/claude-skills
Changes in the last 7 days00
First seen (differs)2026-10-122026-11-05
Endpoint at the last check (differs)Responded 13 h agono remote endpoint we check

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

testdino

In its own words, on Claude Code: claude-plugins-community:

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-test-strategy

In its own words, on Community GitHub marketplaces:

Test planning, risk-based testing, coverage analysis, test pyramid, strategy documentation. Grounded in ISTQB, ISO 25010.

How to run each

testdino As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install testdino@claude-community

qa-test-strategy As a Claude Code plugin

Claude Code
/plugin marketplace add sethdford/claude-skills
/plugin install qa-test-strategy@claude-skills

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only testdino 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: testdino · What it can do: qa-test-strategy · 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 public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built