Browser tests don't run in parallel with `browser.enabled = true`

[timganter]

Describe the bug

When running a single test file using playwright in webkit, chromium, and firefox in a workspace, they run sequentially instead of in parallel.

Reproduction

Steps to reproduce

1. Download this stackblitz: https://stackblitz.com/edit/vitest-dev-vitest-ezbb8s
2. npm install (locally)
3. npm test (locally)

You should see that the browser tests run locally. Confirmed by @hi-ogawa over Discord who suggested making an issue.

Video of repro

sequence.mov

System Info

MacBook Pro with `Total Number of Cores: 12 (8 performance and 4 efficiency)`

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.

[hi-ogawa]

I just found there's TODO for this.

vitest/packages/browser/src/node/pool.ts

Lines 125 to 132 in 5e6de27

	// TODO: paralellize tests instead of running them sequentially (based on CPU?)
	for (const [project, files] of groupedFiles.entries()) {
	if (isCancelled) {
	break
	}
	await executeTests(method, project, files)
	}

Probably you can patch this to Promise.all and see how it goes. I think the concern is that running multiple browsers can be heavy especially on CI with less resource.

    await Promise.all(groupedFiles.entries().map(async ([project, files]) => {
      await executeTests(method, project, files)
    }))