Changelog

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.

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.ts config file instead of providing CLI arguments or reporter configuration

• Limit 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

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.

📝 Introducing Run Notes: A new way to collaborate in Currents. Use notes to document failures, flag issues, or share insights with your team.

• Notes are visible to all users, just below the run title.

• Adding, editing, or removing notes is exclusive to admins.

Writing and running tests is just one step in a more comprehensive workflow. With the recent launch of the Currents Actions Engine, we are enabling teams to automate their testing-related workflows.

Currents Actions, combined with detailed reporting, integrations with third-party tools, test result histories, and observability metrics, unlocks these scenarios using a flexible set of rules and actions. It replaces ad-hoc in-house solutions with a single platform accessible to the entire team.

For example:

• Conditionally and temporarily skip or quarantine a test.

• Dynamically add a tag.

• Send an alert or open a ticket if a test becomes flaky.

• Intelligent selection of tests for CI runs: only high-impact tests run on each commit, while nightly jobs run the full test suite.

We are planning to extend the capabilities of the Actions Engine to implement more actions that support best practices of the testing workflows.