Overview

TestDino collects Playwright test results from CI and keeps the run history, errors, traces, screenshots, videos, logs, and related metadata in one place. It uses that history to help teams investigate failures, identify flaky tests, group recurring errors, and track test health across runs, branches, pull requests, and environments. Through TestDino MCP, AI agents can query test runs, failures, flaky-test history, and other test data while working in tools such as Claude Code and Cursor. TestDino also includes test cases, manual test runs, and release workflows for teams that want to manage automated and manual testing together.

​

Get Started

Three steps take you from a fresh account to test health in CI.

​

Why TestDino

Playwright reports explain a single run.
TestDino explains your suite across every run, branch, and team. As your Playwright suite grows in CI, the questions pile up. Which tests are flaky? What actually broke? Why is the pipeline getting slower? One report cannot tell you. TestDino keeps all your test runs in one place. It catches flaky tests, spots regressions, and helps CI run faster and cheaper. And it gives you the answers where you already work: in your PR, in Slack, and in your IDE, not in a report that vanishes when the job ends.

​

Agent-Callable by Design

Your AI agents can use TestDino too, through MCP or the API. A Cursor or Claude Code agent can check suite health, find flaky tests, write manual test cases, create and track releases, or ask a question about a release, all in one call. No dashboard needed. An agent on its own only sees one run. TestDino remembers all of them, across runs, branches, and teams, and hands that history back to the agent. The smarter the agent, the more it can do with it.

​

Playwright-Native Test Management

​

Core Features

​

Run Control & Orchestration

​

Integrations & Access

​

Watch the 2 minute demo

​

Community and Contact