microsoft / playwright

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
https://playwright.dev
Apache License 2.0
62.73k stars 3.38k forks source link

[Bug]: Debugger is getting hanged while debugging through playwright extension #30883

Closed sat1591 closed 1 week ago

sat1591 commented 2 weeks ago

Version

1.1.2

Steps to reproduce

  1. Create a sample tests in playwright TS
  2. Put a debugger on any line
  3. go to playwright extension
  4. select any test
  5. click on debug to running the tests in debug mode

Expected behavior

Expected the tests should start initiating the browser and hit the break point which I can debug.

Actual behavior

After clicking the debug button the tests are not running anything. The debugger is just hanged like I showed in screenshot. When downgraded my extension version to 1.0.22 the debugging is running as expected. This problem I have noticed in 1.1.1 and 1.1.2

image

Additional context

No response

Environment

System:
    OS: Windows 10 10.0.19045
    CPU: (4) x64 AMD EPYC 7763 64-Core Processor
    Memory: 4.90 GB / 15.95 GB
  Binaries:
    Node: 20.12.2 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
  IDEs:
    VSCode: 1.88.1 - C:\Program Files\Microsoft VS Code\bin\code.CMD
  npmPackages:
    @playwright/test: ^1.43.1 => 1.43.1
mxschmitt commented 2 weeks ago

Please retry in v1.1.3 which we just released.

mxschmitt commented 2 weeks ago

Please retry in v1.1.4 which we just released.

HarneyTester commented 1 week ago

Hi, we didnt raise the original ticket but we have the same issue in v1.1.4

pavelfeldman commented 1 week ago

We can't reproduce this issue. We need exact steps to be able to reproduce: exact project repo or a zip file, exact steps to follow.

HarneyTester commented 1 week ago

I'll see what I can put together. I actually think its the same as https://github.com/microsoft/playwright/issues/30743, although this is closed.

mxschmitt commented 1 week ago

@sat1591 @HarneyTester, could you try v1.1.5? This issue should be addressed in the latest extension update.

HarneyTester commented 1 week ago

Yes all working for me now. Thanks!