TestDino
Playwright Dashboard

TestDino is the cloud companion Playwright platform your AI agents can act on

TestDino records your Playwright runs from CI so your team and your AI agents can act on the results over MCP. See flaky tests and traces in one dashboard.

Choosing the right Playwright dashboard can be challenging. Many teams start with the default Playwright HTML reporter, but it often falls short for cross-run analytics, debugging at scale, and team-wide visibility. Teams report limited customization, integration support, analytical depth, and no shared view of test quality.

The gap has led CTOs, project managers, QA leads, and DevOps managers to seek tools that provide faster debugging, in-depth analytics, and simpler adoption.

This guide walks through TestDino, the Playwright cloud companion that records CI runs, detects flakes, and keeps traces and fix workflows ready for teams and AI agents over MCP. It centralizes runs across shards and splits, groups failures by root cause, and tracks flake rate over time.

TestDino Playwright analytics SummaryTestDino Playwright analytics Test RunsTestDino Playwright analytics Test CaseTestDino Playwright analytics ErrorsTestDino Playwright analytics EnvironmentTestDino Playwright analytics Coverage

A Single Solution for Every Role on Your Team

A single UI enables test suite management for everyone, but the pain feels different depending on your role.

For QA Engineers

You spend hours trying to gather enough evidence for a reproducible bug report, only to have it sent back as "cannot reproduce". You can see a test failing intermittently, but lack the historical data to prove it's a chronic issue that needs priority.

For Developers

You push a commit, and then you wait. The CI pipeline takes forever 🕐, and when it finally fails, the error message is cryptic. You can't easily access the screenshots, videos, or traces you need to debug effectively. The slow, unclear feedback loop is killing your productivity.

For Managers

You're responsible for delivery, but you lack true visibility. Is the team's testing effort actually improving product quality? Is the pass rate going up because the product is more stable, or because flaky tests are being silenced?

You need a clear, data-driven picture of test suite health to ensure releases are safe to ship, but you're operating in the dark.

This is where we bring the solution. TestDino records every Playwright CI run and acts as a central Playwright dashboard that unifies your team and your AI agents around a single, clear view of test quality, giving everyone the exact insights they need, fast.

Setup in Minutes, Not Hours

Adopting a new testing tool often becomes a heavy project with complex code changes, custom frameworks, and weeks of engineering effort before you see value.

TestDino removes the friction by working within the default Playwright reporter setup, so your team can adopt it without rewriting test utilities or framework code.

It is designed for a fast and minimal setup. Your first run streams in within minutes because the @testdino/playwright reporter integrates cleanly with your existing Playwright configuration.

TestDino Playwright test runs view

Fast and Playwright-Native

TestDino plugs into Playwright's reporter array, so you can begin collecting structured test data instantly. You do not need a custom framework or any code refactoring. Adding the @testdino/playwright reporter to your Playwright config file is enough: results, traces and screenshots stream to TestDino during the run, with no upload step.

This lightweight setup keeps your Playwright runs fast and transparent across all environments, without rewriting any tests or pipelines.

The 7 Tabs of a Test Run

This lightweight setup keeps your Playwright runs fast and transparent across all environments, without rewriting any tests or pipelines.

Together, these tabs form a complete Playwright Dashboard experience that covers both technical debugging and historical analysis.

TestDino test run Summary tabTestDino test run Specs tabTestDino test run Errors tabTestDino test run History tabTestDino test run Configuration tabTestDino test run Coverage tabTestDino test run AI Insights tab

Full Playwright Videos

TestDino captures and stores full video recordings of your Playwright test executions. Watch exactly what happened during a test failure - every click, navigation, and assertion - without needing to reproduce the issue locally.

Test History

Track the complete history of every test case across all your CI runs. See pass/fail patterns, identify flaky tests, and understand how test stability changes over time with detailed trend data.

Drill into Error Categories and Their Impact

The Errors tab lets you explore failure data interactively. You can see a timeline of different error types to correlate spikes with deployments and view a table of the most common Error Variants, prioritized by their impact on your test suite.

This lightweight setup keeps your Playwright runs fast and transparent across all environments, without rewriting any tests or pipelines.

Error category timeline chartError variants table prioritized by impact

Integrations that Streamline Your Workflow

To keep your team moving fast, you need to eliminate manual, error-prone tasks such as copying & pasting bug reports. Your testing tool should fit your existing workflow.

We offer one-click integrations with the tools you already use, creating a frictionless path from test failure to resolution.

For CI/CD - integration with GitHub and GitLab for automated PR and MR comments and status checks. The reporter also streams results from Azure DevOps, Bitbucket, CircleCI, Jenkins, TeamCity, AWS CodeBuild, Buildkite and Harness.

These integrations ensure a frictionless flow from TestDino into your Playwright workflow and ensure failures move more quickly across the team.

Ready to Take Control of Your Playwright Tests?

Stop guessing and start measuring. TestDino gives your entire team the clarity and confidence to ship better software, faster.

With a clear Playwright Dashboard and every CI run recorded in one place, teams can stop accidentally ignoring every flake.