TestDino AI Onboarding for Playwright - TestDino Documentation

Connect an AI agent (Claude Code, Cursor, ChatGPT, or similar) to TestDino so it can read your test data, set up reporting, and write Playwright code with the right context. The instructions below are for the human driving the agent: pick a path, then hand the agent the matching resource.

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.

Pick your path

The three 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.

AI features run on Microsoft Azure OpenAI Service, which does not train on customer content. For certifications, encryption, and data handling, see Security & Compliance.

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.

{
  "mcpServers": {
    "TestDino": {
      "command": "npx",
      "args": ["-y", "testdino-mcp"],
      "env": {
        "TESTDINO_PAT": "tpu_xxxxxxxxx"
      }
    }
  }
}

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.

# Install
npm install tdpw

# Upload a Playwright report
npx tdpw upload ./playwright-report --token="$TESTDINO_TOKEN" --upload-html

The tdpw package handles post-run uploads. For real-time streaming, install @testdino/playwright instead and run tdpw test. See Which package to install. You can also use Python for pytest-playwright report uploads:

pip install pytest-playwright-json pytest-html testdino
testdino upload ./test-results --token="$TESTDINO_TOKEN"

Reporter CLI

Choose the Node.js or Python reporting path.

TestDino Docs for Agents

You can give your agent current docs in a context-aware way in three ways:

Markdown docs

Every doc includes a markdown version. Append .md to any page.

Docs for this page: https://docs.testdino.com/ai-onboarding.md

Full llms.txt

Give your agent the documentation index in a single file.

Here are the TestDino docs index: https://docs.testdino.com/llms.txt

Full llms-full.txt

Give your agent the full docs bundle in a single file.

Here are the full TestDino docs: https://docs.testdino.com/llms-full.txt

Universal Starter Prompt

Paste this into ChatGPT, Claude, Cursor, Codex, or another AI assistant:

Read https://docs.testdino.com/llms-full.txt as the authoritative reference for TestDino.

Act as a TestDino documentation assistant and setup guide.
Use the docs as the source of truth when answering questions about TestDino.
When relevant, recommend the exact TestDino docs page or workflow to follow.
If my request depends on live project data, tell me to use TestDino MCP instead of guessing.

## TestDino resources
- Main docs: https://docs.testdino.com
- Docs index: https://docs.testdino.com/llms.txt
- Full docs context: https://docs.testdino.com/llms-full.txt
- Getting started: https://docs.testdino.com/getting-started
- CLI overview: https://docs.testdino.com/cli/overview
- AI overview: https://docs.testdino.com/ai/overview
- MCP overview: https://docs.testdino.com/mcp/overview
- Test management: https://docs.testdino.com/test-management/overview
- Integrations overview: https://docs.testdino.com/integrations/overview
- Data privacy: https://docs.testdino.com/data-privacy/overview

## What you should help me with
- getting started
- CLI setup
- CI integration
- debugging Playwright failures
- platform navigation
- analytics and AI insights
- test management
- integrations
- data privacy and support

## Start here
1. Summarize the main sections of the TestDino docs in a short outline.
2. Ask me which stack I use: Node.js or Python.
3. Ask which CI provider I use, if any.
4. Ask whether I want docs guidance only or live MCP help.
5. Then help me complete the task step by step.

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.

npx skills add testdino-hq/playwright-skill

You can also install individual sub-skills when you want narrower coverage:

npx skills add testdino-hq/playwright-skill/core
npx skills add testdino-hq/playwright-skill/ci
npx skills add testdino-hq/playwright-skill/pom
npx skills add testdino-hq/playwright-skill/migration
npx skills add testdino-hq/playwright-skill/playwright-cli

Playwright Skill

Install the skill and see the supported sub-skills.

Quick Start Guides

Throughout the docs, TestDino includes quick start guides for common tasks. Use these when your assistant already has the docs context and you want it routed into the best next workflow.

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

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?`

AI Test Audit

AI Test Audit is the review workflow for a Playwright suite. It uses TestDino plus MCP to inspect test code quality, missing validation, flaky patterns, maintainability issues, and coverage gaps.

AI Test Audit

Run an AI audit of a Playwright suite and review the report.

AI Insights

AI Insights is the analysis workflow inside the TestDino product. Use it to classify failures, identify persistent and emerging patterns, and inspect recommendations at the test run and test case level.

AI Overview

See every AI feature across TestDino.

Failure Analysis

Review cross-run failure patterns and categories.

Docs grounding vs live data

Docs grounding answers questions from static documentation. MCP reads live data from your project. They complement each other: ground the agent in the docs, then let it query MCP when a request depends on your actual test runs.

If the agent needs	Give it
Full product knowledge in one file	llms-full.txt
A lightweight page index to navigate	llms.txt
Live test runs, failures, or manual test cases	TestDino MCP

Next Steps

Getting Started

Set up TestDino in a Playwright project.

CLI Overview

Choose the Node.js or Python reporting path.

MCP Overview

Connect an assistant to live TestDino data.

AI Overview

Explore AI features across the platform.

Playwright Skill

Load Playwright coding guidance on demand.

Integrations Overview

Route alerts, tickets, and workflows into your tools.

​Pick your path

​Prerequisite: Create a project and key

​TestDino MCP Server

MCP Server

​TestDino Reporter CLI

Reporter CLI

​TestDino Docs for Agents

​Universal Starter Prompt

​Playwright Skill

Playwright Skill

​Quick Start Guides

​Prompt Starters by Goal

​AI Test Audit

AI Test Audit

​AI Insights

AI Overview

Failure Analysis

​Docs grounding vs live data

​Next Steps

Getting Started

CLI Overview

MCP Overview

AI Overview

Playwright Skill

Integrations Overview

Pick your path

Prerequisite: Create a project and key

TestDino MCP Server

TestDino Reporter CLI

TestDino Docs for Agents

Universal Starter Prompt

Playwright Skill

Quick Start Guides

Prompt Starters by Goal

AI Test Audit

AI Insights

Docs grounding vs live data

Next Steps