How teams scale Playwright in CI. For humans and agents.
Debug failures, catch flaky tests, and speed up tests in CI. Turn your test suite into the verification layer that lets you ship at agentic speed.
From failing to fixed, backed by evidence
“Our use of Currents has greatly reduced test troubleshooting time, as well as flaky test detection time.”
Every attempt keeps its Playwright trace, screenshots, video, visual diffs, console and network logs next to the error.
Open any trace in one click, without digging through CI artifacts.
FailedCheckout › pays with a saved cardFailed# 1Error: expect(page).toHaveURL(expected) failed8sError DetailsScreenshots1Videos1Attachments3checkout/payment.spec.tsError: expect(page).toHaveURL(expected) failedExpected pattern: /\/order\/\d+/Received string: "http://localhost/checkout"Timeout: 5000ms Call log: - Expect "toHaveURL" with timeout 5000ms 9 × unexpected value "http://localhost/checkout"
Test observability that keeps up with your agents
“Currents has been a game-changer for our testing process. We can now pinpoint and address flakiness, ensuring reliable test results and increased confidence in our testing process.”
Charts track run status, duration, flakiness and suite size over time, filtered by branch, tag or environment.
Scheduled reports send the top regressions to email or Slack.
Sep 23 - Oct 06
Don't let tests become your CI bottleneck
“Speed, reliability, availability & insightful feedback are the main qualities one looks for in a test orchestration & reporting tool. Currents has outperformed in all these areas and has become an integral part of our CI/CD pipeline.”
Assigns spec files to CI machines from a live queue, ordered by historical duration, so every machine finishes at about the same time.
No manual splitting or file renaming.
Up to 50% faster
From your editor to CI, fully integrated
“The team was fascinated when they started to use Currents. They were getting real-time results, and our international communication channel was flooded with excitement.”
Why teams choose Currents
The memory your agents don't have
An agent starts every session from zero. Currents keeps months of runs, flakes and failures, and hands that history to whoever picks up the fix, person or agent.
?Red means broken. Green means ship.
People learn to ignore a flaky test. Agents can't. Currents separates flakes from real failures, so agents stop chasing noise and your team stops writing off real bugs as flakes.
CI in half the time, for a fraction of the bill
Every agent pull request is another CI run. Currents cuts each one’s time by up to 50% and its cost by up to 70%.
Say yes to faster releases
Agents ship more code than anyone can review by hand. Currents proves each change works, with before-and-after evidence on the pull request and checks that block a failing merge.
