Back to changelog

@currents/playwright 1.5.0

Playwright Test Annotations allows augmenting test results with additional metadata, for example: a Jira ticket number or Test Rail tracking id. Starting…

@currents/playwright 1.5.0

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 the Fail Fast strategy, which allows you to automatically interrupt CI runs after a certain number of test failures. You can configure this in Project Settings or via the CLI using --pwc-cancel-after-failures <number | false>.