[BUG] Missing documentation about the VSCode extension

[AlexKomanov]

Context:

• Extra: VSCode Extension v.0.2.6

Describe the bug

The following chapter has missing information: https://playwright.dev/docs/getting-started-vscode#running-tests

In case we have several projects that cover several parts of the whole project, there is an option to get the following warning message:

In this case - the test/s will not be performed.

In our automation project - we have several projects that cover different sub-folders of the tests folder:

We need to provide the information for the extension - which of the project is the default, and only the tests in the chosen project will be performed. It is possible to choose all of them or the particular one:

The question is the following:

Is it by design? Correct behavior that is just not documented as well? Or maybe a bug?

[phcoliveira]

I made a PR addressing workspaces with multiple root folders and monorepos.

But I still think that the VS Code extension could be improved.

For example, in my explanation about monorepos, you can see a picture showing all tests from all packages. The first project, however, restricts the scope of the files to be found by having setting the property testDir to ./apps/client/tests.

IMHO, the testing tree should only show the matched test files from any given project. It seems to me that, at all times, the testing tree show all test files from all projects, and I find that very confusing.

[debs-obrien]

closing this as docs have been updated