test: browser tests to include project name

vitest-dev · Dec 25, 2024 · 45ba01c · 45ba01c
1 parent 9c9e69b
commit 45ba01c
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/test/browser/specs/benchmark.test.ts b/test/browser/specs/benchmark.test.ts
@@ -4,7 +4,8 @@ import { runVitest } from '../../test-utils'
 test('benchmark', async () => {
   const result = await runVitest({ root: 'fixtures/benchmark' }, [], 'benchmark')
   expect(result.stderr).toReportNoErrors()
-  // TODO 2024-12-11 check |name| when it's supported
-  expect(result.stdout).toContain('✓ basic.bench.ts > suite-a')
+  expect(result.stdout).toContain('✓ |chromium| basic.bench.ts > suite-a')
+  expect(result.stdout).toContain('✓ |firefox| basic.bench.ts > suite-a')
+  expect(result.stdout).toContain('✓ |webkit| basic.bench.ts > suite-a')
   expect(result.exitCode).toBe(0)
 })
diff --git a/test/browser/vitest.config.unit.mts b/test/browser/vitest.config.unit.mts
@@ -8,6 +8,7 @@ export default defineConfig({
         singleFork: true,
       },
     },
+    reporters: 'verbose',
     setupFiles: ['./setup.unit.ts'],
     // 3 is the maximum of browser instances - in a perfect world they will run in parallel
     hookTimeout: process.env.CI ? 120_000 * 3 : 20_000,