Changelog

@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.0 introduces a new configuration option orchestration.batchSize

• set orchestration.batchSize to the number of workers defined in playwright.config.ts

• when orchestration.batchSize is 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

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

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.

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

We’ve released a new REST API endpoint for retrieving Test Results.

GET v1/test-results/:signature

Using 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.

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 the input list values can be found in <subject> list

• includes some - at least one of input list values can be found in <subject> list

• missing - all of the <input> values are missing from the <subject> list

• missing any - any of the <input> values are missing from the <subject> list

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.

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.

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.