Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Running issues in debug does not work and ends up in multiple different situations. #30827

Closed
KennySporck opened this issue May 15, 2024 · 4 comments

Comments

@KennySporck
Copy link

Version

1.1.1

Steps to reproduce

  1. Install playwright for VS code version 1.1.1 extension.
    Either:
  2. Go to the text explorer or file explorer
  3. Run a test in debug via right-mouse button and 'Debug test'
    OR
  4. Go to the terminal
  5. Enter the following command: npx playwright test 'testfile' --debug

Expected behavior

The test starts and runs in debug and breaks on breakpoints.

Actual behavior

Test runs from test explorer:
The session does not start and the test indicaties a start-up spinner animation in the test explorer.
It is also not possible to stop the test from being initiated and the user is forced to restart VS Code.

Test runs via terminal:
The session starts but breaks on the beforeEach section of the test. The user can manually resume the test by pressing resume in the debug window.

Additional context

A roll back to version 1.0.22 resolved the issue.
Since i did not know at first hand that playwright was updated, I tried several things that did not resolve the issue:

  • Reinstall playwright
  • Reinstall VSCode

Environment

Playwright 1.1.1
@mxschmitt
Copy link
Member

Might be the same as #30743 - if its about debugging ends up in a hang / stall.

@pavelfeldman
Copy link
Member

Please follow the BUG issue template so that we could reproduce your issue. That's the only way we can fix it, please help us pinpointing it!

@mxschmitt
Copy link
Member

@KennySporck please try VSCode extension v1.1.5

@KennySporck
Copy link
Author

@KennySporck please try VSCode extension v1.1.5

Issue seems to me resolved in v.1.1.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants