# TestDino | Playwright Reporting and Analytics

> TestDino records Playwright test runs from CI, providing centralized debugging, flaky test detection, and analytics your team and your AI agents can act on.

Source: https://testdino.com

---

[New Give your AI agents test context with MCP](https://testdino.com/integrations/testdino-mcp)

# Transform how you test with Playwright in CI

TestDino is a Playwright cloud companion. It records CI runs, detects flakes, and keeps traces and fix workflows ready for teams and AI agents over MCP.

[Start a 14-day Free Trial](https://app.testdino.com/auth/signup?utm_source=website&utm_medium=hero_cta&utm_campaign=landing) [Schedule a demo](https://cal.com/testdino/30min)

Trusted by teams at

![OpenObserve][Case Study](https://testdino.com/blog/openobserve-case-study)

![Penpot]

![Franklin][Case Study](https://testdino.com/blog/franklin-case-study)

![Monument]

![Lumin]

![Greenline]

![Keen][Case Study](https://testdino.com/blog)

Debugging

## Debug test failures in your browser

Run Summary

Every test run gets a multi-tab report: summary, spec breakdown, error groups, run history, and configuration metadata. Understand any run in 5 minutes.

[View run reports](https://testdino.com/features/run-summary)

Error Groups

1-Click Trace Viewer

Screenshots, Video & Visual Diffs

Live Run

Flake Management

## Find and fix unreliable tests

Flaky Tests

Every test gets a stability percentage and a root cause category: timing, environment, network, assertion, or other. You see which tests are unreliable and why, not just that something failed again.

[How detection works](https://testdino.com/features/flaky-tests)

Test Explorer

Environment Mapping

Test History

Analytics & Trends

## Track test health across your suite

Analytics Overview

Six views in one dashboard: suite summary, test run timing, individual test trends, error categorization, coverage metrics, and environment pass rates. Filter everything by branch, tag, or time period.

[Explore analytics](https://testdino.com/features/test-trends)

Run History

Environment Analytics

Code Coverage

Test Tags & Annotations

CI & Team Integration

## Fits into how your team ships code

CI/CD & PR Gates

Add the TestDino reporter to GitHub Actions or GitLab CI. Set pass rate or flaky thresholds on PRs. TestDino posts a status check so code that doesn't meet your bar can't be merged.

[View setup guide](https://testdino.com/features/cicd-integrations)

Test Run Summary at PR

Issue Tracker Sync

Slack Alerts & PDF Reports

Test Management

## Your shards are running. You have no idea what's passing.

Without TestDino

With TestDino

### Tests pass. You still don't know.

GitHub Actions

 Playwright E2E Tests

#1162

 Summary

Jobs

 playwright-e2es (1/3)

 playwright-e2es (2/3)

 playwright-e2es (3/3)

 merge-reports

With TestDino

### Results stream in as tests run.

TestDino

Live

SHARDED

 0s

0 0

0%

Shard 1 Shard 2 Shard 3 Shard 4 Shard 5

Worker 1

 Idle

Worker 2

 Idle

Worker 3

 Idle

Worker 4

 Idle

Worker 5

 Idle

[See every feature in action](https://testdino.com/features/showcase)

## One run your whole team can act on

What each role gets, and what your agents handle without opening it.

Developers

### See test results in your PR, not a separate tab.

- AI summaries posted to every commit and pull request
- Flaky tests you introduced highlighted automatically
- Audits cite the branch's real run history, not a static code read
- One-click link from failure to trace replay

QA Engineers

### Triage hundreds of failures in minutes, not hours.

- Failures pre-sorted by AI into actionable categories
- One stack trace, one error group, instead of 20 open tabs
- Manual cases, runs, and releases live beside the automated specs
- Cross-run trend analysis and regression alerts

SDETs

### Run it sharded, split, or single. It streams either way.

- Sharded runs merge into one report through a shared run ID
- Split mode groups jobs that run different commands
- Environment mapping with regex patterns
- Agents file the ticket and write test cases over MCP

Engineering Managers

### Know if a release is ready, without asking.

- Pass rate thresholds enforced on every PR
- Scheduled PDF reports to your inbox
- CI cost and efficiency dashboards
- Release readiness visible without asking the team

## Start streaming in three steps

Results stream live and stay as history your agents can act on.

- 1 ### Install the reporter ```
npm install @testdino/playwright
```
- 2 ### Register the reporter in your config playwright.config.ts ```
reporter: [ ['@testdino/playwright', { token: process.env.TESTDINO_TOKEN, }], ]
``` Set TESTDINO_TOKEN to a project API key. [Generate an API key](https://docs.testdino.com/guides/generate-api-keys)
- 3 ### Run your tests ```
npx playwright test
```

[Read the CI setup guides](https://docs.testdino.com/guides/ci-setup-overview)

## Works with your favourite tools

Connect seamlessly with Jira, Slack, GitHub, Linear, Azure DevOps, Asana, and monday to keep your workflow smooth and your team aligned.

[### TestDino MCP Query test results, debug failures, and manage test cases from your IDE via MCP.](https://testdino.com/integrations/testdino-mcp)

[### GitHub Get AI-generated test summaries on pull requests and CI status checks on every commit.](https://testdino.com/integrations/github)

[### Jira Create Jira issues from test failures with full error context, screenshots, and links.](https://testdino.com/integrations/jira)

[### Slack Route test alerts by environment and notify specific users when annotated tests fail.](https://testdino.com/integrations/slack-app)

[### Linear File structured bug reports from test failures with failure history and code context.](https://testdino.com/integrations/linear)

[### GitLab Post AI-generated test summaries on merge requests and sync MR state with TestDino.](https://testdino.com/integrations/gitlab)

[### Azure DevOps View Playwright test runs, failure trends, and flaky tests inside Azure DevOps.](https://testdino.com/integrations/azure-devops)

[### Asana Create Asana tasks from test failures with error details, test steps, and screenshots.](https://testdino.com/integrations/asana)

[### monday Create monday.com items from test failures and view test run data in dashboards.](https://testdino.com/integrations/monday)

[See all integrations](https://testdino.com/integrations)

## MCP server for AI-assisted debugging

Claude, Cursor, and Copilot can query your test results directly. Ask your AI assistant why a test failed and it pulls real context from TestDino.

## Teams love what we built

See why developers choose TestDino to ship faster and debug smarter

![Daniel Bacigalupo]

We were on the default Playwright reporter, and it was tedious to dig through; half a day gone just triaging failures. The TestDino MCP changed that for us. I now run through the failures in minutes instead of devoting half a day to it, and pulling the latest runs straight through the MCP sped up bug triage drastically. AI failure classification and Slack reports do the rest. It's saved us weeks.

15 min

To triage failures,
down from half a day

3 weeks

Saved across the team

Daniel Bacigalupo

Quality Assurance Manager, Keen

![Daniel Bacigalupo]

![Johan Frølich]

Migrating to TestDino from Currents was an easy decision. The features are stronger, the cost is lower, and the interface makes debugging far less painful. Flaky test detection and AI failure classification have simplified debugging and reduced our CI costs by cutting down reruns and noisy failures.

40%

Reduction in CI costs

90%

Less time triaging failures

Johan Frølich

CTO & Co-founder, Franklin

![Johan Frølich]

![Shrinath Rao]

Over 30 flaky tests and no structured way to track them, just CI artifacts and morning guesswork. TestDino's "Most Flaky Tests" feature broke this pattern. We can see failure trends now and pull up video recordings of exactly what went wrong. The TestDino MCP server is the magic piece on top, I ask my Claude agent about a failure and it pulls full context from TestDino without switching tabs. We went from 30-something flaky tests down to 3 or 4.

70%

Fewer flaky test reruns

3x

Faster failure triage

Shrinath Rao

Lead Quality Assurance Engineer, OpenObserve

![Shrinath Rao]

## Verified reviews on G2

Reviews from teams running Playwright in CI, published on G2.

![G2]

###### AI-powered Playwright reporting for analyzing test failures

Analyzing failed Playwright runs in CI used to eat up a lot of our time. TestDino solved that with a centralized dashboard that pulls in screenshots, logs, and failure trends in one place. What's been most useful is the automatic grouping of failures, since instead of checking each failing test individually, we can immediately see patterns and likely causes. It's made triaging failures, and identifying which tests are simply flaky, dramatically faster.

5/5

![Yash J.]

Yash J.

Lead Software Engineer

![G2]

###### Clear visibility into slow and flaky Playwright tests

We inherited an existing test suite without much context on how it was built, and TestDino gave us a real way to take ownership of it. It shows us clearly which tests are the slowest, the flakiest, and the ones failing most often, which has been essential for knowing where to focus our effort. It's given us the visibility to understand the current state of the code and steadily improve its reliability.

4.5/5

![Estefania F.]

Estefania F.

Senior QA Engineer at Penpot by Kaleidos

![G2]

###### Comprehensive dashboard for QA automation

I monitor everything my tests do, from the full list of tests to detailed error screenshots. The GitHub integration is smooth, so commit hashes, CI runs, and HTML reports open straight from the dashboard. I use TestDino almost every day, and it has improved the quality of our automation code.

5/5

![Shrinath R.]

Shrinath R.

Lead QA Automation Engineer

[Read all 9 reviews](https://testdino.com/reviews)

## Switching from another tool?

See how TestDino compares to the tools you already know.

[Currents](https://testdino.com/compare/currents-vs-testdino)

[Allure Report](https://testdino.com/compare/allure-report-vs-testdino)

[Datadog](https://testdino.com/compare/datadog-vs-testdino)

[BrowserStack](https://testdino.com/compare/browserstack-test-reporting-vs-testdino)

[ReportPortal](https://testdino.com/compare/reportportal-vs-testdino)

[TestRail](https://testdino.com/compare/testrail-vs-testdino)

[View all comparisons](https://testdino.com/compare)

## Enterprise-grade privacy, security and data protection

Your test results, traces, and artifacts stay protected under the same security standards your enterprise customers expect.

[### ISO 27001 Your test data is handled under a certified information security management system, audited annually by independent assessors.](https://testdino.com/security#iso-27001)

[### SOC 2 Type II Continuous monitoring of security, availability, and confidentiality controls & verified by a third-party auditor, not just a checklist.](https://testdino.com/security#soc-2)

[### GDPR Data processing agreements, EU hosting options, and privacy-by-design principles baked into every feature from day one.](https://testdino.com/security#gdpr)

## FAQs

### What is TestDino?

TestDino, also searched as testdino or Test Dino, is a cloud-based companion web app for Playwright that records CI test runs to provide centralized debugging, flaky test detection, and analytics. It is built for both teams and AI agents, making test runs, failures, and fix workflows fully queryable and actionable over MCP and API.

### How does TestDino work?

### What kind of AI insights does it provide?

### What testing frameworks does it support?

### Can it detect flaky tests automatically?

### Can I get alerts or export reports?

### Is it customizable to our environments, branches, and workflows?

### How much time does TestDino save each developer?

### Does it work with sharded or split CI jobs?
