Looking to migrate from Currents? Compare Currents vs TestDino. TestDino groups errors, embeds traces, and feeds AI coding agents.
Currents is a Playwright dashboard. It captures traces, detects flaky tests via retries, and balances runs across CI workers. TestDino does all of that too and goes further. TestDino is a Playwright-focused test intelligence platform. It groups errors by root cause, ties each run to its pull request, and hands your test data to Claude Code, Cursor, or any MCP-compatible agent.
But TestDino doesn't stop at reporting. It also comes with built-in test management designed for how engineering works in 2026. Test cases live alongside their run history, manual runs, and exploratory sessions roll up under date-bound releases, and your entire test record is queryable by Claude Code, Cursor, or any MCP-compatible agent, so your AI coding tools aren't working blind.
Currents vs TestDino comes down to depth. Here's where TestDino goes further, and where Currents falls short.
Ease of setup
Setup takes under 5 minutes. Add the reporter to your Playwright config, push, and your first run populates a dashboard with AI failure categories, flaky detection, and error groups already active.
Full failure context
Every failed test opens with an embedded trace viewer, screenshots, video, console logs, and error grouping by message, stack trace, and location. Developers fix tests from a single view instead of piecing together context across tabs.
MCP-native test access
The TestDino MCP Server hands Cursor, Claude Code, and Claude Desktop a direct line to Playwright runs. Agents debug failures with debug_testcase, query runs by branch or environment, and rank flaky tests across recent history.
Predictable pricing
$39/month billed annually for up to 3 users with 25,000 executions included. No per-test overage. Free tier covers 5,000 executions and every core feature.
Steep learning curve
Many users report that Currents' interface presents a lot of data and can be hard to use for teams that want quick answers. This slows onboarding and leaves non-specialists struggling to scan the dashboard.
Basic error grouping
Failures cluster by error message alone, so the same bug written twice splits across buckets while unrelated tests with similar timeouts end up together. Triage requires developers to read through stack traces manually.
Limited flaky detection
A test is flagged flaky only when retries are enabled, and it fails, then passes. Teams running CI without retries could miss flakes for weeks.
Expensive pricing
Currents starts at $49/month for 10,000 test results, with no free plan, and each additional 1,000 tests adds $5. Small teams and CI-heavy suites often find that costs add up quickly.
| | |
|---|---|---|
| Pricing (starts at) | $39/month (billed annually) | $49/month (Team, 10K results) |
| Best for | Playwright test intelligence & management | Playwright/Cypress dashboards & CI debugging |
| Playwright integration | Native (trace viewer, error grouping, MCP) | Native (first-class) |
| Ease of use |  | |
| One-step CI setup | One tdpw upload line | currents-action / CLI wrapper |
Dashboards & Reporting | ||
| Unified Playwright dashboard | Basic dashboard | |
| Multi-tab test run detail | Summary, History, AI Insights & more | Run overview |
| Pull request insights (per-PR history) | ||
| Test ExplorerBrowse tests as a hierarchy, a flat list, or by tag. | ||
| Real-time streaming | Per-shard/worker | |
| Scheduled PDF reports (email) | Daily/Weekly/Monthly | |
Test Analytics | ||
| Analytics: trends & patterns | Basic analytics charts | |
| Code coverage, per-file | Istanbul, run-level | |
| Environment analytics | Pass-rate/flaky by env | Via tags/branches filter |
Debugging & Evidence | ||
| Built-in Playwright trace viewer | ||
| Screenshots & video replay | Embedded | |
| Console logs (per test) | Node + browser | |
| Visual diff comparison | Diffs as artifacts | |
| Smart error grouping | Message/stack/location | |
| Flaky detection (+ stability %) | Root-cause + % | |
| Playwright tags & annotations | Priority/owner/links/metrics | |
CI/CD Optimization | ||
| Rerun only failed tests | ||
| GitHub CI Checks quality gates | Per-env + mandatory tags | |
| Branch → environment mappingMatch each Git branch to the environment it runs against. | Exact/regex | |
| Smart rerun history (branch+commit) | ||
| Sharded / parallel run support | Per-shard live view | |
| Native CI breadth | GitHub, GitLab, Azure DevOps, TeamCity, Bitbucket, CircleCI, Jenkins | GitHub Actions, CircleCI, GitLab, Jenkins, Buildkite, Bitrise, AWS CodeBuild, Azure Pipelines |
| Self-managed GitLab | ||
Test Management | ||
| Test case management (suites, ownership) | ||
| Bulk test creation (PRDs/Jira/stories) | via MCP | |
| Release tracking (releases/cycles/sprints) | ||
| Exploratory / manual sessions | ||
| Import / export test cases | JSON/CSV/ZIP | |
AI & Automation | ||
| Local MCP (IDE agents) | Cursor/Claude Code/Copilot | |
| Remote MCP (web AI) | ||
| AI test run summary on GitHub PRs | ||
| AI test suite audit (audit score + report) | ||
| AI failure classification | ||
Integrations & Collaboration | ||
| Bug tracking breadth | Jira, Linear, Asana, monday | Jira, GitHub (webhook/API) |
| Slack notifications (run summaries) | App + webhooks | |
Platform & Security | ||
| Public API & CLIs | REST + tdpw / testdino | REST API + currents CLI |
| Project-level AI controls | Per-feature toggles | API key scoping |
| Compliance & certifications | ISO 27001, SOC 2 Type II, GDPR | SOC 2, SSO, SCIM (Ent) |
Plans & Pricing | ||
| Plan tiers | Free · Pro $39 · Team $79 · Enterprise | Team $49/mo · Enterprise (custom) |
| Free executions | 5,000/mo | Free trial only |
| Support | Chat + Slack Connect + Priority email | Chat + Email (Team) · Slack Connect (Ent) |
| Start for Free | ||
Feature-by-feature breakdown showing how each tool handles the areas that matter most to testing teams.
The Currents dashboard doesn't include a tabbed run detail view or separate analytics dashboards, and its PR integration runs through GitHub comments instead of a dedicated view. Scheduled reports arrive as email summaries without a PDF format, making executive-level sharing harder.
Error grouping in Currents clusters failures by error message alone, with no stack trace or location dimensions, and no dedicated visual regression comparison panel. The same root cause often ends up split across buckets, leaving developers to triage manually.
No AI failure classification and flaky detection is retry-based only. Teams without CI retries enabled can miss flakes entirely, while developers still read through logs manually.
list_testruns, pull full failure context with traces and artifacts through debug_testcase, and rank flaky tests across recent runs.The Currents MCP Server is read-only. Agents can fetch runs, tests, and specs, but cannot create or update manual test cases, suites, or annotations. Test management stays outside the agent loop, breaking AI-first workflows.
Merge-blocking quality gates and branch-regex environment mapping aren't part of Currents. Teams running staging, QA, and production branches must manage environment context outside the platform, which complicates per-environment trend analysis.
Currents doesn't include dedicated test case management.
Purpose-built capabilities that help Playwright teams ship faster and debug smarter.
Where each platform leads, and where it falls short.
Currents is a Playwright dashboard and test orchestrator focused on CI execution speed and flaky test management.
Smart Test Orchestration
The pwc-p client distributes tests across parallel workers using historical timing data.
Multi-Framework Support
Works with Cypress, Playwright, Jest, WebdriverIO, Vitest, and Nx.
Currents Actions Automation
Rule-based workflows auto-quarantine flaky tests, skip known offenders, or add tags based on run history and flakiness thresholds.
TestDino is a Playwright-native AI test intelligence platform that classifies failures, groups errors by root cause, and opens test data to AI agents through MCP.
AI-Powered Failure Classification
Every failure is tagged as Bug, UI Change, Unstable, or Miscellaneous with a confidence score, cutting triage time across the team.
TestDino MCP Server
Lets AI coding agents query Playwright test runs, debug failures with full retry and artifact context, detect flaky tests, and manage manual test cases and suites, all from the editor.
Multi-Dimensional Error Grouping
Failures cluster by message, stack trace, and location together, so the same root cause lands in one bucket instead of three.
CI/CD Optimization Stack
Rerun failed tests only, GitHub quality gates that block merges on flaky thresholds, and environment mapping for branch-to-env trends.
Verified reviews from QA and engineering teams running Playwright in production.
Analyzing failed test runs in CI used to take a lot of time. TestDino gives me a centralized dashboard for Playwright results with screenshots, logs, and failure trends. The automatic grouping and categorization of failures means I triage from patterns instead of reading each CI log.
Lead Software Engineer
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.
Lead QA Automation Engineer
TestDino shows us which tests are slowest, most flaky, and fail most often, which helps us prioritize improvements. We inherited an existing project, and it gave us the insights to take ownership of the suite and improve its reliability.
Senior QA Engineer
The interface is clean and easy to navigate, so getting started with test creation is straightforward. I like having both visual workflows and code-based options, and the dashboard makes it easy to review results and understand failures quickly.
QA Specialist
Support has been excellent, and the setup was straightforward. The interface is intuitive and gives a clear overview, and the pricing is competitive. The team is active, consistently shipping new features and improvements.
CTO & Co-Founder
TestDino is easy to use and delivers valuable analytics out of the box. The dashboard is clean and intuitive, and the initial setup was not difficult at all. I would rate it a nine for recommending it to colleagues.
Senior Quality Assurance Manager
Enterprise-grade security so your team can focus on shipping instead of worrying about data.
Secure authentication, role-based access control, and data encryption safeguard your test data in transit and at rest.
Persistent analytics with historical tracking deliver reliable insights about test performance, coverage, and release readiness.
Automated backups and retention policies maintain a complete history of test data. Project-scoped access prevents unauthorized changes.
Currents charges per test result above the 10K threshold, with overage at $5 per extra 1K. TestDino offers flat monthly pricing with predictable costs.
10,000 test results per month. Extra usage at $5 per additional 1,000 tests.
10 users
Up to 1 year data retention
Playwright native features
MCP Server, REST API, HTTP Webhooks
SOC2 Type 2 compliance
Chat and email support
For dev teams shipping to production. Flat pricing, no per-test overage.
25,000 test executions per month
Up to 3 users
90-day data retention
AI failure classification
TestDino MCP Server with read and write access
PR features and CI/CD optimization
Debugging features and trace viewer
Integrations with Jira, Linear, Asana, Slack
Stop wasting time on
flaky tests
Yes. TestDino plugs into your playwright.config.ts as a native reporter, so project structure, browser channels, retries, and traces appear as first-class data the moment your first run completes.
Side-by-side comparisons of features, pricing, and integrations to help you pick the right testing tool.
