Error running web-test-runner from WSL

Hi,

I’m getting the following error when running web-test-runner src/**/*.spec.js in WSL

Error: Could not automatically find any installation of Chrome. If it is installed, use the “installationPath” option to set it manually. Use @web/test-runner-puppeteer or @web/test-runner-playwright for a bundled browser.

I have CHROME_PATH as follows:

CHROME_PATH=“/c/Program\ Files\ \(x86\)/Google/Chrome/Application/chrome.exe”

I’m able to run chrome from WSL command line with the variable above.

Any thoughts ?

Thanks,

[geoffrich]

For future reference, I ran into a similar issue where chrome launcher was trying to use my Windows Chrome installation, not my WSL Chrome installation. This was throwing the below error.

Failed to launch local browser installed at /mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe. This could be because of a mismatch between the version of puppeteer and Chrome or Chromium. Try updating either of them, or adjust the executablePath option to point to another browser installation. Use the --puppeteer flag to run tests with bundled compatible version of Chromium.

test/component.test.js:

 ❌ connect ECONNREFUSED 127.0.0.1:49515 

Chrome: |██████████████████████████████| 1/1 test files | 0 passed, 0 failed

The solution was to set an environment variable that points to my WSL installation.

export CHROME_PATH=/usr/bin/google-chrome

This can also be set in the launch options.

import { chromeLauncher } from '@web/test-runner-chrome';

export default {
  browsers: [
    chromeLauncher({
      launchOptions: {
        executablePath: '/usr/bin/google-chrome'
      },
    }),
  ],
};

[LarsDenBakker]

@dmondev sorry this issue was sitting here for a while. We delegate the logic for finding the installation to chrome-launcher. It runs inside node, are you sure that environment variable is available inside the unix subsystem? I removed one extra layer of abstraction on our side in https://github.com/modernweb-dev/web/pull/1146, and improved the error message. Perhaps you could try again?

@tvvignesh looks like it’s complaining about the chrome version, do you have an older version?