vitest.workspace.json not discovering Tests

[ldrick]

Describe the bug

I have a workspace like that:

./frontend/projectA/vite.config.ts
./frontend/projectB/vite.config.ts
./backend
./not-a-npm-project
./e2e-tests

Right now I'd like to use the ./vitest.workspace.json because this is not a monorepo, neither it works well with vscode multi-root-workspaces due to many old school setup not so easy to change.

Unfortunately vitest vscode doesn't recognize the file or at least tests from both frontend-projects do not show up.

Reproduction

This is the vitest.workspace.json:

["frontend/*/vite.config.ts"]

System Info

I am working within WSL2 hosted in Windows 11

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[ldrick]

After trying little more around, I found vscode-jest#virtualfolders which provides enough to setup in the given folder structure.

If vitest would provide something like that, I could have 2 rootFolders (which indeed they are):

{
    "vitest.virtualFolders": [
        {
            "name": "Project A Unit Tests",
            "rootPath": "frontend/projectA/",
            "runMode": "on-demand",
            "vitestCommandLine": "npm run test --"
        },
        {
            "name": "Project B Unit Tests",
            "rootPath": "frontend/projectB/",
            "runMode": "on-demand",
            "vitestCommandLine": "npm run test --"
        }
    ]
}

[sheremet-va]

The extension was rewritten from the ground up in #253.

It should now support vitest.workspace.json file out of the box. If you still have the bug with a pre-release version, please open a separate issue.