docs

Guide AI agents through TestDino MCP tools for test data access and analysis.

8|3|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/testdino-hq/testdino-mcp --skill docs-testdino-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/testdino-hq/testdino-mcp/tree/main/docs
Command: npx skills add https://github.com/testdino-hq/testdino-mcp --skill docs-testdino-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides AI agents with a structured understanding of TestDino MCP tools, enabling efficient access to test data, analysis, and test-case management.

Core Features & Use Cases

  • Guidance on MCP tool patterns, decision trees, and best practices for health, listing, and detail retrieval.
  • Use cases include diagnosing failures, debugging, and automating manual test-case workflows.
  • Clear, actionable prompts for AI agents to interact with TestDino via MCP during coding and QA tasks.

Quick Start

Instruct the AI to first run health() to obtain the projectId, then use other tools like list_testruns(), list_testcase(), get_run_details(), or debug_testcase() to answer questions about test data and failures.

Frequently Asked Questions about docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use MCP tools to fetch TestDino test runs and diagnose failures?

To use MCP tools for TestDino test runs, first run health() to get the projectId, then use list_testruns() or get_run_details() to fetch data and diagnose test failures.

What is the best way to automate manual test case workflows with an AI agent?

Automating manual test case workflows requires guiding AI agents with structured MCP tool patterns to call list_testcase() and manage test data across TestDino projects.

Do I need a Personal Access Token to let an AI agent access TestDino MCP tools?

Yes, accessing TestDino MCP tools requires a PAT provided via an environment variable, alongside obtaining the projectId from the health() function before making further tool calls.

How does an AI agent diagnose debugging issues across TestDino projects?

An AI agent diagnoses debugging issues by applying MCP tool decision trees to fetch test data via list_testruns() and isolate failure root causes using debug_testcase() within TestDino.

Can I use MCP patterns to manage test cases across multiple TestDino projects?

Yes, you can use MCP patterns to manage test cases across multiple projects by supplying the correct projectId from health() to target tools like list_testcase() for each specific TestDino project.