[BUG] Chromium is initiated before and after test runs if using VSCode extension when "show trace viewer" is selected

[davidjonesdialexa]

System info

• Playwright Version: [v1.37]
• Operating System: [Windows 10]
• Browser: [Chromium]
• Other info:

Happy to provide more details, but this issue does not seem to be related to my code, but rather the VSCode extension

When the following option is selected in the Test Explorer, and then I launch a test with either the test explorer or the green play buttons within spec files, the test runner attempts to open a Chromium instance before the test's Browser and after the test has finished if the test fails, presumably to open the html reporter. Chromium is currently blocked in my work environment so I get a security notification. The test, which runs on branded Chrome, runs correctly and the results show up in the Test Results output pane.

Steps

• Block chromium in your work environment
• select "show trace viewer" in the Test Explorer
• run a test using the vscode extension interface either in the Test Explorer or directly from a spec file

related to #26930

[pavelfeldman]

"Show trace viewer" is showing the live trace using the Chrome browser, so if Chrome is blocked it explains why the feature is not working.

[pavelfeldman]

Why was this issue closed?

Thank you for your contribution to our project. This issue has been closed due to its limited upvotes and recent activity, and insufficient feedback for us to effectively act upon. Our priority is to focus on bugs that reflect higher user engagement and have actionable feedback, to ensure our bug database stays manageable.

Should you feel this closure was in error, please create a new issue and reference this one. We're open to revisiting it given increased support or additional clarity. Your understanding and cooperation are greatly appreciated.