Run every test faster, for less.
Playwright's --shard splits spec files by file order, so every pull request waits on the slowest machine. Currents balances them by duration on the CI machines you already run. Runs finish up to 40% faster, and on spot instances CI cost is up to 70% lower.
Example run
12 spec files · 4 CI machines · chromium
Run timeline split with --shard in file order. Machine 1 gets the three longest spec files and runs for 7 minutes 41 seconds. The other three finish within 4 minutes 9 seconds and sit idle for 11 minutes 21 seconds in total.
Run timeline balanced by Currents from duration history. All four machines finish between 4 minutes 49 seconds and 4 minutes 52 seconds. Split with --shard, the same run took 7 minutes 41 seconds.
Same spec files, same machines. Only the split changes.
Your CI is only as fast as its slowest shard
A pull request waits for the last machine to finish, and every run pays for the whole suite.
Waiting on a pull request
DaysHow long Planable's pull requests took to merge before Currents. Every push waits for the slowest machine before anyone can trust the result.
Read the Planable storyA CI bill that grows
Every pull request and every re-run pays for the whole suite again. The more your team ships, the more each month costs.
Agent pull requests
Agents make this worse. Each agent pull request runs the suite again, often several times while the agent iterates, so the cost of a slow, unbalanced run now scales with agent use.
See how Currents verifies agent work
A live queue that balances every run
Currents keeps how long each spec file took in past runs. Each run starts from a queue of those files, longest first, and every machine takes the next one the moment it is free. When one machine runs slow, the others take the files it would have run.
- account/profile2m 4s
- admin/users2m 52s
- auth/login2m 45s
- billing/invoices51s
- cart/checkout47s
- cart/discounts1m 54s
- catalog/search2m
- orders/history52s
- orders/returns1m 9s
- settings/team1m 58s
- shipping/rates54s
- wishlist/share1m 17s
- orders/returns1m 9s
- shipping/rates54s
- orders/history52s
- billing/invoices51s
- cart/checkout47s
On your CI machines
Your tests run where they run today. Currents hands each machine its next spec file and records the results.
Spec files, for Playwright
Currents balances whole spec files, so one very long file still runs on one machine. Orchestration supports Playwright.
In every paid plan
Orchestration is included in every paid plan. The guide sets it up in your CI config.
Playwright orchestration docs (opens in a new tab)
Fail fast, re-run only what failed
A run that has already failed shouldn't keep your machines busy. Stop it early, then run again only the tests that broke.
Currents counts failed tests across every machine in the run. When they reach the number you set, the run is cancelled on all of them. Spec files already running finish and keep their results.
Fail fast docs (opens in a new tab)
Rules that keep the pipeline moving
Currents Actions quarantine, skip or tag the tests a rule matches, by file, test title, tag, project, error message, branch and more. Once the Currents fixture is in place, a rule needs no code change and no pull request.
- A flaky test stops blocking
- Quarantine flaky tests and they still run and report. A quarantined test's failure doesn't fail the run, so the pipeline keeps moving while someone fixes it.
- An expiry, if you want one
- Give a rule an expiry date, and Currents alerts Slack or email before it lapses.
- Only passes count
- A quarantined test counts toward usage only when it passes. Skipped tests never count.
- See what every rule touched
- The Affected Tests tab lists each test a rule quarantined, skipped or tagged.
Ask your agent
- Ask
Quarantine the tests that flaked more than 5% this week, until Friday.- Calls
- currents-get-tests-performance
- currents-create-action
- Answer
- 2 tests flaked more than 5% this week, at 8% and 6%. Created 2 quarantine rules that expire Fri 20 Nov.
Your agent can create, update, enable, disable and archive rules through MCP when the person who connected it is an Admin or Actions Admin. Every rule sits in the dashboard for the team to review.
A rule steps one known flake aside. Every other failure still has to pass.
Real failures still block the merge
Quarantine takes the noise out of the check and leaves the gate where it was. A real failure still turns the required check red, so green still means safe to merge.
- Quarantined · not blocking
- The known flake still runs and reports. Its failure no longer fails the check.
- Failed · blocking
- Any other failure fails Currents Tests, and the merge waits until it passes.
Required in Branch protection · GitHub
GitHub App docs (opens in a new tab)- cart › applies a discount codecart/discounts.spec.tsRunningPassed
- search › autocomplete suggests productscatalog/search.spec.tsRunningQuarantineNot blocking
- checkout › pays with a saved cardcart/checkout.spec.tsRunningFailed · blocking
Run on spot instances without losing tests
Spot instances cost less because the cloud can take them back at short notice. When your CI passes on the cloud's eviction notice, Currents moves that machine's spec files to a healthy one.
The run carries on and every file still reports. It works on orchestrated Playwright runs, on AWS, Azure or Google Cloud.
Read the spot instances guide (opens in a new tab)FundGuard on spot instances, with Currents
Read the FundGuard storyAWS
CI cost, down 50%
FundGuard's cost of running Playwright tests on AWS spot instances.
Azure
CI cost, down 90%
FundGuard's cost of running Playwright tests on Azure spot virtual machines.
Works with the CI you already run
Each provider has a setup guide in the docs. Orchestration has worked examples for GitHub Actions, GitLab, Jenkins and Nx.
- GitHub Actions setup guide (opens in a new tab)
- GitLab setup guide (opens in a new tab)
- Jenkins setup guide (opens in a new tab)
- CircleCI setup guide (opens in a new tab)
- Azure DevOps setup guide (opens in a new tab)
- Buildkite setup guide (opens in a new tab)
- AWS CodeBuild setup guide (opens in a new tab)
- Harness setup guide (opens in a new tab)
- Nx setup guide (opens in a new tab)
Your tests run on your own machines. Currents decides which machine takes which spec file and records the results.
Five teams published their before and after
Every number comes from a published case study. The label above it says what produced it.
Orchestration and spot instances
FundGuard
Read the FundGuard storyCurrents Orchestration
From about 80 to 40min
FundGuard's end-to-end pipeline, from about 80 to about 40 minutes.
Spot instances
CI cost, down 70%
FundGuard's CI/CD cost, on spot instances with Currents Orchestration.
Kittl
Read the Kittl storyCurrents Orchestration
Single-test time, down 50%
The average execution time of a single test.
Spot instances
Compute costs, down 60to80%
Kittl's compute costs on spot instances.
Other changes made with Currents
Ramp
Read the Ramp storyMoved to Playwright
CI fleet, down 62%
Ramp's CI machine fleet, after it moved to Playwright with Currents.
Sherpany
Read the Sherpany storyStability work and duration metrics
From about 18 to 11min
Sherpany's suite of about 900 tests, after stability work guided by duration metrics.
Planable
Read the Planable storyRan in parallel · Cypress, 2023
From 2 hours 45 minutes to 10min
Planable's end-to-end suite, once it ran in parallel.
“We have a fixed amount of time to make sure a code change does not regress our product. As the cadence of changes grew and the product features expanded this became more of a challenge, especially when taking costs into account.”
Gilad Dayagi / Director of Web Platform Engineering at FundGuardSee what your CI could save
Set four numbers from your own pipeline. The result uses two published figures: runs up to 40% faster with Currents Orchestration, and CI cost up to 70% lower on spot instances.
50 runs × 20 min × 30 days = 30,000 min · 30,000 min × 40% = 12,000 min · 30,000 min × 4 machines × $0.010 × 70% = $840
This is an estimate. The time saved depends on how unbalanced your suite is today. The cost figure assumes your CI machines move to spot instances.
Run it on your own suite (opens in a new tab)Faster CI without skipping tests
Test selection makes CI faster by running fewer tests. Currents makes the whole suite faster and cheaper to run, so every pull request is checked by all of it.
Skip tests to save time
chromium (4 machines)7 of 12 spec files ran
ranskipped, not verified
- A test selection tool runs the tests it judges affected by a change and skips the rest.
- A skipped test checks nothing on that pull request. If the selection misses, the break shows up after the merge.
- That gap matters more when agents write code nobody reads line by line.
Run all of them for less
chromium (4 machines)12 of 12 spec files ran
ranbalanced by duration
- Currents balances spec files across your machines by duration, so runs finish up to 40% faster.
- Fail fast counts failures across every machine and stops a failing run at the limit you set.
- Re-run only the failed tests, spread over all your machines.
- On spot instances, CI cost is up to 70% lower.
How Currents compares with sharding, hosted grids and test selection
Six questions to ask before you change how CI runs. Every answer about another tool is from that vendor's own docs or pricing page, checked in November 2026.
| Criterion | Currents | Playwright --shardBuilt into Playwright | Cypress Cloud | HyperExecuteTestMu AI, formerly LambdaTest | Test selection toolsDatadog Test Impact Analysis, CloudBees Smart Tests |
|---|---|---|---|---|---|
| Runs on your own CI machines | Yes | Yes | Yes | On its own cloud VMs, or a private cloud | Yes |
| Balances machines by duration history | Spec files, from a live queue | Splits by file or test count | Spec files, by past durations | Splits using past runs and statuses | Datadog: selects tests, no splittingCloudBees: bins by past duration |
| Spot instance support | Moves spec files off a machine the cloud evicts | Not documented | Not documented | Not documented | Not documented |
| Quarantine or skip without a code change | Quarantine, skip or tag by rule | Skips are set in test code or config | No built-in quarantine | Test Muting skips a test, by hand or after repeated failures | Datadog: quarantine or disableCloudBees: quarantine |
| Frameworks | PlaywrightCypress up to 12.17Others' results as JUnit XML | Playwright | Cypress | Selenium, Playwright, Cypress, Appium and more | Many, per language: Jest, Vitest, Playwright and more |
| Pricing model | Per test resultOrchestration in every paid plan | Free and open source | Per test result | Per parallel test | Datadog: per active committerCloudBees: custom quote |
Sources for the other products' cells
- Playwright --shard
- Cypress Cloud
- HyperExecute
- Test selection tools
- docs.datadoghq.com/tests/test_impact_analysis (opens in a new tab)
- docs.cloudbees.com/docs/cloudbees-smart-tests/latest/features/test-suite-parallelization (opens in a new tab)
- docs.datadoghq.com/tests/flaky_management (opens in a new tab)
- cloudbees.com/blog/smart-tests-high-failure-rate-tests-quarantine (opens in a new tab)
- docs.datadoghq.com/tests/setup/javascript (opens in a new tab)
- docs.cloudbees.com/docs/cloudbees-smart-tests/latest/send-data-to-smart-tests/record-test-results/record-test-results (opens in a new tab)
- datadoghq.com/pricing/list (opens in a new tab)
- cloudbees.com/products/saas-platform/pricing (opens in a new tab)
Test it against the CI you run now
Run your suite through Currents on the same machines, then compare the run time with your old runs. The numbers come from your own pipeline.
Start a 14-day free trial (opens in a new tab)Three steps to a faster pipeline
Minutes from signup to your first recorded run.
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 guidePrompt for your agentSet up this repository to report test results to Currents. Read https://docs.currents.dev/getting-started/setup-with-an-agent.md and follow it.Let Currents split the run
Swap --shard for one command. Currents balances spec files by duration on your own CI machines. Included in every paid plan.
Read the orchestration guideCI test step# Before npx playwright test --shard=${{ matrix.shard }}/${{ strategy.job-total }} # After npx pwc-p runGate the merge
Install the GitHub App and make the Currents check required. GitLab and Bitbucket too.
GitHub App docsPull requestSome checks haven’t completed yetAll checks have passed1 queued1 successful checkCurrents TestsRequiredWaiting to run1,204 passed · 0 flaky · 6m 12s
