📢 Playwright VS Code Extension Project Management

[pavelfeldman]

FAQ VS Code Extension

Q: There is no play button next to the test name in my test file, what happened?

In order for the green button to appear next to the test name in your file you need to have the project for that test selected in the project section of the Playwright sidebar. You will then see the tests in the test explorer and be able to run them by clicking the play button from the explorer or the green play button directly in the file.

Q: Setup project only runs if it is checked, why?

This is a change in behavior, now consistent with the UI Mode. It allows bypassing setup project if needed and is useful when re-running the same test over and over, while the setup is already performed.

Q: My config file is missing in the drop-down of configs, how do I fix it?

If your project contains more than one playwright configuration file, you can switch between them by first clicking on the gear icon in the top right corner of the Playwright sidebar. This will show you all the configuration files in your project. Select the configuration files you want to use by checking the checkbox next to each one and clicking on the 'ok' button.

Q: Global setup no longer runs each time I run a test. Why?

• The first time your tests run we run global setup. Global setup now runs only once.

• You can tear down your test manually by clicking Run global teardown from the Setup section in the Playwright sidebar.
• To manually rerun global setup click the Run global setup option from the Setup section in the Playwright sidebar.
• When debugging tests, global setup will re-run automatically before your tests to ensure isolated environment and better repeatability of the issues.

Q: My working directory is now workspace folder. Why?

• cwd used to point to the config folder, now we start tests from the workspace folder.
• Usually, your terminal is in workspace folder, so we are making it consistent with your CLI and CI experience.
• If this change affected you, you are using local file names in your tests. Make sure to resolve them, use path.join(__dirname, '../name') or similar before you pass those names into the fs module methods.