TestDino

Visit Website

Introduction

TestDino records every Playwright run in CI, detects flakes and keeps traces and fix workflows ready for teams and for AI agents over MCP. Every GitHub Actions run arrives with its git context, and per-test execution history shows whether a failure is flaky or a real regression.

A case study describes Keen replacing the default Playwright reporter with TestDino and cutting Playwright triage from half a day to 15 minutes. Plans are sized by test executions per month, with optional manual testing.

If your team already writes Playwright tests, a reporting layer like this is often the cheapest improvement you can make: it turns red builds into a prioritised list of real regressions and known flakes.

Features

1. CI run recording: Git context on every run.
2. Flake detection: Flaky versus real regressions.
3. Traces: Kept for debugging.
4. MCP access: Agents read results and fix tests.
5. Manual testing add-on: Optional.

Pros

1. Free plan: 5,000 executions a month.
2. Trial: 14 days on Pro and Team.

Cons

1. Playwright-specific: Other frameworks not the focus.
2. Execution-based pricing: Large suites cost more.

Usage and Links (Example)

1. Sign up and install the TestDino reporter in your Playwright config.
2. Run tests in GitHub Actions.
3. Review flaky tests and connect the MCP server to your agent.

Resources:

• TestDino website

Pricing

TestDino has a Free plan (5,000 test executions a month, 1-month analytics retention), Pro at $39 a month (10,000 executions) and Team at $79 a month (40,000 executions), with extra executions at $3 per 1,000, 20% off annual billing, a 14-day trial and custom Enterprise.

Recommended for?

1. Playwright teams drowning in CI failures.

Conclusion

TestDino gives Playwright suites history, flake detection and agent access.

Compare it with Currents on your own runs.

On CheckOps, TestDino is filed under the End-to-end & functional and Release & CI gates stages. Related tools listed here include Currents, Allure Report, ReportPortal, Trunk Flaky Tests, Buildkite Test Engine and Testmo. Which one fits best depends mostly on your stack, your team’s size and skills, and whether you prefer to run tools yourself or pay for a managed service. This page reflects the official website, documentation and repository as they stood on 11 November 2026.