Annotations, Steps, UI changes

📝 Test Annotations

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

Starting from version @currents/playwright@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"
})

CopyCopied!

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.

---

👟 Inline Steps View

One of the unique features of Currents reporter for Playwright is how we upload the results. Instead of waiting for the whole test or a spec file to complete, we stream step-level information. That allows to capture very detailed information - even if playwright or CI machine crashes, we still send and present the last reported step.

The recent release exposes step-level information within test details view for more convenient and effective troubleshooting.

For example, one of our clients uses test steps as a “documentation” - they give steps descriptive names, so team members can quickly understand what’s happening in a test just by glancing at the reported steps.

---

🌼 UI changes

We revamped the UI for more convenient browsing:

• split test attempt details into tabs (error details, screenshots, videos, traces, steps)
• improved the onboarding and setup instructions to help new users start using the platform