[Feature] Expose Trace-Viewer as a static web application available in Playwright documentation page.

Playwright has a CLI command for showing the Trace Viewer web application, that helps visualize the steps a Playwright script executed. This can be useful for debugging broken tests, by visually inspecting why the test broke.

I’d like to avoid the need to download the tracer file for my test session, and viewing my trace via the CLI command, and instead I would like to be able to display such session in a public web app, by providing a url to my tracer log file.

For example, the Trace Viewer could be hosted at the address: https://trace-viewer.playwright.dev/ and I would like to pass a url to my trace log file as a url parameter: ?tracePath=https://some-domain.com/trace_logs.zip. The Trace Viewer web app could then load the file via an XHR request, and allow debugging my Playwright script.

What do you think about such a solution? Would others find it useful? I think that way we could pass artifacts from CI systems directly to the static web app for rendering.

[neil-morrison44]

@Evilweed That sounds more like what I was suggesting here https://github.com/microsoft/playwright/issues/9026

You could deploy the traces as pages then link / iframe them into your report rather than a 3rd party website where you still have to upload the trace (which I think is what this issue suggests) or run the cli.

[pavelfeldman]

This is now done, we’ll provide more details as a part of the release notes.