testdino
v1.0.0Use 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.
by TestDinoMIT340updated 9 hours ago
Source
git clone https://github.com/anthropics/claude-plugins-communityClone the source, then follow the repository's marketplace instructions for your runtime. The plugin root is testdino/ inside the repository.
Layout
├── .claude-plugin/plugin.json├── skills/testdino-audit/SKILL.md├── skills/testdino-health/SKILL.md├── skills/testdino-manual-runs/SKILL.md├── skills/testdino-manual-tests/SKILL.md├── skills/testdino-releases/SKILL.md├── skills/testdino-runs/SKILL.md├── skills/testdino-sessions/SKILL.md└── .mcp.json
Skills7
Use only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.
Use when the user wants to check TestDino connection status, validate their PAT, discover available organizations and projects, or find the right projectId. Always call this first when the project context is ambiguous before any other TestDino tool.
Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156.
Use when the user wants to create, update, or browse manual QA test cases and suites in TestDino — not execution runs. Covers list_manual_test_suites, list_manual_test_cases, get_manual_test_case, create_manual_test_case, update_manual_test_case, create_manual_test_suite.
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers list_releases, get_release, create_release, and update_release. Accepts counter-style IDs like MS-12.
Use when the user wants to inspect automated test runs, list failed or flaky tests, debug a failing testcase with historical context, or filter runs by branch, commit, author, environment, browser, status, or tags. Includes list_testruns, get_run_details, list_testcase, get_testcase_details, and debug_testcase.
Use when the user wants to browse, inspect, create, or update exploratory testing sessions in TestDino — by state, status, session type, assignee, release, or tags. Covers list_sessions, get_session, create_session, and update_session. Accepts counter-style IDs like SES-12.
MCP servers1
- url
- https://mcp.testdino.com
Manifests1
{
"name": "testdino",
"description": "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.",
"version": "1.0.0",
"author": {
"name": "TestDino",
"email": "support@testdino.com"
},
"homepage": "https://testdino.com",
"repository": "https://github.com/testdino-hq/TestDino-Plugins",
"license": "MIT",
"keywords": [
"claude-code",
"mcp",
"testdino",
"testing",
"playwright",
"qa"
]
}