fix(browser): use correct project when filtering entries in the bro…

…wser mode (#7167)

packages/browser/src/node/plugin.ts

@@ -152,7 +152,9 @@ export default (parentServer: ParentBrowserProject, base = '/'): Plugin[] => {
       name: 'vitest:browser:tests',
       enforce: 'pre',
       async config() {
-        const project = parentServer.vitest.getProjectByName(parentServer.config.name)
+        // this plugin can be used in different projects, but all of them
+        // have the same `include` pattern, so it doesn't matter which project we use
+        const project = parentServer.project
         const { testFiles: allTestFiles } = await project.globTestFiles()
         const browserTestFiles = allTestFiles.filter(
           file => getFilePoolName(project, file) === 'browser',

test/browser/specs/runner.test.ts

@@ -1,18 +1,22 @@
+import type { Vitest } from 'vitest/node'
+import type { JsonTestResults } from 'vitest/reporters'
 import { readFile } from 'node:fs/promises'
 import { beforeAll, describe, expect, onTestFailed, test } from 'vitest'
 import { instances, provider, runBrowserTests } from './utils'
 
 describe('running browser tests', async () => {
   let stderr: string
   let stdout: string
-  let browserResultJson: any
+  let browserResultJson: JsonTestResults
   let passedTests: any[]
   let failedTests: any[]
+  let vitest: Vitest
 
   beforeAll(async () => {
     ({
       stderr,
       stdout,
+      ctx: vitest,
     } = await runBrowserTests())
 
     const browserResult = await readFile('./browser.json', 'utf-8')
@@ -28,6 +32,12 @@ describe('running browser tests', async () => {
       console.error(stderr)
     })
 
+    const testFiles = browserResultJson.testResults.map(t => t.name)
+
+    // test files are optimized automatically
+    expect(vitest.projects.map(p => p.browser?.vite.config.optimizeDeps.entries))
+      .toEqual(vitest.projects.map(() => expect.arrayContaining(testFiles)))
+
     // This should match the number of actual tests from browser.json
     // if you added new tests, these assertion will fail and you should
     // update the numbers