Changelog
Follow new updates and improvements to Currents.
May 14th, 2025
Improved
@currents/playwright@1.13.0 focused on improving the efficiency of Playwright Orchestration. While testing the beta version of this feature one of our customers reported a decrease of Playwright CI tests from 42 to 29 minutes (~30% improvement).
The improvement was achieved by a more efficient use of Playwright Worker Processes + a highly concurrent nature of playwright test runner.
If you are already using orchestration, give it a try:
@currents/playwright@1.13.0introduces a new configuration optionorchestration.batchSizeset
orchestration.batchSizeto the number of workers defined inplaywright.config.tswhen
orchestration.batchSizeis set, in addition to an optimized spit of test files between the CI machines, the orchestration takes into account the # of workers in each machine
See an Example GitHub Repository.
Additional resources:
Playwright Parallelization techniques overview
Orchestration Setup instructions
April 25th, 2025
We are happy to announce the release of a dedicated reporter for Node.js Testing Framework.
You can run the Node.js tests, use the dedicated reporter and send the test results to Currents. See Documentation for more details.
Example setup
# npm install @currents/node-test-reporter @currents/cmd --save-dev
# node --test --test-reporter=@currents/node-test-reporter --test-reporter-destination=./report.xml **.test.mjs
# npx currents convert --input-format=junit --input-file=./report.xml --framework=node
# npx currents upload --key=XXX --project-id=YYY
Run example
April 15th, 2025
Improved
The Test Explorer just got a serious upgrade to help you spot troublemaker tests faster:
New tabular layout – A more compact, ergonomic table view with sortable columns makes scanning and comparing test data a breeze.
Group filter – Quickly slice your test list by group to narrow your focus.
Export results – Need to share results or dig deeper offline? You can now export the table with a single click.
Volume metrics – We’ve introduced Flakiness Volume, Failure Volume, and Duration Volume to help you identify the biggest contributors to CI noise—even if their raw failure rates are low. Read more.
UI quality-of-life upgrades – Subtle but meaningful improvements across the board: better spacing, inline actions and flexible layout.
It’s cleaner, faster, and more actionable. Dive in and explore.
April 4th, 2025
Improved
Fixed
Improvements
Improved support of running only previously last failed tests for runs created with Currents Orchestration
Bug Fixes
Improve the error message formatting for failed network requests
March 6th, 2025
Improved
We’ve released a new REST API endpoint for retrieving Test Results.
GET v1/test-results/:signatureUsing this endpoint you can get… the test results 🤠, filtered by tags, branches or test status, including details like:
individual attempts details
duration and timings
error details
flakiness indicator
metadata like git information, project etc.
Check out the documentation for details.
March 5th, 2025
Improved
includes Operator for Currents Actions
We’ve added a few additional Currents Actions operators to unlock more expressive configurations. The new operators allow evaluating lists (e.g. test tags or test title path).
For example, for the following expression <subject> <operator> <input>
includes- all of theinputlist values can be found in<subject>listincludes some- at least one ofinputlist values can be found in<subject>listmissing- all of the<input>values are missing from the<subject>listmissing any- any of the<input>values are missing from the<subject>list
Requires @currents/playwright@1.10.0
Annotation Filters for Test Results Chart
Playwright Annotations is a convenient way to augment your test results with metadata like Test Owners, Custom Notifications and more.
Now you can refine the Test Results and Test Flakiness charts using annotation type and annotation description values.
February 20th, 2025
Improved
Github
We’ve improved our integration with GitHub and Slack — now you can receive a single message for all groups in a run.
Click on “Single notification for all groups” under the GitHub integration in Project Settings > Integrations > Github to enable it. Read more.
Slack
Click on “Single notification for all groups” under the Slack integration in Project Settings > Integrations > Slack to enable it. Read more.
February 19th, 2025
Improved
We’ve improved our integration with GitHub - now you can connect your Currents account to multiple GitHub organizations.
Select the GitHub organization and repository in Project Settings > Integrations to enable GitHub comments, status checks. Read more.
February 11th, 2025
Improved
Fixed
Currents Dashboard
Improved notifications
We’ve revamped the internal implementation of the notifications and integrations system to support an increasing demand for more scenarios
A new option was added to Slack and GitHub integration settings to allow sending a single notification for multi-group runs (Slack, GitHub, GitLab)
Allow setting repository default branch - in preparation for future improvements and to allow tracking trends use the most recent data from the default branch as a reference.
We’ve switched selected customers to a secure Cloudflare R2 storage and have done the necessary work to allow bringing your own storage for improved security.
@currents/playwright v1.9.3
Allow using
currents.config.tsconfig file instead of providing CLI arguments or reporter configurationLimit the number of nested sibling steps to 2000
@currents/cmd v1.6.8
Improved support and documentation for Jest, Vitest and NodeJS Test Runner results
February 11th, 2025
New
We’ve been working on allowing a more granular control of the test results by adding more filters. The recent release allows filtering data in various views by group name.
For example, if you have different tests for different Playwright projects, you can filter the metrics by project name (groups).
We are planning to add more controls and filters like annotations, framework versions, OS etc.