Changelog

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

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

New

Playwright Test Annotations allows augmenting test results with additional metadata, for example: a Jira ticket number or Test Rail tracking id. Starting from version 1.5.0 Currents will store test annotations for the recorded tests, the annotations will show up in the dashboard.

Use case: test owners
Some test annotations have a special purpose, for example:

 testInfo.annotations.push({ 
    "type": "owner",
    "description": "johnSmith"
 })

Using type:owner has a special meaning in the dashboard - it will designate… a test owner. Test owner can be a person or a team.

We are working on incorporating the concept into our integrations and across the dashboard - e.g. sending notifications to a person or a team when their test fails, allowing filtering tests by their owner.

Let us know if you have more use cases that involve annotations.

Fixes

• Retry reporting results when certain network requests fail

• Better support for Fail Fast strategy, which allows to automatically interrupt CI runs when a certain number of tests failed. Can be configured in Project Settings or via CLI using --pwc-cancel-after-failures <number | false>