New to TestDino? Run your first test upload with the human walkthrough at Getting Started first. Use this page to give an AI agent access once your project exists.
Quick Reference
| Step | Section | What you do |
|---|---|---|
| 1 | Pick your path | Choose what the agent does: read live data, upload results, ground in docs, or write tests |
| 2 | Create a project and key | Set up the credential your path needs: API key or PAT |
| 3 | Set up your path | Wire up one or more: MCP, Reporter CLI, docs, or Skill |
| 4 | Give the agent context | Paste the starter prompt, then use goal-based prompt starters |
| 5 | Route the agent | Send it to the right guide and choose docs vs live data |
Pick your path
The 4 integration points solve different problems. Most teams use more than one.| If you want the agent to… | Use | Setup |
|---|---|---|
| Read live test runs, failures, and flaky tests from your workspace | TestDino MCP | Add the MCP server config + a Personal Access Token |
| Upload Playwright results to TestDino | Reporter CLI | npm install tdpw + an API key |
| Answer questions grounded in the TestDino docs | Docs for agents | Point it at llms.txt / llms-full.txt |
| Write and debug Playwright tests with expert guidance | Playwright Skill | npx skills add testdino-hq/playwright-skill |
Prerequisite: Create a project and key
A human creates the TestDino account, organization, and project. Once a project exists, create the credential that matches your path:- API key for CLI uploads
- Personal Access Token (PAT) for MCP
Your Playwright project also needs HTML and JSON reports before you can upload test runs. Use Getting Started for the first upload flow and Generate API Keys for key setup.
TestDino MCP Server
MCP is the live-data path for TestDino. It lets your AI assistant inspect test runs, failed test cases, flaky tests, and manual test cases from your workspace. The TestDino MCP server works with Claude Code, Cursor, Claude Desktop, ChatGPT, and other MCP-capable tools. The server reads your Personal Access Token from theTESTDINO_PAT environment variable.
MCP Server
View setup instructions for local and remote MCP clients.
TestDino Reporter CLI
The TestDino Reporter CLI uploads Playwright test results, traces, screenshots, videos, and metadata to TestDino. It is the main path for getting data into the platform before an AI assistant can reason about it.tdpw package handles post-run uploads. For real-time streaming, install @testdino/playwright instead and run tdpw test. Python users upload pytest-playwright reports with the testdino package. See Which package to install.
Reporter CLI
Choose the Node.js or Python reporting path.
TestDino Docs for Agents
Ground the agent in current docs. Pick the scope that fits the task:| Scope | What it gives the agent | Source |
|---|---|---|
| One page | The exact page you’re on, as markdown | Append .md to any URL |
| Page index | A lightweight map to navigate the docs | llms.txt |
| Full bundle | Every page in one file for deep grounding | llms-full.txt |
Universal Starter Prompt
Paste this into ChatGPT, Claude, Cursor, Codex, or another AI assistant:Onboard any AI assistant to TestDino using the docs as the source of truth.
Prompt Starters by Goal
Use these after your assistant has loaded the docs context.| Goal | Prompt |
|---|---|
| Set up a new project | Help me set up TestDino for a Playwright project from scratch. |
| Configure CI | Show me how to upload Playwright results to TestDino in GitHub Actions. |
| Learn the platform | Walk me through the Test Runs page and how to debug a failure. |
| Understand AI features | Explain the difference between AI Insights, MCP, and Test Audit. |
| Organize test cases | Help me organize suites and manual test cases in TestDino. |
| Find the right page | Which TestDino docs page should I read for Slack alerts? |
Playwright Skill
The Playwright Skill gives coding agents specialized guidance for writing, debugging, and maintaining Playwright tests. Use it when you want help inside your test repo, especially for flaky tests, locators, assertions, CI configs, or Playwright architecture patterns.Playwright Skill
Install the skill and see the supported sub-skills.
Quick Start Guides
Where to send the agent next. When it has the docs context and a clear goal, point it at the matching guide.| Goal | Best page |
|---|---|
| First-time setup | Getting Started |
| Choose the right CLI path | CLI Overview |
| Upload from CI | CI Setup Overview |
| Debug a failure | Debug Playwright Test Failures |
| Learn AI features | AI Overview |
| Connect live data | MCP Overview |
| Organize manual test cases | Test Management Overview |
| Configure integrations | Integrations Overview |
Explore AI features
Once the agent is connected, point it at TestDino’s AI workflows. AI Test Audit reviews a Playwright suite for code quality and coverage gaps. AI Insights and Failure Analysis classify failures and surface cross-run patterns.AI Test Audit
Run an AI audit of a Playwright suite and review the report.
Failure Analysis
Review cross-run failure patterns and categories.
AI Overview
See every AI feature across TestDino.
Next Steps
Getting Started
Set up TestDino in a Playwright project.
MCP Overview
Connect an assistant to live TestDino data.
CLI Overview
Choose the Node.js or Python reporting path.
Integrations Overview
Route alerts, tickets, and workflows into your tools.