nightwatch - session not created - unable to connect to renderer
See original GitHub issueVersion
3.9.3
Reproduction link
https://if-this-is-a-real-requirement-just-close-and-ill-move-on
Environment info
Environment Info:
System:
OS: macOS 10.14.5
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Binaries:
Node: 10.15.0 - ~/.nvm/versions/node/v10.15.0/bin/node
Yarn: 1.17.3 - ~/.nvm/versions/node/v10.15.0/bin/yarn
npm: 6.10.1 - ~/.nvm/versions/node/v10.15.0/bin/npm
Browsers:
Chrome: 75.0.3770.142
Firefox: 67.0.4
Safari: 12.1.1
npmPackages:
@vue/babel-helper-vue-jsx-merge-props: 1.0.0
@vue/babel-plugin-transform-vue-jsx: 1.0.0
@vue/babel-preset-app: 3.9.2
@vue/babel-preset-jsx: 1.0.0
@vue/babel-sugar-functional-vue: 1.0.0
@vue/babel-sugar-inject-h: 1.0.0
@vue/babel-sugar-v-model: 1.0.0
@vue/babel-sugar-v-on: 1.0.0
@vue/cli-overlay: 3.9.0
@vue/cli-plugin-babel: ^3.9.2 => 3.9.2
@vue/cli-plugin-e2e-nightwatch: ^3.9.2 => 3.9.2
@vue/cli-plugin-eslint: ^3.9.2 => 3.9.2
@vue/cli-plugin-unit-jest: ^3.9.0 => 3.9.0
@vue/cli-service: ^3.9.3 => 3.9.3
@vue/cli-shared-utils: 3.9.0
@vue/component-compiler-utils: 2.6.0 (3.0.0)
@vue/eslint-config-standard: ^4.0.0 => 4.0.0
@vue/preload-webpack-plugin: 1.1.0
@vue/test-utils: ^1.0.0-beta.29 => 1.0.0-beta.29
@vue/web-component-wrapper: 1.2.0
eslint-plugin-vue: ^5.2.3 => 5.2.3 (4.7.1)
jest-serializer-vue: 2.0.2
vue: ^2.6.10 => 2.6.10
vue-eslint-parser: 5.0.0 (2.0.3)
vue-hot-reload-api: 2.3.3
vue-jest: 3.0.4
vue-loader: 15.7.1
vue-router: ^3.0.3 => 3.0.7
vue-style-loader: 4.1.2
vue-template-compiler: ^2.6.10 => 2.6.10
vue-template-es2015-compiler: 1.9.1
vuex: ^3.0.1 => 3.1.1
npmGlobalPackages:
@vue/cli: Not Found
Steps to reproduce
This isnt reproducable by anyone else, but I have upgraded all packages and my chrome binary and its still happening
What is expected?
selenium launches chrome and runs e2e tests
What is actually happening?
selenium launches chrome and immediately exits
Error retrieving a new session from the selenium server
Connection refused! Is selenium server started?
{ value:
{ message:
'session not created\nfrom disconnected: unable to connect to renderer\n (Session info: chrome=75.0.3770.142)\n (Driver info: chromedriver=2.46.
628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS X 10.14.5 x86_64) (WARNING: The server did not provide any stacktrace information)\nCo
mmand duration or timeout: 868 milliseconds\nBuild info: version: \'3.141.59\', revision: \'e82be7d358\', time: \'2018-11-14T08:25:53\'\nSystem info: ho
st: \'l.local\', ip: \'fe80:0:0:0:1c33:be36:3840:8a33%en0\', os.name: \'Mac OS X\', os.arch: \'x86_64\', os.version: \'10.14.5\', java.version: \'12.0.1
\'\nDriver info: driver.version: unknown',
error: 'session not created' },
status: 33 }
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Selenium & ChromeDriver: session not created, unable to ...
I am trying to run automated tests via Webdriver.io, Selenium and ChromeDriver on Mac. I am using the latest versions of all involved...
Read more >Chromedriver session Error.Session not created:Chrome ...
Best coding solution for query Chromedriver session Error.Session not created:Chrome version must be>= 60.0.3112.0(chromedriver=2.33.506092,platform=Linux ...
Read more >WebDriver - W3C
WebDriver is a remote control interface that enables introspection and control of user agents. It provides a platform- and language-neutral ...
Read more >Setting up your own test automation environment
We will cover writing and running Selenium tests using Node.js, as it is quick and easy to get started, and a more familiar...
Read more >Getting Started | Nightwatch.js
Selenium Server is a Java application which Nightwatch uses to connect to the ... GeckoDriver is not yet feature complete, which means it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So I got this working by installing chromedriver 76 as a dev dependency and then specifying it in my nightwatch config:
So am I reading this correctly, if you have chrome 76 installed you need to upgrade vue cli to
v4.0.0-beta.0…
to run e2e tests? Can I upgrade chromedriver separately? It doesn’t seem to have an effect.