How to Run Tests in Playwright with the VS Code Extension

[@roblesrt]

Keep on coming... thanks for sharing!

[@samztang953]

Thanks for the video, very helpful. I wonder if there is UI button that I can run the 'last failed tests'. I know there is a option in the command line, like this npx playwright test --last-failed Is there a button for that in the UI?

[@PDuimelaar]

thanks for the update! I just have a couple of questions: - on your previous update, you talked about the new command to only execute failed tests. Is there any way we can configure this in our job in the build pipeline (azure). - Do you have an example on HOW we can use multiple configurations (lets say one for test env and one for prd env) in the build pipeline? Because we might want to run a subset of tests with different data (that we specified in the config) on prd.

[@Playwrightdev]

that command is only for development. for ci we have retries which will retry a test when failed. To use a different config use --config after the test run command: playwright.dev/docs/test-cli

[@redenjohnzarra9822]

I appreciate the setup with selectable configurations, especially since we're using a monorepo (kudos to you all). The thing that I don't like, however, is setting the cwd in the opened workspace - in our case, root of the project (both in run debug and run test). This causes environment configurations from the root to be used, and as our project setup is done inside the project folder (as it should be), it leads to issues. Although this can be fixed by opening a workspace only in my project folder, I also have dependencies and utilities to update outside of it. What would be nice is if there's a toggle to choose which cwd to use (workspace or config folder). I have actually cloned the git repo and manually compiled a .vsix file, which I am using until this is fixed. I hope you can address this, as I want to have an updated extension with the cool features you are developing. You're doing some great things guys and I can't thank you enough 💙

[@Playwrightdev]

can you submit this as a feature request on GitHub, thanks

[@bryanf]

Hi, many thanks for the detailed instructions, I am wondering where I can find the example code? The example I get by "npm init playwright@latest" doesn't contain setup.ts or other test files we used in the example, many thanks!

[@qasurfer]

I'd like to hear more about storage state, I guess I can look it up. All my tests login fresh for a clean experience but I can see how they can become unmanageable.

[@Playwrightdev]

sure check out this post: dev.to/playwright/a-better-global-setup-in-playwright-reusing-login-with-project-dependencies-14

[@qasurfer]

@@Playwrightdev Perfect thank you

[@Butterflywm8]

Cool video, BUT, it would be much more useful for this project to have the repo link on GitHub. I see lots of tests and settings on video, but we can not look into them to get a clear picture, would it be possible to share the link here?

[@scottishfoldmocha5875]

Hi, I have a test for clicking on disabled button, to expect no redirect, but test fails with timeout, even if I set noWaitAfter: true await button.click({noWaitAfter: true}); Is this limitation/defect in Playwright? Why does it expect navigation on disabled button and fails with timeout error? Is there any work around it? I know about button.dispatchEvent('click') will not wait for navigation, but that doesn't work with enabled button, I need to test that enabled button redirects on click and disabled doesn't redirect.

[@hito6464]

I wonder If you could make a video on how to write a test for Adobe Analytics and Google Analytics (dataLayer) requests, which fire on page load and clicks. How to verify the values in the payload of such requests.

[@Playwrightdev]

see if this helps: locator handler - kzbin.info/www/bejne/gZu2knyHgdGapNU

[@Acksakal]

Thank you for your content. I have a question: in my vscode (win 10) an inline green triangle button to run individual tests is not showing. Simply does not appear in UI of VsCode. Did anybody come across the same issue? If yes, how did you resolve it? Feedback appreciated.

[@Playwrightdev]

I recommend to file an issue on GitHub. Make sure to use latest Playwright, latest VSCode extension and latest VSCode.

[@Acksakal]

@@Playwrightdev All are up to date. Actually, I found the issue in my vscode settings.json. It turns out, I had this feature "editor.glyphMargin" set to false which was hiding those green play buttons 😅😅

[@WarrenLu-ct8dn]

Can you share the demo project?

[@WolfsGhostCodes-jx2lv]

Why don't I see the Projects section on the Playwright Tests tab? For reference see 0:51

[@Playwrightdev]

It might have different reasons, e.g. error in your config, missing Node.js, no Playwright installed etc. I recommend to file an issue on GitHub - happy to triage it from there. Ideally we then improve the error reporting based on the cause, so other users don’t run into it.