mcpField
T
testdino-manual-tests

testdino-manual-tests

github.com/anthropicsTesting & quality4.8k50 installsUpdated 2w ago
Repository

About testdino-manual-tests

testdino-manual-tests is a skill for managing manual QA cases and suites in TestDino. It covers finding and inspecting existing cases as well as creating or updating cases and suites; manual execution runs are handled separately.

Key features

  1. 01Browse manual test suites and cases
  2. 02Inspect individual test cases
  3. 03Create and update test cases
  4. 04Create test suites
  5. 05Filter by status, priority, tags, and other fields

Use cases

  1. 01Create a manual test case
  2. 02Update case preconditions or steps
  3. 03Find cases in a suite
  4. 04Create a manual test suite

MCP support

The skill guides use of TestDino manual-test tools for listing, retrieving, creating, and updating cases and suites; execution runs use separate tools.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/anthropics/claude-plugins-community --skill testdino-manual-tests

After installing, type/testdino-manual-testsin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported