testdino-manual-tests

$npx mdskill add anthropics/claude-plugins-community/testdino-manual-tests

Create, update, browse manual QA test cases and suites in TestDino

  • Identify the target suite for manual test case creation or updates.
  • Use API calls to list, create, update, or retrieve manual test cases and suites.
  • Automatically resolve existing fields on updates by sending only changed field values.
  • Return results in a structured format for easy consumption.

SKILL.md

.github/skills/testdino-manual-testsView on GitHub ↗
---
name: testdino-manual-tests
description: 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.
---

# TestDino Manual Tests

Use TestDino manual-test tools when the user wants to create, update, or browse manual QA cases and suites.

Preferred flow:

1. Call `health` if `projectId` is not known.
2. Use `list_manual_test_suites` to find the destination suite when needed.
3. Use `list_manual_test_cases` or `get_manual_test_case` to inspect existing cases.
4. Use `create_manual_test_case`, `update_manual_test_case`, or `create_manual_test_suite` for edits.

Boundary:

- This skill is for manual test cases and suites.
- Manual execution runs are a separate workflow and should use the manual-run tools.

Good requests for this skill:

- create a manual test case
- update preconditions or steps
- list manual cases in a suite
- create a new manual test suite

Common filters from the docs:

- search
- suite
- status
- priority
- severity
- type
- layer
- behavior
- automation status
- tags
- flaky flag

When creating a case:

- confirm or resolve the target suite first
- include steps, preconditions, and postconditions when the user provides them
- preserve existing fields on updates by sending only the fields that should change
- send structured arrays for fields like tags when the MCP payload requires arrays

More from anthropics/claude-plugins-community

SkillDescription
eli5Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture explainer of how something works.
html-planWrite an implementation plan as one interactive HTML page - a tree of claims (why › what › how › where), each proved by one exhibit (UI mockup, state machine, call stack, schema or code), with the decisions the user has to make placed on the claim they change. Use when the user types /html-plan, or asks for a plan, RFC or design before building something that touches more than a couple of files.
quickdesignUse the `quickdesign` CLI to generate AI media — UGC promo videos, image edits, product creatives, video upscales — through Seedance, Kling, Sora2, Nano Banana, and GPT Image. Invoke this skill whenever the user asks for a talking-avatar video, multi-segment ad / promo / explainer, image edit (object swap, angle change, state change), product photoshoot, or video upscale via QuickDesign.
testdino-auditUse 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.
testdino-healthUse 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.
testdino-manual-runsUse 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.
testdino-releasesUse 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.
testdino-runsUse 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.
testdino-sessionsUse 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.
tres-asc845-swap-reprice-skill>