How do you get web-test-runner to visit vite's server instead of trying to connect to some (random?) location?

[NullVoxPopuli]

Hello,
I have this error:

❯ pnpm test

> [email protected] test /Users/psego/Development/OpenSource/emberjs/glimmer-vm
> web-test-runner

# I patched in some extra logging
starting...
vite starting...
vite started...
	http://localhost:5173

2023-05-08T21:27:14.986Z ERROR webdriver: RequestError: connect ECONNREFUSED 127.0.0.1:4444
    at ClientRequest.<anonymous> (file:///<long-path>/node_modules/.pnpm/[email protected]/node_modules/got/dist/source/core/index.js:789:107)
    at Object.onceWrapper (node:events:628:26)
    at ClientRequest.emit (node:events:525:35)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.socketErrorListener (node:_http_client:494:9)
    at Socket.emit (node:events:513:28)
    at Socket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)


 ❌ Failed to create session.
Unable to connect to "http://127.0.0.1:4444/", make sure browser driver is running on that address.
If you use services like chromedriver see initialiseServices logs above or in wdio.log file as the service might had problems to start the driver.
    Error: Failed to create session.    

My web-test-runner.config.mjs:

import { vitePlugin } from '@remcovaes/web-test-runner-vite-plugin';
import { defaultReporter } from '@web/test-runner';
import { webdriverLauncher } from '@web/test-runner-webdriver';

export default {
  // Fake file, because we don't want @web/test-runner to build anything
  files: ['testem.js'],
  // Launches Vite
  plugins: [vitePlugin()],
  reporters: [defaultReporter({ reportTestProgress: true, reportTestResults: true })],
  browsers: [
    webdriverLauncher({
      automationProtocol: 'webdriver',
      path: '/',
      capabilities: {
        browserName: 'chrome',
        'goog:chromeOptions': {
          args: [
            // --no-sandbox is needed when running Chrome inside a container
            process.env.CI ? '--no-sandbox' : null,
            '--headless',
            '--disable-gpu',
            '--disable-dev-shm-usage',
            '--disable-software-rasterizer',
            '--mute-audio',
            '--remote-debugging-port=0',
            '--window-size=1440,900',
          ].filter(Boolean),
        },
      },
    }),
  ],
};

[NullVoxPopuli]

It seems the test runners tries to get going even before vite is booted.

I put

      await new Promise(resolve => setTimeout(resolve, 50_000));

in the vite plugin to try to see if vite is even booting correctly, and I went right to the webdriver error....
no waiting 50s at all.

2023-05-08T21:52:57.029Z ERROR webdriver: Request failed with status 404 due to Error: Response has empty body
2023-05-08T21:52:57.029Z ERROR webdriver: Error: Response has empty body
    at getErrorFromResponseBody

I also hard-coded the vite port to 4444 -- because I haven't seen any options to specify a page to visit.