You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several running tests workers should run without any connection issues to ChromeDriver (with same major version as Chrome).
INFO Running end-to-end tests ...
Launching up to 8 concurrent test worker processes...
Starting ChromeDriver on auto-generated port...
ℹ Connected to ChromeDriver on port undefined (1168ms).
...
What is actually happening?
All of the workers are unable to connect to ChromeDriver.
INFO Running end-to-end tests ...
Launching up to 8 concurrent test worker processes...
...
⚠ Failed to connect to ChromeDriver on localhost with port 9515.
This started to happen after updating @vue/cli-plugin-e2e-nightwatch from v4 to v5.0.8 (Nightwatch updated from v1 to v2).
This package has Nightwatch as dependency with version 2.0.5 (current -> 2.3.7).
In the Nightwatch version 2.2.3 was fixed the following issue.
The text was updated successfully, but these errors were encountered:
Version
5.0.8
Environment info
Steps to reproduce
Enabling test_workers on
nightwatch.conf.js
file and running script:npm test:e2e
What is expected?
Several running tests workers should run without any connection issues to ChromeDriver (with same major version as Chrome).
What is actually happening?
All of the workers are unable to connect to ChromeDriver.
This started to happen after updating @vue/cli-plugin-e2e-nightwatch from v4 to v5.0.8 (Nightwatch updated from v1 to v2).
This package has Nightwatch as dependency with version 2.0.5 (current -> 2.3.7).
In the Nightwatch version 2.2.3 was fixed the following issue.
The text was updated successfully, but these errors were encountered: