Skip to main content
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

3 steps take you from a fresh account to test health in CI.
Step 1: connect Playwright to TestDino by adding @testdino/playwright to your config so results stream liveStep 2: set up your CI provider, with GitHub, GitLab, CircleCI, Azure DevOps, and Jenkins supported
Step 3: connect your AI agent to TestDino through the MCP server

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.

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 each time. Every test run ties to its branch, pull request, and environment, so a regression traces back to the commit that introduced it. Failures group by root cause instead of piling up one by one, and a test’s flakiness is visible across its full run history, not just the current one. That history reaches you in the PR, in Slack, and in your IDE, not only on a dashboard you have to remember to open.

Alternatives to TestDino

Playwright-Native Test Management

Core Features

Run Control & Orchestration

Integrations & Access

Watch the 2 minute demo

Community and Contact

Discord

Questions and updates from the community.

GitHub

Follow TestDino on GitHub.

Contact Support

Get help from the TestDino team.
Last modified on September 7, 2026