Skip to main content
TestDino collects Playwright results, logs, errors, traces, videos, and screenshots, then aggregates them into analysis for faster debugging. Your team reads these insights from dashboards, Slack notifications, MCP, and PR comments. Go from a fresh account to your first uploaded test run in about five minutes. Use the AI agent prompt below to let an assistant handle the setup, or follow the manual steps.

​
Prerequisites

Uploaded data is encrypted in transit and at rest. TestDino is SOC 2 Type 2 and ISO 27001 certified: see Security & Compliance.

​
Set up with an AI agent

Copy the prompt below into Cursor, Claude Code, or another AI coding assistant. It carries the verified steps and guardrails for uploading your first run, so the agent configures the reporters and runs the upload for you.

Use this pre-built prompt to set up TestDino faster.

Open in Cursor
For the full agent workflow, including MCP and starter prompts, see AI Onboarding.

​
Set Up Your First Project

1

Create a project

After signup and onboarding, click New Project to create your first project.TestDino new project creation screen with project name field
2

Get your API key

Go to Project Settings → API Keys and generate a new key. Copy and save it securely.TestDino Project Settings API Keys page showing generated key with copy button
3

Export your API key

Store the key in the TESTDINO_TOKEN environment variable so the CLI can read it. Every command below uses this variable.
export TESTDINO_TOKEN=<your-api-key>
NoteNever hardcode the key in source or CI config. In CI, store it as a secret and reference it as an environment variable.
4

Install the TestDino CLI

npm install tdpw
View TestDino npm package for tdpw ↗
5

Configure Playwright reporters

Add JSON and HTML reporters to your Playwright config:
playwright.config.js
reporter: [
  ['html', { outputDir: './playwright-report' }],
  ['json', { outputFile: './playwright-report/report.json' }],
]
NoteThe HTML reporter must be listed before the JSON reporter. Playwright’s HTML reporter clears its output directory on each run, so placing it first ensures report.json is not deleted.
6

Run tests and upload

# Run your tests
npx playwright test

# Upload results to TestDino
npx tdpw upload ./playwright-report --token="$TESTDINO_TOKEN" --upload-html
NoteExport your API key as the TESTDINO_TOKEN environment variable. Never hardcode it in source or CI config.
7

Verify in TestDino

Open Test Runs in your TestDino project. You should see your run at the top of the list with its pass/fail counts, duration, and a link into the full report with traces and screenshots. If it appears, your setup is working.TestDino Test Runs page showing first uploaded test run
No run showing up? The most common cause is reporter order. The HTML reporter must be listed before the JSON reporter in playwright.config.js, or report.json gets cleared before upload. See Quick Setup troubleshooting if it persists.
8

Integrate with your CI pipeline

Automate test uploads by adding TestDino to your CI workflow.Follow the CI Setup Guide to configure your provider (GitHub Actions, GitLab CI, Azure DevOps, CircleCI, TeamCity, and more).Optionally, set up Branch Mapping to organize test runs by environment.
9

Connect your tools

Connect your communication and project management tools to route test results where your team works:
  • Slack: get notified on test failures
  • Jira: auto-create tickets from failures
  • GitHub: PR comments and status checks
  • All Integrations: Linear, Asana, Monday.com, and more

​
Next Steps

TestDino MCP

Access test results and fix issues directly with AI agents

Users & Roles

Invite and manage team members in your organization