[BUG] Playwright for VSCode - No Playwright tests found.

[yogeshgadge]

Context:

"No Playwright tests found."
In the Testing - Test Explorer

vscode version: 1.79
Playwright Test for VSCode v1.0.13

This morning suddenly after the updates Playwright test are not showing up.

Developer Tools console is showing the error saying node not found.
It is found from bash/zsh shell as it is in the path

 ERR [Extension Host] Error: not found: node
at li (/Users/REDACTED/.vscode/extensions/ms-playwright.playwright-1.0.13/out/extension.js:9:1936)
	at ui (/Users/REDACTED/.vscode/extensions/ms-playwright.playwright-1.0.13/out/extension.js:9:2673)
	at async V (/Users/REDACTED/.vscode/extensions/ms-playwright.playwright-1.0.13/out/extension.js:14:966)
	at async Oe._runNode (/Users/REDACTED/.vscode/extensions/ms-playwright.playwright-1.0.13/out/extension.js:14:7618)
	at async Oe.getPlaywrightInfo (/Users/REDACTED/.vscode/extensions/ms-playwright.playwright-1.0.13/out/extension.js:14:3484)
	at async Ve._rebuildModel (/Users/REDACTED/.vscode/extensions/ms-playwright.playwright-1.0.13/out/extension.js:91:5625)
	at async Ve.activate (/Users/REDACTED/.vscode/extensions/ms-playwright.playwright-1.0.13/out/extension.js:91:4834)

• Playwright Version: 1.34.3
• Operating System: mac
• Node.js version: 18.16.0
• Visual Studio Code version: 1.79
• Playwright for VSCode extension version: v1.0.13
• Browser: Chromium
• Extra: my playwright.config.ts is located in /projects/foo-app/src/e2e/playwright.config.ts

Code Snippet

Help us help you! Put down a short code snippet that illustrates your bug and
that we can run and debug locally. For example:

Describe the bug

Add any other details about the problem here.

[yogeshgadge]

I believe this is same as #20332 I am using nvm and vscode can't find node ?

[mxschmitt]

Could you try to completely close vscode and start it again?

[yogeshgadge]

Yes I tried that. Also installed node using brew.

…

On Wed, Jun 14, 2023, 3:33 AM Max Schmitt ***@***.***> wrote: Could you try to completely close vscode and start it again? — Reply to this email directly, view it on GitHub <#23684 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASPWOGKZ2U3FKUCXHVTTMDXLFSL7ANCNFSM6AAAAAAZFGTPCI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[yogeshgadge]

Here is what worked - instead of clicking VSCode from Dock navigate to your project folder from open a bash and the open code code . and the errors are gone.

[mxschmitt]

Just to double check, did you before right click on the vscode icon in the dock and clicked on "Quit"?

[yogeshgadge]

I clicked "Quit Visual Studio Code". But I had even restarted my machine.

[yury-s]

Here is what worked - instead of clicking VSCode from Dock navigate to your project folder from open a bash and the open code code . and the errors are gone.

When you launch VSCode from terminal it inherits its environment including PATH variable. When launching from dock the PATH is likely different for some reason and node binary is not there. Try following the VSCode troubleshooting guide: https://code.visualstudio.com/docs/supporting/faq#_resolving-shell-environment-fails

There is also some relevant discussions in microsoft/vscode#21655 and https://stackoverflow.com/questions/66162058/vscode-complains-that-resolving-my-environment-takes-too-long

[yury-s]

Closing per the response above, feel free to open a new issue if it doesn't work.

[Neurovert]

Here is what worked - instead of clicking VSCode from Dock navigate to your project folder from open a bash and the open code code . and the errors are gone.

best response - works, thank you!

[jshtawayHR]

Here is what worked - instead of clicking VSCode from Dock navigate to your project folder from open a bash and the open code code . and the errors are gone.

This did not work for me.

[yogeshgadge]

Curious why does playwright need access to the shell? I am assuming that when vs code is started via a shell it's pkigins gets access to it

…

On Wed, Apr 24, 2024, 2:29 PM jshtawayHR ***@***.***> wrote: Here is what worked - instead of clicking VSCode from Dock navigate to your project folder from open a bash and the open code code . and the errors are gone. This did not work for me. — Reply to this email directly, view it on GitHub <#23684 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASPWOG2EJAROOITMJ277I3Y672XHAVCNFSM6AAAAAAZFGTPCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVGU3TKNRYHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>