nvm compatibility

[troppoli]

We use nvm to manage our node version on windows.

I've just updated wdio from 7.3x to 8.14 and wdio-electron-service from 3.5.1 to 4.3.0. When I run, I can see that the proper electron chromerdriver gets pulled down and cached. The wido runner on the other hand seems to think nothing is setup and attempts to download the driver for my installed chrome and fails.

I pulled this repo down and ran the tests. The launcher.spec.ts fails

launcher.spec.ts > on windows platforms › should execute a JS chromedriverCustomPath via the bat file
AssertionError: expected 'C: \Program Filds \nodejs\node.exe' to include 'windows\node* ) test/launcher .spec.ts:160:49
158
{ mock:
'config' },
159
);
160| expect (process.env.WDIO_ELECTRON_NODE_PATH). toContain(iswin? 'windows \Inode* : 'bin/node"); 

Before I dive deeper, is this a red flag?

-s

[troppoli]

I made a simple repo by cloning the electron quickstart, then running
npm init wdio and gave the following responses.

? A project named "electron-quick-start" was detected at "C:\gitlab\wdio-electron-trouble\electron-quick-start", correct? Yes
? What type of testing would you like to do? Desktop Testing - of Electron Applications
> https://webdriver.io/docs/desktop-testing/electron
? What is the path to your compiled Electron app? ./dist
? Which framework do you want to use? Mocha (https://mochajs.org/)
? Do you want to use a compiler? Babel (https://babeljs.io/)
? Do you want WebdriverIO to autogenerate some test files? Yes
? Where should these files be located? C:\gitlab\wdio-electron-trouble\electron-quick-start\test\specs***.js
? Which reporter do you want to use? spec
? Do you want to add a plugin to your test setup?
? Do you want to add a service to your test setup? electron
? Do you want me to run npm install Yes

Setting up Babel project...
✔ Success!

Installing wdio packages:

• @wdio/local-runner@latest
• @wdio/mocha-framework@latest
• @wdio/spec-reporter@latest
• wdio-electron-service
• @babel/register
• @babel/core
• @babel/preset-env
  This setup exhibited the same trouble. It ignores the electron config and goes for the local browser:

C:\gitlab\wdio-electron-trouble\electron-quick-start>npm run wdio

electron-quick-start@1.0.0 wdio
wdio run ./wdio.conf.js

Execution of 1 workers started at 2023-08-10T17:18:22.162Z

2023-08-10T17:18:22.179Z DEBUG @wdio/utils:initialiseServices: initialise service "electron" as NPM package
2023-08-10T17:18:22.240Z DEBUG electron-service: launcher received options: {
appPath: './dist',
appName: 'dave',
appArgs: [ 'foo', 'bar=baz' ],
chromedriver: { logFileName: 'wdio-chromedriver.log' },
electronVersion: '23.1.0'
}
2023-08-10T17:18:22.243Z DEBUG electron-service: setting chromedriver service options: {
logFileName: 'wdio-chromedriver.log',
chromedriverCustomPath: 'C:\gitlab\wdio-electron-trouble\electron-quick-start\node_modules\wdio-electron-service\bin\chromedriver.exe'
}
2023-08-10T17:18:22.244Z INFO chromedriver: Initiate Chromedriver Launcher (v8.1.1)
2023-08-10T17:18:22.245Z INFO @wdio/cli:launcher: Run onPrepare hook
2023-08-10T17:18:22.245Z DEBUG electron-service: downloading Chromedriver for Electron v23.1.0...
2023-08-10T17:18:22.246Z DEBUG electron-service: chromedriver download config: {
version: '23.1.0',
artifactName: 'chromedriver',
force: false,
cacheRoot: undefined,
platform: undefined,
arch: undefined
}
2023-08-10T17:18:22.252Z DEBUG electron-service: assets downloaded to C:\Users\stroppoli\AppData\Local\electron\Cache\aa87dbcf7862ac804df9d46cb5e9a4f6ec81289bedb90aa64d3922d9ebd37c63\chromedriver-v23.1.0-win32-x64.zip
2023-08-10T17:18:22.494Z DEBUG electron-service: assets extracted
2023-08-10T17:18:22.495Z INFO chromedriver: Start Chromedriver (C:\gitlab\wdio-electron-trouble\electron-quick-start\node_modules\wdio-electron-service\bin\chromedriver.exe) with args --port=9515 --url-base=/
2023-08-10T17:18:22.525Z INFO chromedriver: Starting ChromeDriver 110.0.5481.100 (4be7a36f7cb943af6118e449bbab494b43dcaddd-refs/branch-heads/5481_77@{#14}) on port 9515
2023-08-10T17:18:22.526Z INFO chromedriver: Only local connections are allowed.
2023-08-10T17:18:22.526Z INFO chromedriver: Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
2023-08-10T17:18:22.534Z INFO chromedriver: ChromeDriver was started successfully.
2023-08-10T17:18:22.624Z DEBUG @wdio/cli:utils: Finished to run "onPrepare" hook in 379ms
2023-08-10T17:18:22.628Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2023-08-10T17:18:22.628Z DEBUG @wdio/cli:utils: Finished to run "onWorkerStart" hook in 0ms
2023-08-10T17:18:22.630Z INFO @wdio/local-runner: Start worker 0-0 with arg: run,./wdio.conf.js
2023-08-10T17:18:22.637Z DEBUG @wdio/local-runner: Send command run to worker with cid "0-0"
[0-0] 2023-08-10T17:18:23.427Z INFO @wdio/local-runner: Run worker command: run
[0-0] 2023-08-10T17:18:23.774Z DEBUG @wdio/runner: init remote session
[0-0] 2023-08-10T17:18:23.776Z DEBUG @wdio/utils:initialiseServices: initialise service "electron" as NPM package
[0-0] 2023-08-10T17:18:23.841Z DEBUG electron-service: setting browser capabilities {
[0-0] browserName: 'chrome',
[0-0] 'goog:chromeOptions': {
[0-0] binary: './dist/win-unpacked/dave.exe',
[0-0] args: [ 'foo', 'bar=baz' ],
[0-0] windowTypes: [ 'app', 'webview' ]
[0-0] }
[0-0] }
[0-0] 2023-08-10T17:18:23.843Z DEBUG @wdio/utils:shim: Finished to run "beforeSession" hook in 0ms
[0-0] RUNNING in chrome - file:///C:/gitlab/wdio-electron-trouble/electron-quick-start/test/specs/test.e2e.js
[0-0] 2023-08-10T17:18:23.943Z DEBUG @wdio/runner: init remote session
[0-0] 2023-08-10T17:18:23.944Z INFO webdriver: Initiate new session using the WebDriver protocol
[0-0] 2023-08-10T17:18:23.952Z INFO webdriver: Downloading Chromedriver v115.0.5790.171
[0-0] 2023-08-10T17:18:24.418Z ERROR @wdio/runner: Error: Download failed: server returned code 404. URL: https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/115.0.5790.171/win64/chromedriver-win64.zip
[0-0] at file:///C:/gitlab/wdio-electron-trouble/electron-quick-start/node_modules/@puppeteer/browsers/src/httpUtil.ts:96:23
[0-0] at ClientRequest.requestCallback (file:///C:/gitlab/wdio-electron-trouble/electron-quick-start/node_modules/@puppeteer/browsers/src/httpUtil.ts:66:7)
[0-0] at Object.onceWrapper (node:events:628:26)
[0-0] at ClientRequest.emit (node:events:513:28)
[0-0] at ClientRequest.emit (node:domain:489:12)
[0-0] at HTTPParser.parserOnIncomingClient (node:_http_client:693:27)
[0-0] at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
[0-0] at TLSSocket.socketOnData (node:_http_client:534:22)
[0-0] at TLSSocket.emit (node:events:513:28)
[0-0] at TLSSocket.emit (node:domain:489:12)
[0-0] at addChunk (node:internal/streams/readable:315:12)
[0-0] at readableAddChunk (node:internal/streams/readable:289:9)
[0-0] at TLSSocket.Readable.push (node:internal/streams/readable:228:10)
[0-0] at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)
2023-08-10T17:18:25.260Z DEBUG @wdio/local-runner: Runner 0-0 finished with exit code 1
[0-0] FAILED in chrome - file:///C:/gitlab/wdio-electron-trouble/electron-quick-start/test/specs/test.e2e.js
2023-08-10T17:18:25.262Z INFO @wdio/cli:launcher: Run onWorkerEnd hook
2023-08-10T17:18:25.263Z DEBUG @wdio/cli:utils: Finished to run "onWorkerEnd" hook in 1ms
2023-08-10T17:18:25.263Z INFO @wdio/cli:launcher: Run onComplete hook
2023-08-10T17:18:25.264Z DEBUG @wdio/cli:utils: Finished to run "onComplete" hook in 0ms

Spec Files: 0 passed, 1 failed, 1 total (100% completed) in 00:00:03

2023-08-10T17:18:25.265Z INFO @wdio/local-runner: Shutting down spawned worker
2023-08-10T17:18:25.518Z INFO @wdio/local-runner: Waiting for 0 to shut down gracefully
2023-08-10T17:18:25.520Z INFO @wdio/local-runner: shutting down
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

[goosewobbler]

As of v5, the Electron service works with WDIO 8.14.0 and up. We still need to update the WDIO configuration wizard for the new version so recommend users manually configure for now.

[goosewobbler]

@christian-bromann I'm updating the WDIO config wizard for the new version, hopefully will be done this week

[anshitbansal21]

@goosewobbler Unrelated to this but I am planning to use wdio-electron-service in my project but we currently use
"webdriverio": "7.7.5"

I am relatively new to this and learning more about the WebdriverIO framework, is there somewhere from where I can understand which packages are compatible/ or not by myself?

[christian-bromann]

@anshitbansal21 I recommend using latest WebdriverIO. There are no docs on what is compatible and what not since there are too many possibilities how you can set up WebdriverIO. This video is a good start: https://www.youtube.com/watch?v=iQNxTdWedk0

[anshitbansal21]

Got it. Already seen that video 😄 Thanks for creating that!