Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.testdino.com/llms.txt

Use this file to discover all available pages before exploring further.

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

CursorOpen in Cursor
TestDino collects Playwright results, logs, errors, traces, videos, and screenshots to provide aggregated analysis for faster debugging and shipping. Your team accesses these insights proactively through dashboards, Slack notifications, MCP, and PR comments — wherever they work.

​
Prerequisites

​
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

Install the TestDino CLI

npm install tdpw
View TestDino npm package for tdpw ↗
4

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.
5

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.
6

Verify in TestDino

Open Test Runs in your TestDino project.TestDino Test Runs page showing first uploaded test run
7

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.
8

Connect your tools

Connect your communication and project management tools to get the most out of TestDino:
  • 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