Overview

TestDino records Playwright test runs from CI and keeps what each run produced: errors, traces, screenshots, videos, logs, and the branch, pull request, and environment behind it. That history is what triage runs on. Failures group by root cause, a test’s flakiness is measured across its full run history, and the result reaches you in the pull request, in Slack, and in your IDE through MCP.

Stream your first run

Hand it to your coding agent, or run these 3 steps yourself.

Install @testdino/playwright and stream the first test run.

Open in Cursor

Install the reporter

npm install @testdino/playwright

Add it to your Playwright config

playwright.config.ts

import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['@testdino/playwright', {
      token: process.env.TESTDINO_TOKEN,
    }],
  ],
});

Run your tests

export TESTDINO_TOKEN="your-api-key"
npx playwright test

Results stream to the dashboard as each test case completes, so nothing is uploaded after the run. Create the key in Generate API Keys.

Start here

Quick Setup

API key to a verified first test run, in 5 minutes.

Connect your CI

GitHub Actions, GitLab, Jenkins, CircleCI, Azure DevOps, Bitbucket, Buildkite.

Connect an AI agent

Give Claude Code or Cursor your test history over MCP.

Debug a failure

Open a failed test case with its trace, screenshots, and console logs.

Watch the 2 minute demo

Record and debug every run

Feature	What it does
Real-time streaming	Results appear in the dashboard as each test case completes, mid-run.
Centralized debugging	Native Playwright traces, screenshots, videos, and console logs for every CI run.
Flaky test detection	Catches tests that flip across CI runs, not only Playwright’s per-run retry flag, with one-click fix workflows.
Error grouping	Groups similar failures by error message and root cause instead of listing them one by one.
AI failure analysis	Classifies each failure as Actual Bug, UI Change, Unstable Test, or Miscellaneous.
Test Explorer	Find failing, flaky, or slow test cases across a whole project, then open any one for detail.
Dashboard	Test health, trends, flaky tests, and pull request status in one view.
Analytics	Trends across test runs, branches, and pull requests.
Code coverage	Which code your test cases cover, and where the gaps are across runs.

A persistent test record

A single Playwright report dies with the job that produced it. TestDino keeps every run, so a failure links back to its history instead of starting from zero, and a regression traces to the commit that introduced it.

Alternatives to TestDino

Use TestDino from an agent

An agent that runs your suite sees one run. TestDino hands back every run before it: the same test case last week, on another branch, in another environment. The smarter the agent, the more it does with that.

Interface	What agents do with it
MCP server	Local and remote. Query failures, check suite health, trigger reruns, and run fix workflows without opening a dashboard.
Public API	Every platform operation is scriptable.
AI test audit	Before your agent reviews a line of code, it pulls the branch’s top failing, flaky, and slow tests from real CI history. Findings cite evidence, such as a test that failed 8 of its last 10 runs, instead of a generic static-analysis guess.
Tools reference	Create manual test runs, releases, and exploratory sessions on the same suite structure as the automated specs.

Control what CI runs

Feature	What it does
Selective execution	Run only failed test cases or only flaky test cases, straight from TestDino.
Smart orchestration	Optimized sharding and load balancing across CI machines to cut execution time.
Trigger reruns	Start test runs from the dashboard, the API, or MCP.
GitHub CI checks	Block merges until tests meet quality gates.

Automated and manual tests in one suite

Test management puts manual test cases in the same suite structure as your Playwright specs. Run them in releases and sessions with tracked results, from the dashboard or over MCP.

Integrations & access

Area	What you get
Version control & CI	GitHub, GitLab, Bitbucket, Jenkins, and CircleCI, tied to pull requests and branches.
Notifications & workflows	Slack action-based notifications with custom templates, plus Jira and Linear.
Storage & retention	Artifacts and test results are retained for a fixed period on every plan. Analytics retention scales with your plan.
Security & support	SOC 2 and ISO 27001 certified. Email and live chat support on all plans, with dedicated Slack Connect channels and SLAs on Enterprise.

Community and Contact

Discord

Questions and updates from the community.

GitHub

Follow TestDino on GitHub.

Contact Support

Get help from the TestDino team.

Getting Started

AI-Native Testing

Test Generation

Test Intelligence

Test Management

Guides

Connect Your Pipeline

Organization & Access

Integrations

Data Privacy & Security

Resources

Stream your first run

Start here

Quick Setup

Connect your CI

Connect an AI agent

Debug a failure

Watch the 2 minute demo

Record and debug every run

A persistent test record

Alternatives to TestDino

Use TestDino from an agent

Control what CI runs

Automated and manual tests in one suite

Integrations & access

Community and Contact

Discord

GitHub

Contact Support

​Stream your first run

​Start here

Quick Setup

Connect your CI

Connect an AI agent

Debug a failure

​Watch the 2 minute demo

​Record and debug every run

​A persistent test record

Alternatives to TestDino

​Use TestDino from an agent

​Control what CI runs

​Automated and manual tests in one suite

​Integrations & access

​Community and Contact

Discord

GitHub

Contact Support

Stream your first run

Start here

Watch the 2 minute demo

Record and debug every run

A persistent test record

Use TestDino from an agent

Control what CI runs

Automated and manual tests in one suite

Integrations & access

Community and Contact