Regression: Debugging in Playwright Test for VSCode does not work anymore

[kora-rider]

Version

Since 1.43.0 and also in 1.44.0

Steps to reproduce

Precondition: clone repo https://github.com/kora-rider/Playwright_testing

1. Put the breakpoint in VSCode to any row in the test file with the name "TC001_úspěšné_přihlášení.spec.ts"
2. Run debug

note: In case there is no breakpoint it runs well

Expected behavior

Run the browser and stop the test on a certain breakpoint.

Actual behavior

The browser does not run and the VSCode plugin gets stuck, even not possible to stop the debugging.

Additional context

No response

Environment

System:
    OS: macOS 14.4.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 61.38 MB / 16.00 GB
  Binaries:
    Node: 21.0.0 - /opt/homebrew/bin/node
    npm: 10.7.0 - /opt/homebrew/bin/npm
  Languages:
    Bash: 3.2.57 - /bin/bash
  npmPackages:
    @playwright/test: ~1.44.0 => 1.44.0

[bhushantbn]

I have also faced same problem on vs-code extension in Ubuntu 22.04.4 LTS

look nothing happens. before that launch it works fine but now somehow vs-code extension not execute the test.

need to close vs code every time which is very time consuming.

[mxschmitt]

Bisected to:

• b41b802...da2b099
• 1.43.0-alpha-2024-03-20 bad
• 1.43.0-alpha-2024-03-19 good

Filed upstream bug: microsoft/vscode-js-debug#2009

Seems to be fixed in VS Code insiders.

@kora-rider could you try VSCode insiders?

[kora-rider]

@mxschmitt I tried VSCode insiders, but the behaviour is the same as the VSCode. I tried a plugin Playwright Test for VSCode
v1.1.1.

[mxschmitt]

@kora-rider which VSCode insiders version are you using?

[kora-rider]

@mxschmitt The last one:

Version: 1.90.0-insider (Universal)
Commit: bbc4ba1eff648ee542972589216f211b7a6a08f2
Date: 2024-05-14T05:49:42.658Z
Electron: 29.3.1
ElectronBuildId: 9464424
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.4.0

[mxschmitt]

@kora-rider could you try using the latest 18.x or latest 20.x release? These are LTS releases - while 21.0.0 is more of a very early version without bugfixes included.

See here: https://nodejs.org/en/download

[kora-rider]

@mxschmitt I tried to install Node 20.X LTS, but it does not help. It only works when I downgrade Playwright to version 1.42. This configuration works for me:

System:
OS: macOS 14.4.1
CPU: (8) arm64 Apple M1 Pro
Memory: 37.98 MB / 16.00 GB
Binaries:
Node: 20.13.1 - /opt/homebrew/bin/node
npm: 10.5.2 - /opt/homebrew/bin/npm
Languages:
Bash: 3.2.57 - /bin/bash
npmPackages:
@playwright/test: ~1.42.0 => 1.42.1

[iedgeleybistech]

The v1.1.1 release of the VSCode Playwright Extension seems to be the culprit. Rolling back to the previous version brings back debugging.

[webdevpchoi]

Confirming the same - on v1.1.1, clicking any of the test folders from the extension panel results in an infinite loader and the actual tests in the folder do not appear in the dropdown in the panel and therefore cannot click each individual test to run/debug.

Reverting back to an 1.0.22 seems to resolve the problem temporarily.

[occo-lbl]

v1.1.1では、拡張パネルからテストフォルダのいずれかをクリックすると、無限ローダーが発生し、フォルダ内の実際のテストがパネルのドロップダウンに表示されないため、個々のテストをクリックして実行/デバッグすることはできません。

1.0.22に戻すと、問題が一時的に解決するようです。

In my case, if I stop running tests from the vscode extension while debugging is running, I end up in an infinite loader state.
To resolve this condition, I need to restart vscode.

[guido-visser]

In my case, if I stop running tests from the vscode extension while debugging is running, I end up in an infinite loader state. To resolve this condition, I need to restart vscode.

Experiencing the same issue here. Ctrl/Cmd + Shift + P -> Reload Window is a workaround, but it's very annoying. Or just revert the extension back to version 1.0.22, like mentioned above.

[occo-lbl]

Bak seems to have been resolved 6 hours ago!
Please check it out!

https://github.com/microsoft/playwright-vscode/releases/tag/v1.1.2

[mxschmitt]

@kora-rider could you try v1.1.4?

[kora-rider]

@mxschmitt I tried, but it's still the same.

[gbmhunter]

v1.1.4 is still broken for me (debug won't work). Like above, reverting to v1.0.22 fixed the issue for now.