[Bug]: Artifact traces copy command

[stychu]

Version

1.52.0

Steps to reproduce

Not sure how to reproduce it with ease, but I will describe the case.

We have playwright tests running in azure pipelines. When tests fail we generate the report artifact to be able to download it. The report artifact is names something like playwright-report-230221-1 which is being downloaded as a zip file. Once unpacked we get a folder with report named playwright-report-230221-1 when I open the index file and try to view the traces for the failed test I get this

The Playwright Trace Viewer must be loaded over the http:// or https:// protocols.
For more information, please see the [docs](https://aka.ms/playwright/trace-viewer-file-protocol).

When I change the folder name to playwright-report and open the traces again I get this

The Playwright Trace Viewer must be loaded over the http:// or https:// protocols.

You can open the report via npx playwright show-report /Users/.../Downloads/playwright-report from your Playwright project. Copy Command
For more information, please see the [docs](https://aka.ms/playwright/trace-viewer-file-protocol).

Here I can copy the command and run it npx playwright show-report /Users/.../Downloads/playwright-report which is not great experience to view the traces but now it works.

Expected behavior

I would expect that No matter the folder name of the playwright reports it should deduce its name and absolute path to it and show the screen with the copy command option so I dont need an extra step with renaming the folder just to playwright-repost

Actual behavior

It can't show the screen with copy command when the folder of report is named something different than playwright-report

Additional context

No response

Environment

System:
    OS: macOS 15.0.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 68.28 MB / 32.00 GB
  Binaries:
    Node: 20.19.0 - ~/.local/state/fnm_multishells/59216_1748617274537/bin/node
    npm: 10.8.2 - ~/.local/state/fnm_multishells/59216_1748617274537/bin/npm
    pnpm: 9.9.0 - ~/.local/state/fnm_multishells/59216_1748617274537/bin/pnpm
  Languages:
    Bash: 3.2.57 - /bin/bash
  npmPackages:
    @playwright/test: 1.52.0 => 1.52.0

[pavelfeldman]

Not sure what you mean - I can open report via npx playwright show-report foobar when it is in the foobar folder.

[stychu]

Right...

1. Do any playwright test run that fails at least one test and generates playwright-report
2. Copy playwright-report folder to some other destination on the hard drive (Downloads for example)
3. Open folder
4. Open index.html in the browser
5. Click on failed test suite
6. Click on traces page preview
7. See the page with:

The Playwright Trace Viewer must be loaded over the http:// or https:// protocols.

You can open the report via npx playwright show-report /Users/.../Downloads/playwright-report from your Playwright project. Copy Command
For more information, please see the [docs](https://aka.ms/playwright/trace-viewer-file-protocol).

Now

1. Go back to that copied folder
2. Rename the folder to something like playwright-report-123
3. Open renamed folder
4. Open index.html in the browser
5. Click on failed test suite
6. Click on traces page preview
7. See the page with:

The Playwright Trace Viewer must be loaded over the http:// or https:// protocols.

For more information, please see the [docs](https://aka.ms/playwright/trace-viewer-file-protocol).

^^^ No suggestion for the npx command to cppy.

[MRYisus2895]

Use the command "npx playwright show-report "

This will open the report on a localhost and from there you can now open the trace viewer.