To get real value from an automated test suite, it is not enough to write and run the tests in CI. What you do with the results matters just as much. A good reporting layer lets you see which tests passed, which failed, and more importantly, understand the reasons behind those failures.

For teams working in Playwright and Cypress, two tools often come up for this job: Currents and Datadog Test Optimization. Both promise to turn a raw CI run into something clear and readable, but they approach the problem from very different directions. We will look at what each one actually does, what it costs, and which kind of team it really fits.

Our quick take

Currents and Datadog Test Optimization both turn CI test runs into something you can actually read, but they solve the problem from opposite ends.

Currents is a Playwright and Cypress first dashboard. You point a reporter at it, and you get centralized traces, screenshots, videos, flaky detection, and test orchestration that load-balances specs across CI machines. It does one job, for one kind of team, and stays out of the rest of your stack.

Datadog Test Optimization is the testing slice of a full observability platform. It instruments tests in 7 languages, renders each run as an APM-style trace, and correlates failing tests with service logs, infrastructure metrics, and underlying traces. It is broad, deep, and priced per active committer.

If your pain is "My Playwright suite in CI is a black box," Currents is the more direct fit. If your pain is "I already live in Datadog and want my tests in the same pane of glass as everything else," Datadog wins on correlation. The rest of this article is the details behind that sentence.

And if your suite is specifically Playwright, it's worth keeping TestDino on your radar as you read. It's Playwright-native, with AI failure analysis and test case management built in, and you get that depth without taking on a full observability platform. We come back to why at the end.

Currents vs Datadog Test Optimization: Full feature comparison

What each tool actually is

Currents

Currents started life as the commercial evolution of the open-source Sory-Cypress project, so its roots are in Cypress. Today, the homepage leads with "All-in-one Dashboard for Playwright Testing," and Playwright is its primary focus.

The shape of it: you add a reporter to your Playwright or Cypress config, and every run streams into a cloud dashboard. You get one-click access to traces, screenshots, videos, and console output across all shards and CI machines. On top of that sit flaky detection, an algorithmic error grouping engine (Error Explorer, shipped late 2025), and "Smart Test Orchestration" that load-balances specs based on historical duration to cut wall-clock pipeline time.

What it deliberately is not: an application observability tool. It watches your tests in CI, not your services in production.

Datadog Test Optimization

Datadog Test Optimization is the testing-phase component of Datadog's CI/CD observability suite. (It is the product that was previously called CI Visibility, then Test Visibility, and is now Test Optimization.) It auto-instruments your test runs and renders each as a distributed trace, just as Datadog renders a production request.

That framing is the whole point. Because a test run is a trace, a test that calls an instrumented service shows you the full downstream trace: the service spans, the logs, the infra metrics, all in one timeline. For end-to-end testing, it can even integrate with RUM. It supports 7 languages and roughly 25 frameworks, so it is not a Playwright tool; it is a test tool that happens to support Playwright (version 1.18 and up).

The trade-off lives in that breadth. Because it instruments via a language tracer rather than a Playwright reporter, Playwright-specific artifacts (the trace viewer, video, projects, and streamed results) are not first-class as they are in a Playwright-native dashboard.

Pricing: Usage-based vs per-committer

This is where the two tools feel most different, because they bill on completely different axes.

Currents

Currents is usage-based. The public Team tier starts at $49/month for 10,000 test results per month, with an overage of $5 per additional 1,000 tests. The per-1K rate decreases as volume increases (larger plans are documented at roughly $3.32 per 1K). Annual billing gives you one month free. Data retention is up to 1 year (3 months hot, 9 months cold). An Enterprise tier adds SAML SSO, SCIM, Slack Connect, and bring-your-own-storage at custom pricing.

A "test result" is a single test execution including its artifacts. So your bill tracks how many tests you run, not how many people are on the team.

A free trial exists, but Currents does not publicly document the trial length or whether a card is required. Treat those as "ask sales" items.

Datadog Test Optimization

Datadog bills per active committer per month, plus usage: $20 billed annually, $24 month-to-month, $29 on-demand. An "active committer" is a Git author with at least 3 commits in a given month; bot commits and commits made directly in the GitHub UI are not counted. Each committer includes 1 million test spans per month (each test execution is a span), with an overage of $3 per additional million spans. Code Coverage is a separate per-committer add-on ($8–$12), though you get one coverage committer free per billed Test Optimization committer.

So the per-head figure is the floor, not the ceiling. A small team running a large or retry-heavy suite can blow through the included spans and incur span overage on top of the seat cost; the model is not flat per head.

There is no separately published perpetual free tier for Test Optimization beyond Datadog's standard 14-day platform trial.

And, critically, Datadog's headline value (correlating a failing test with the APM trace, logs, and infra metrics underneath it) only materializes if you also pay for those products:

• APM at roughly $31–$40 per host/month
• Log management at $0.10 per ingested GB plus $1.70 per million indexed events
• Infrastructure monitoring at $15–$23 per host.

Enable only the per-committer seats, and you get a competent test dashboard, but you lose the cross-stack correlation that was the reason to choose Datadog over a focused tool in the first place.

Datadog's overall pricing can be widely described as complex and hard to forecast. A documented high-watermark host model (a short scaling spike can bill the whole month at peak) and compounding usage meters mean bills can climb faster than expected, so model your real usage: committers, span volume, and any platform products you turn on before committing.

How to think about it

The honest comparison is not seat price vs. usage price. Currents and TestDino are standalone tools you can add (or remove) in an afternoon with a single, predictable bill.

Datadog Test Optimization is a line item on an observability platform, and its real cost depends on how much of that platform you light up to make it useful.

Map your committer count and your monthly span volume, and whatever APM/logs/infra you would need for correlation before you decide, not the $20 sticker alone.

Framework and Playwright fit

If your suite is Playwright (or Cypress), Currents gives you native, first-class handling: the time-travel trace viewer, screenshots, video replay, console logs, and live-streamed partial results that survive a runner crash. That is the experience it was built for.

Datadog supports Playwright as one of many frameworks via language-level tracer instrumentation rather than a Playwright reporter. You get test health, flakiness, and duration data, plus the correlation story, but not the Playwright-specific artifact depth. PHP, for what it is worth, is not supported by Datadog at all; Currents is JS-centric and does not target it either.

So the framework question splits cleanly:

1. Playwright/Cypress only, want artifact depth? Currents.
2. Polyglot suite across Java, Python, Go, .NET, and JS? Datadog covers all of it under one bill.

Where TestDino fits: if it's Playwright artifact depth you're after, but you also want built-in AI failure analysis and test case management that neither of these tools includes, that combination is the gap TestDino was built to fill. More on that at the end.

Flaky tests, orchestration, and cutting CI time

Both tools take flaky tests seriously, but with different mechanics.

Currents auto-activates flaky detection when retries are enabled, reports a flakiness rate, and offers a fail-fast option (failOnFlakyTests on Playwright 1.52+). Its bigger CI-time lever is orchestration: it load-balances specs across your CI machines based on historical duration, with marketing claims of up to 50% faster than native Playwright sharding, plus fail-fast mode and spot-instance support.

Datadog has a centralized Flaky Tests Management workflow with explicit states (Active, Quarantined, Disabled, Fixed). Quarantine lets a flaky test keep running without breaking your build. Its CI-time lever is Test Impact Analysis (formerly Intelligent Test Runner), which maps tests to code via per-test coverage and skips tests unaffected by a given change. So Currents makes the same tests run faster in parallel; Datadog runs fewer tests in the first place.

Those are genuinely different strategies, and the better one depends on your suite. A suite where every test touches shared code benefits more from orchestration; a large suite with good code isolation benefits more from impact analysis.

AI features

Both tools now expose an MCP (Model Context Protocol) server, so an AI coding agent like Claude Code or Cursor can query your test data. But the depth differs.

Currents is "AI-ready" rather than "AI-powered." It's an official MCP server that exposes test history to external agents, and ships an Agent Skill and an IDE extension. Critically, Currents performs no AI analysis of its own; the reasoning occurs within whatever agent consumes the data.

Datadog does run AI on its own data. It assigns each flaky test to 1 of 14 root-cause categories based on execution patterns, and its Bits AI Dev Agent (in preview) can auto-diagnose a flaky test and open a GitHub PR with a candidate fix validated against historical data. Its MCP server went GA in March 2026 with read and write tools for test events and flaky-test states.

If "let my IDE agent see my tests" is enough, both deliver. If you want the platform itself to categorize and propose fixes, Datadog is further along.

Integrations and ecosystem

Currents integrates with GitHub, GitLab, Bitbucket, Jira, Linear, Slack, Microsoft Teams, n8n, and HTTP webhooks. GitHub gets commit status checks and PR comments (PR comments need the GitHub App). It is a focused set aimed at the test-to-ticket loop.

Datadog integrates with itself, which is the entire pitch. Tests correlate with APM traces, logs, infra metrics, and RUM. Source-control features are richest on GitHub (PR comments are GitHub only), with GitLab and Azure DevOps linking and partial Bitbucket support. Notifications route through Datadog monitors to Slack, Jira, Teams, PagerDuty, and more.

The ecosystem question is really a lock-in question. Currents stay in its lane and are easy to add or remove. Datadog is most valuable when the rest of your observability already lives there, and switching away later means re-instrumenting.

Security and compliance

Currents holds SOC 2 Type 2 (achieved March 2025) and CSA STAR Level 1. Data is US-only (AWS us-east-1). SSO (SAML 2.0) and SCIM are Enterprise-only, and there is no self-hosted option for Currents itself (the self-host route is the separate OSS, sorry-cypress, Cypress only). ISO 27001 is not listed.

Datadog carries the full enterprise compliance roster: SOC 2 Type I and II, ISO 27001/27017/27018/27701, HIPAA, PCI DSS, GDPR, FedRAMP, CSA STAR, and more, all tracked in its public Trust Center. For a regulated enterprise, this is rarely a contest.

So which one should you pick?

Strip away the feature lists, and it comes down to one question: how wide is the problem you are solving?

• Pick Currents if your problem is bound to Playwright or Cypress tests in CI, and you want deep artifact handling, orchestration to cut pipeline time, and a tool you can add in an afternoon without adopting a platform.
• Pick Datadog Test Optimization if your problem is broader than tests; you run a polyglot suite; and the real value is seeing a failing test next to the service trace and logs that explain it, all inside an observability platform you (probably) already pay for.

Neither is wrong. They are aimed at different teams with different shapes of pain.

What Playwright teams actually want

Here is the gap both tools leave open.

Currents gives you Playwright depth but no test case management, no AI analysis of its own, and no release-level view. Datadog gives you breadth and correlation but treats Playwright as one of many frameworks, with no native reporter and no Playwright-specific artifact experience.

If you are a Playwright team that wants the artifact depth of a native tool, built-in AI that classifies your failures, and test management in the same place, that is a different product category.

TestDino is built for that middle.

• It is Playwright-native (built-in inline trace viewer, smart error grouping, flaky root-cause analysis)
• It classifies failures with AI rather than handing the data off
• It ships both local and remote MCP for Cursor, Claude Code, and Copilot, and it adds test case management, release tracking, and PR insights in one place.
• It is SOC 2 Type II, ISO 27001, and GDPR compliant.
• Setup is 1 line: tdpw upload.
• It starts free with 5,000 executions per month and all core features, with Pro at $49/month.

If "Currents vs Datadog" was really you asking "what is the best home for my Playwright tests in CI," it is worth a look before you decide.

FAQs