Feature Request: Enhanced Playwright Integration - Support for Test Annotations, Trace Viewer, and Visual Testing

[li-zhixin]

Summary

As a Playwright user, I'm currently missing several key capabilities in ReportPortal's test reporting that are essential for comprehensive test analysis. This forces me to use both native Playwright reports and ReportPortal simultaneously, which creates inefficiency in our testing workflow.

Missing Features

1. Test Annotations Support

• Reference: https://playwright.dev/docs/test-annotations
• Description: Playwright test annotations (like test step) are not displayed or properly handled in ReportPortal
• Impact: Losing important test metadata that helps understand test behavior and requirements

2. Trace Viewer Integration

• Reference: https://playwright.dev/docs/trace-viewer-intro
• Description: Playwright's trace viewer functionality is not integrated into ReportPortal
• Impact: Cannot analyze detailed test execution traces, making debugging much more difficult

3. Visual Testing Capabilities

• Reference: https://playwright.dev/docs/test-snapshots
• Description: Visual testing results and screenshot comparisons are not properly displayed
• Impact: Visual regression testing results are not accessible within ReportPortal interface

Expected Outcome

Enhanced Playwright integration that includes:

• Display of test annotations in the ReportPortal UI
• Integration or linking to Playwright trace viewer
• Proper handling and display of visual testing results and screenshot comparisons

This would allow teams to use ReportPortal as the single source of truth for Playwright test reporting without losing critical debugging and analysis capabilities.

Use Case

Currently maintaining dual reporting systems creates overhead and fragments the testing workflow. A unified solution would significantly improve developer productivity and test result analysis efficiency.

[AmsterGet]

Hello @li-zhixin !
Thank you for your feedback, we greatly appreciate your use cases.
Since ReportPortal is a unified test results accelerator for any language/framework, your suggestions will be carefully reviewed by our team to see if they can be implemented in a way that is useful for all our users.

A brief explanation about test annotations:
We mainly support the annotations mentioned (fixme and skip mark a test as skipped in ReportPortal, describe groups tests into sets, step creates nested steps at the log level).
All of them work by default, except for steps - this option is disabled by default and can be enabled using the configuration option includeTestSteps.
Could you share a list of annotations that are missing from your setup?

[li-zhixin]

I apologize for my carelessness. I did not notice the default value of includeTestSteps. You can ignore the suggestion regarding Test Annotations Support. I apologize again for my oversight. I hope you will not overlook other suggestions because of this.

[ne0t3ric]

The trace viewer integration would be great, a lot of team uses this debugger for flaky tests which happens quite often when implementing end-2-end testing. A minima, would be great to have the attachment url in a hook (defined in rpConfig) so it could be exploited and read by a self hosted trace viewer for example