Make red mean broken. Fix it in minutes.

Currents separates flaky tests from real regressions, so you can trust your CI again. Every failure comes with the evidence your team, or your agent, needs to fix it.

  • Cursor
  • Red Hat
  • Autodesk
  • Snowflake
  • n8n
  • ServiceNow
  • LangChain
  • US EPA
  • Palo Alto Networks
  • Canadian Red Cross

Every flaky test teaches your team to ignore red

A retry that goes green hides the flake. Do it often enough and nobody reads red anymore. Coding agents learn the same habit: asked for a green build, they add a wait and move on.

Now with . Every guess gets an answer.

Currents tells flaky from broken on every run

  • Every execution on record. Test History shows each execution of a test across runs and branches: red failed, purple passed but flaked.
  • Broken tests, by name. Project Overview lists the tests that passed, then failed every run since on a branch.
  • On the pull request too. The GitHub run comment prints each test's last 30 days, with the base branch beside it.

Keep flakes out of the build, not out of sight

  • Out of the build, still on record. A quarantined test still runs and reports its results. With Playwright, its failure doesn't fail the run.
  • Your agent writes the rule, in view. Ask it to quarantine a test until Friday. The rule sits in Actions with the rest, and Currents alerts Slack or email before it lapses.
  • Or make flakes block the merge. Teams that want it strict set failOnFlakyTests, and any flaky test fails the run.

Red to fixed in minutes, by you or by your agent

10:02. Currents comments on the pull request: checkout › applies a promo code failed, and one other test flaked. It failed 2 of 2 runs on this branch and none on main, so this change broke it.

  • The right cause, nearly 4× as often

    Given the same CI failures, a model found the right root cause nearly 4 times as often with Currents' failure analysis as with the Playwright output and the test code alone.

  • The alert reaches the owner

    Annotate a test or set a mention rule, and the Slack alert mentions its owner, with Fix with AI on it for their agent.

  • The issue comes filled in

    From the failure in Currents, create or link a Jira or Linear issue that carries its error and stack trace.

Let agents fix tests without letting them hide failures

The Playwright Best Practices skill teaches web-first assertions, solid locators and how to find a flake's real cause. It installs from GitHub, no Currents account needed.

Terminal
npx skills add https://github.com/currents-dev/playwright-best-practices-skill

Fix the causes that cost the most

  • One cause behind many red tests. Error Explorer groups Playwright errors by category, action and target, and counts the tests each one breaks.
  • Ranked by what each test costs. Test Explorer sorts by impact, rate times executions, so a test that runs often can outrank a flakier one.
  • The CI time red costs you. Project Overview adds up the CI time spent on runs that finished with failures.

Watch your flaky rate fall

  • Better or worse at a glance. Six Project Overview tiles show the change since the previous period.
  • A year of history. Analytics keep 12 months, enough to show a fix held.
  • Reports that come to you. A scheduled summary lands in email or Slack, so nobody has to log in.

Sherpany cut flaky tests from 5% to 0.1%

  • Sherpany

    Flaky test rate

    From about 5% to 0.1%

    Sherpany's flaky tests as a share of its Playwright suite, before and with Currents.

  • n8n

    Flaky test rate

    From about 2 to 3% to 0.3%

    n8n's flaky test rate. The drop spans its move from Cypress to Playwright.

“Currents gave us the tools to lay a solid foundation for a fast, reliable end-to-end test suite.”
Sherpany QA Team

Three steps until red means broken

Minutes from signup to your first recorded run.

  1. Record every run

    Start a trial, then add the reporter and your project's keys to CI.

    Start a 14-day free trialRead the setup guide
    Prompt for your agent
    Set up this repository to report test results to Currents. Read https://docs.currents.dev/getting-started/setup-with-an-agent.md and follow it.
  2. Gate the merge

    Install the GitHub App and make the Currents check required. Flaky tests are marked and real failures block the merge. GitLab and Bitbucket too.

    GitHub App docs
    Pull request
  3. Connect your agent

    Add the Currents MCP server and sign in. Your agent reads failures, history and traces.

    Connect Cursor, Codex or ChatGPT
    Terminal
    claude mcp add --transport http --scope user currents https://mcp.currents.dev/mcp

Questions teams ask

Trust red again