> ## 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.
# Overview
> TestDino is the AI-native Playwright observability and test management platform. Detect flakes, debug failures, and query your suite from any agent over MCP.
export const VideoSchema = ({name, description, thumbnailUrl, uploadDate, duration, contentUrl, embedUrl}) => {
const schema = {
"@context": "https://schema.org",
"@type": "VideoObject",
name,
description,
thumbnailUrl,
uploadDate,
...duration ? {
duration
} : {},
...contentUrl ? {
contentUrl
} : {},
...embedUrl ? {
embedUrl
} : {},
publisher: {
"@type": "Organization",
name: "TestDino",
logo: {
"@type": "ImageObject",
url: "https://docs.testdino.com/logo/light.svg"
}
}
};
return ;
};
TestDino is the test intelligence platform for Playwright. It explains what your suite is doing across every CI run, and exposes every operation to AI agents over the Model Context Protocol or the API.
It is for QA engineers, SDETs, software developers, and AI engineers building agent-driven test suites, whose job is to keep a growing end-to-end suite stable and earning its place in the project.
Traditional tools report a pass/fail count and stop there. As a suite scales in CI, that leaves teams with little visibility across runs, branches, and pipelines. TestDino replaces that with meaningful metrics, analytics, and a fully queryable view of your test data, so your team owns and manages all of it.
## 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 APIs. 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.
## Analyze Failures
|
| Run manual test cases in releases and sessions, tracked with results. |
## Watch the 2 minute demo
## Community and Contact
Questions and updates from the community.
Follow TestDino on GitHub.
Get help from the TestDino team.
## Why TestDino
Playwright reports explain a single run.