Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Tests on chrome doesn't work when an instance is already open #1636

Closed
ghost opened this issue Dec 14, 2014 · 3 comments
Closed

Tests on chrome doesn't work when an instance is already open #1636

ghost opened this issue Dec 14, 2014 · 3 comments

Comments

@ghost
Copy link

ghost commented Dec 14, 2014

I'm testing protractor features and when I have an instance of chrome open, for example, I'm searching something on google and working with protractor tests and I wanna run the tests on chrome the google chrome opens a new tab with "data:," on address bar and the tests doesn't work. follow the log:

[chrome #2] PID: 6868
[chrome #2] Specs: C:...\default_spec.js
[chrome #2]
[chrome #2] Using the selenium server at http://localhost:4444/wd/hub
[chrome #2] ERROR - Unable to start a WebDriver session.
[chrome #2]
[chrome #2] C:...\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\error.js:113
[chrome #2] var template = new Error(this.message);
[chrome #2] ^

@hankduan
Copy link
Contributor

@kaahxd The error shouldn't have anything to do with the fact that you have another instance of chrome open already (try with chrome closed and see if it works). Anyway, make sure your selenium server is set up correctly (i.e. does http://localhost:4444/wd/hub resolve for you?).

Please refer to http://angular.github.io/protractor/#/tutorial for help.

@juliemr
Copy link
Member

juliemr commented Dec 16, 2014

Agreed, this looks like an issue with your selenium server. Also try running with the --troubleshoot flag to get more information.

@juliemr
Copy link
Member

juliemr commented Jan 6, 2015

Haven't heard anything in several weeks, closing as obsolete.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants