TestDino

Tool snapshot
Best fitCoding · Data Analysis · Automation
In one lineTestDino centralizes Playwright CI results, failure evidence, flaky-test analysis and reporting, with MCP access for AI-agent workflows.

TestDino is a cloud companion for teams running Playwright tests. It collects CI results into run reports, tracks flaky tests and retains evidence for debugging. Its MCP server lets an AI agent query test data and failure history from an editor.

Reporting the tests you already run

Setup adds the TestDino Playwright reporter to the test configuration and supplies a project API key. Results can stream while tests run, including sharded CI jobs. Run reports contain a summary, spec-file breakdown, error groups, history and configuration metadata, with coverage and insights views also available.

The run-summary feature groups failures with matching error signatures across spec files. You can compare runs to identify changed outcomes and inspect browser, OS, viewport, shard, retry and CI job details in the report. Screenshots, video, visual differences and a trace viewer help connect a failed test with what happened during execution.

Flake detection and team workflows

TestDino detects flaky tests through retry analysis and cross-run patterns. A failure followed by a passing retry is one signal; different results across runs without code changes are another. The flaky-test feature tracks stability trends and classifies likely causes as timing, environment, network, assertion or other.

Those categories help prioritize investigation rather than proving a root cause. Teams can look at subsequent runs after a fix to assess whether stability improved. MCP access lets a connected agent inspect flaky tests and failure history and suggest fixes.

The homepage describes GitHub and GitLab CI integration, pull-request status checks, issue-tracker connections and Slack alerts. Some of these are paid-plan features, so select a tier around the workflow you need instead of assuming that every integration comes with the free account.

Capacity, billing and retention

The pricing page lists 5,000 monthly executions for Free, 10,000 for Pro and 40,000 for Team. These allow one, three and thirty users respectively. One test run across three browsers counts as three results; retries do not add to the count.

Pro adds MCP and REST API access, AI analysis and scheduled reports. Team adds issue-tracker integrations and GitHub CI checks. The Pro calculator displays $49 per month, with a 20% annual-billing discount advertised. Enterprise has custom volume and deployment arrangements.

Retention is a separate consideration from execution capacity. The published comparison gives Free seven days of artifact retention and Pro and Team twenty-one days. Confirm the required history and billing option when choosing a plan for an existing suite.