Tuesday 30 May 2017

The path to the driver executable must be set by the webdriver.chrome.driver system property

Environment

  • Windows 10
  • Node v6.10.3
  • Npm v3.10.10
  • Protractor v5.1.2

Issue

I am running into the error below when running protractor. This must be very basic issue since I am following the tutorial documentation on the official website. http://www.protractortest.org/#/tutorial.

Executing the command protractor conf.js results in the following error.

[13:58:14] I/launcher - Running 1 instances of WebDriver [13:58:14] I/hosted - Using the selenium server at localhost:4444/wd/hub [13:58:14] E/launcher - The path to the driver executable must be set by the webdriver.chrome.driver system property; for more information, see github.com/SeleniumHQ/selenium/wiki/ChromeDriver. The latest version can be downloaded from chromedriver.storage.googleapis.com/index.html [13:58:14] E/launcher - WebDriverError: The path to the driver executable must be set by the webdriver.chrome.driver system property; for more information, see github.com/SeleniumHQ/selenium/wiki/ChromeDriver. The latest version can be downloaded from chromedriver.storage.googleapis.com/index.html at WebDriverError (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:27:5) at Object.checkLegacyResponse (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:505:15) at parseHttpResponse (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13) at doSend.then.response (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:440:13) at process._tickCallback (internal/process/next_tick.js:109:7) From: Task: WebDriver.createSession() at Function.createSession (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:777:24) at Function.createSession (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\chrome.js:709:29) at createDriver (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:167:33) at Builder.build (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:623:16) at Hosted.getNewDriver (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\lib\driverProviders\driverProvider.ts:60:29) at Runner.createBrowser (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\lib\runner.ts:225:39) at q.then.then (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\lib\runner.ts:391:27) at _fulfilled (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54) at self.promiseDispatch.done (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30) at Promise.promise.promiseDispatch (C:\Users\randy.dinh\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13) [13:58:14] E/launcher - Process exited with error code 199

My configuration file looks like this.

exports.config = {
seleniumAddress: 'http://localhost:4444/wd/hub',
specs: ['todo-spec.js'],
capabilities: {'browserName': 'chrome'},
directConnect: false,
chromeDriver: 'C:\Users\user_name\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_2.29.exe'
};



via Thunder_Cat_

No comments:

Post a Comment