As a testing process matures, running the tests is rarely the hard part anymore. The real challenge becomes organising everything around them: the test cases, the runs, the results, and the decisions a team makes based on all of it. This is where a dedicated platform starts to earn its place.

For teams weighing their options, two paid and hosted tools often sit side by side: Allure TestOps and Currents. They can look similar at first glance, yet they are built for genuinely different jobs. One manages an entire testing practice, manual and automated alike, while the other goes deep on debugging Playwright and Cypress runs in CI. We will look at what each one does, how they are priced, and which kind of team each is really meant for.

Our quick take

Both Allure TestOps and Currents are paid, hosted services that make test runs manageable for teams. The difference is scope.

Allure TestOps is a full Test Management System (TMS). It unifies manual and automated testing in one place: test cases, test plans, launches, AQL-driven dashboards, two-way Jira integration, and the ability to trigger CI runs from the platform. It is framework-agnostic and management-first. It sits above your CI as a governance and analytics layer; it does not run tests itself.

Currents is a focused Playwright and Cypress CI dashboard. It goes deep on automated runs: native trace and video access, flaky detection, error grouping, and test orchestration that load-balances specs across CI machines. It is debugging-first and Playwright-first.

So this is a breadth-vs-depth decision. If you need to manage an entire testing practice (manual and automated testing, cases, plans, governance), TestOps is built for that. If you need the deepest possible view of a Playwright suite running in CI, Currents is built for that. The rest is detail.

And if your suite is specifically Playwright, it's worth keeping TestDino on your radar as you read. It brings test management and Playwright-native depth together in one place, with AI failure analysis on top. We come back to why at the end.

Allure TestOps vs Currents: Full feature comparison

What each one actually is

Allure TestOps

Allure TestOps, by Qameta Software, is a commercial Test Management System plus reporting and analytics platform. Its own docs describe it as a "Test Operations Swiss army knife" covering "the entire life cycle for testing for both manual and automated tests." It links manual and automated testing in one hub.

The key thing to understand is that TestOps does not execute your tests. It sits above your CI. It manages test cases and plans, triggers CI jobs, ingests results (via the Allure result format), and provides dashboards, analytics, and governance on top. One launch corresponds to one CI workflow run. It supports both a managed Cloud edition and a self-hosted Server edition.

Currents

Currents is a hosted CI test dashboard, Playwright-first (with Cypress roots from the open-source sorry-cypress project). You add a reporter to your config and runs stream into the service. It centralizes traces, screenshots, video, and console output across every CI machine, then layers on flaky detection, algorithmic error grouping (Error Explorer), and "Smart Test Orchestration" that load-balances specs across machines to cut pipeline time.

Currents is not a test management system. There is no manual testing, no test plans, no test-case design workflow. It is a debugging and CI-optimization tool for automated suites.

The core difference: Manage a practice vs debug a suite

Everything else follows from this.

Allure TestOps answers "how do I manage all of my testing?" It blends manual and automated testing, stores test cases as living documentation ("Smart Test Cases" that auto-update from automated runs), organizes work into test plans and launches, tracks defects with two-way Jira sync, and exposes everything through Allure Query Language (AQL) for custom dashboards and KPIs. It can trigger and rerun CI jobs across multiple CI systems from inside the platform. This is a platform for a QA org.

Currents answers "what happened in my Playwright runs and how do I fix it fast?" It centralizes artifacts, finds flakes, groups errors, and speeds up the pipeline. This is a tool for an automation team.

If you need both, you are looking at two different product categories, not two competitors in one category.

Pricing: Per seat vs per usage

The two tools bill on different axes, which is the single most practical thing to model.

Allure TestOps (per user)

Cloud is graduated per active user per month:

• 1–30 users: $39/user/month
• 31–50 users: $36/user/month
• 51–100 users: $34/user/month
• 101+ users: $30/user/month

Self-hosted Server starts at $39/user/month for 5–50 users (50+ is contact sales), with a 3-month minimum term and a 5-user minimum. Cloud billed annually gets a 10% discount. There is a 14-day free trial (no card required; the instance goes read-only after day 14 if you do not pay). No free-forever tier.

Cloud includes 60 GB of storage per instance, and that is a hard cap (Qameta's docs say it "cannot be changed for a SaaS instance" today). Teams that need more buy additional storage through sales, so the per-seat price is not the whole story: a heavy Playwright suite that stores a lot of videos, screenshots, and traces can hit that ceiling and carry a usage-based storage cost on top of the seats.

So your bill tracks headcount. A 5-person team is around $195/month; a 30-person team is around $1,170/month.

Currents (per usage)

Currents is usage-based: from $49/month for 10,000 test results, with overage at +$5 per additional 1,000 (the per-1K rate drops with volume). Annual billing gives one month free. Data retention is up to 1 year. Enterprise (custom) adds SAML SSO, SCIM, and bring-your-own-storage.

So your bill tracks how many tests you run, regardless of team size.

How to choose

A small team running a large suite tends to favor a per-seat model like TestOps, since the seat count, not the test count, drives most of the bill, with the caveat that artifact volume still has to fit inside the 60 GB storage cap noted above, or you pay for more.

A large team running a modest suite tends to favor usage-based pricing like Currents, since you pay for runs rather than headcount. Map your real headcount against your monthly test volume and your artifact storage before deciding, because the two models cross over at very different points.

Playwright depth

Allure TestOps ingests Playwright through the generic Allure result format, where Playwright is 1 of 55 supported frameworks. Screenshots render inline as attachments and steps show in the scenario. Still an, inline Playwright trace viewer is not confirmed in TestOps (it exists in the open-source Allure Report, but for the commercial platform, it was described as "on the radar" with no confirmation it shipped). In practice, the trace is likely a downloadable attachment you open in the standalone Trace Viewer.

Currents is purpose-built for Playwright artifacts: one-click time-travel trace viewer, screenshots, video replay, console logs, all centralized across CI machines, with real-time streaming that survives a runner crash. First-class, by design.

So, for raw Playwright debugging depth, Currents is the more native experience. TestOps trades that depth for framework breadth.

Where TestDino fits: Currents gives you Playwright depth, TestOps gives you management breadth. If you want both in one place, plus AI that actually analyzes failures, TestDino is built for that middle ground. Full detail at the end.

Orchestration and CI

This is the sharpest functional differentiator.

Allure TestOps does not run tests, so it does not orchestrate or load-balance.

What it does instead is two-way CI integration: you can trigger, stop, and rerun CI jobs from the platform, and select jobs across different CI systems for a test plan. The underlying CI, not TestOps, handles any parallelization. It supports a broad set of CI systems natively (Jenkins, GitHub, GitLab, TeamCity, Bamboo, Bitbucket, Azure DevOps, CircleCI, and more).

Currents orchestrate. Its "Smart Test Orchestration" load-balances spec files across your CI machines based on historical duration, with marketing claims up to 50% faster than native Playwright sharding, plus fail-fast mode and spot-instance support. It actively makes your runs faster.

So Currents speeds up execution; TestOps coordinates execution.

Flaky tests and error handling

Allure TestOps detects flaky tests using its own heuristic (at least 3 status transitions over the most recent 10 executions) and offers mute management to suppress a known-failing test from launch stats with a reason. Error handling is via regex-based "Defects" plus two-way Jira sync. Note that the defect matching is the regex you configure, not AI.

Currents auto-detects flaky tests with a stability percentage across stored history (activated when retries are enabled), offers a fail-fast option, and groups errors algorithmically via Error Explorer.

Both handle flakes and failures competently; Currents leans toward automated debugging signals, TestOps toward management workflows (mute, defect tracking, Jira).

AI and MCP

Neither tool runs its own AI failure analysis today, but both have moved into the MCP era.

Allure TestOps shipped an official, built-in MCP server in release 26.1.1 as a public beta, with tools for AI agents covering test-case CRUD, shared steps, test-result search, mute management, and issue details. The docs flag that "this feature may be subject to additional fees in future releases," so treat it as a maybe-paid beta. Its triage is otherwise regex-based, not AI.

Currents ships @currents/mcp (version 2.0, October 2025), plus an Agent Skill and IDE extension. Like TestOps, Currents performs no AI analysis of its own; the reasoning occurs within the agent that consumes the data.

So both expose data to your agent; neither has a built-in AI engine that diagnoses failures for you.

Deployment, data residency, and compliance

This is where the two differ in ways that matter for procurement.

Allure TestOps offers both Cloud (SaaS) and self-hosted Server (Kubernetes, Docker Compose, DEB, RPM). Cloud data lives in the EU (AWS Frankfurt).

• On security: the certifications it cites (SOC 1, SOC 2, ISO 27001) are AWS's data-center certifications, rather than an independent audit of the product itself, so phrase.
• The product does provide SSO (SAML, OIDC, LDAP, Okta), RBAC, audit logs, and 256-bit TLS. The self-hosted option is the strongest answer for teams that need full data control.

Currents is cloud-only (no self-hosted Currents), with US data residency (AWS us-east-1).

• It holds SOC 2 Type 2 (its own, achieved March 2025) and CSA STAR Level 1.
• SSO (SAML) and SCIM are Enterprise-only. ISO 27001 is not listed.

Quick read: TestOps wins on deployment flexibility (self-host, EU residency); Currents has its own SOC 2 Type 2 attestation. Which matters more depends entirely on your compliance requirements.

So which one should you pick?

• Pick Allure TestOps if you need to manage a whole testing practice: manual & automated testing, test cases & test plans, governance, a polyglot suite across many frameworks, two-way Jira integration, AQL analytics, and the option to self-host on EU infrastructure. It is a TMS first.
• Pick Currents if you run Playwright or Cypress and want the deepest CI debugging experience: native artifacts, flaky analytics, error grouping, and orchestration that actually cuts pipeline time, billed on usage rather than seats.

The two are genuinely aimed at different jobs. Some orgs even run both: TestOps as the management layer, a CI dashboard for automated-run depth.

What Playwright teams actually want

If you read all of that and thought, "I want the management features of TestOps but the Playwright depth of Currents, in one place, with AI that actually analyzes my failures," then neither is a clean fit.

TestOps is framework-agnostic and management-first, so Playwright is 1 of 55 adapters, and the trace experience is not native. Currents is Playwright-deep but is not a test management system and doesn't run any AI of its own.

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 "Allure TestOps vs Currents" was really about finding a single platform that supports both management and Playwright-native depth, it is worth a look before you commit.

FAQs