test(browser): add integration test for project name encoding

- Replace unit test mock with a real browser integration test
- Add fixture with project name containing an ampersand ('&')

Author: dkkim0122

test/browser/fixtures/project-name-encoding/basic.test.ts

@@ -0,0 +1,5 @@
+import { expect, test } from 'vitest'
+
+test('basic test', () => {
+  expect(true).toBe(true)
+})

test/browser/fixtures/project-name-encoding/vitest.config.ts

@@ -0,0 +1,14 @@
+import { defineConfig } from 'vitest/config'
+import { provider } from '../../settings'
+
+export default defineConfig({
+  test: {
+    name: 'Components & Hooks',
+    browser: {
+      enabled: true,
+      provider,
+      instances: [{ browser: 'chromium' }],
+      headless: true,
+    },
+  },
+})

test/browser/specs/client-url.test.ts

@@ -0,0 +1,15 @@
+import { expect, test } from 'vitest'
+import { runBrowserTests } from './utils'
+
+test('runs tests correctly when project name contains special characters', async () => {
+  const { stderr, stdout, exitCode } = await runBrowserTests({
+    root: 'test/browser/fixtures/project-name-encoding',
+  })
+
+  // Prior to the fix, this would fail with a WebSocket connection error or similar
+  expect(stderr).toBe('')
+  expect(exitCode).toBe(0)
+  expect(stdout).toContain('Test Files  1 passed')
+  // Confirm the project name is correctly displayed (meaning it was parsed correctly)
+  expect(stdout).toContain('Components & Hooks')
+})