Running a Windows Chrome binary from WSL not working

[csvan]

• Node Version: 9.8
• Protractor Version: 5.1
• Angular Version: N/A
• Browser(s): Chrome 65
• Operating System and Version Windows 10 Enterprise
• Your protractor configuration file

Currently, the following config can be added in order to make WSL (Windows Susbsystem for Linux) use the locally installed Chrome on Windows in order to run component tests:

  capabilities: {
    browserName: 'chrome',
    version: '',
    platform: 'ANY',
    specs: [path.join(process.cwd(), 'features', '**', '*.feature')],
    chromeOptions: {
      binary: "/mnt/c/Program\ Files\ \(x86\)/Google/Chrome/Application/chrome.exe",
      args: ['--no-sandbox', 'lang=en-US', '--disable-gpu', '--always-authorize-plugins',
        'user-data-dir=node_modules/.cache/chrome/',
        'disk-cache-dir=node_modules/.cache/chrome/',
        'load-extensions=node_modules/.cache/chrome/',
      ],
    },
    loggingPrefs: {
      driver: process.env.LOG_LEVEL_DRIVER,
      server: process.env.LOG_LEVEL_SERVER,
      browser: process.env.LOG_LEVEL_BROWSER,
      performance: 'ALL',
    },
  },

However, this just results in Chrome simply launching, but not navigating to the actual system under tests.

[DouglasLivingstone]

@rfgamaral has been able to get this working by explicitly using the Windows versions of Selenium and WebDriver: microsoft/vscode#49908 (comment)

[rfgamaral]

@rfgamaral has been able to get this working by explicitly using the Windows versions of Selenium and WebDriver: microsoft/vscode#49908 (comment)

If I got this right, Chrome runs on Windows so you need to use Windows paths and protractor runs through WSL so you need WSL paths for the protractor configuration. And since Chrome runs on Windows it also needs Selenium Windows binaries. That's the Gist of it.

[DouglasLivingstone]

Think so! Trying to get this working myself :-)