test:e2e fails on mac

[JeremyMarshall]

test:e2e fails on mac as its looking for chromedriver.exe

Running "protractor:chrome" (protractor) task
Using ChromeDriver directly...
[launcher] Error: Could not find chromedriver at /Users/xxxxx/src/node/test/node_modules/grunt-protractor-runner/node_modules/protractor/selenium/chromedriver.exe
>>
Fatal error: protractor exited with code: 1


Execution Time (2014-08-14 21:02:44 UTC)
injector:sass        102ms  ▇▇ 4%
concurrent:test       1.8s  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 65%
injector:css          95ms  ▇▇ 3%
bowerInstall:target  157ms  ▇▇▇ 6%
autoprefixer:dist    240ms  ▇▇▇▇▇ 9%
express:dev          190ms  ▇▇▇▇ 7%
protractor:chrome    160ms  ▇▇▇ 6%
Total 2.8s

This is the same regardless of if I run

webdriver-manager start

I only have Chrome and Safari on my mac for the moment

[JeremyMarshall]

I fixed this by running

node node_modules/grunt-protractor-runner/node_modules/protractor/bin/webdriver-manager update

which is an alias in the package.json

  "scripts": {
    "start": "node server/app.js",
    "test": "grunt test",
    "update-webdriver": "node node_modules/grunt-protractor-runner/node_modules/protractor/bin/webdriver-manager update"
  }

but doing npm update-webdriver directly fails

Jeremys-MacBook-Pro:test jeremymarshall$ npm update-webdriver

Usage: npm <command>

where <command> is one of:
    add-user, adduser, apihelp, author, bin, bugs, c, cache,
    completion, config, ddp, dedupe, deprecate, docs, edit,
    explore, faq, find, find-dupes, get, help, help-search,
    home, i, info, init, install, isntall, issues, la, link,
    list, ll, ln, login, ls, outdated, owner, pack, prefix,
    prune, publish, r, rb, rebuild, remove, repo, restart, rm,
    root, run-script, s, se, search, set, show, shrinkwrap,
    star, stars, start, stop, submodule, t, tag, test, tst, un,
    uninstall, unlink, unpublish, unstar, up, update, v,
    version, view, whoami

npm <cmd> -h     quick help on <cmd>
npm -l           display full usage info
npm faq          commonly asked questions
npm help <term>  search for help on <term>
npm help npm     involved overview

Specify configs in the ini-formatted file:
    /Users/jeremymarshall/.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config

[email protected] /usr/local/lib/node_modules/npm

Version

Jeremys-MacBook-Pro:test jeremymarshall$ npm version
{ http_parser: '1.0',
  node: '0.10.30',
  v8: '3.14.5.9',
  ares: '1.9.0-DEV',
  uv: '0.10.28',
  zlib: '1.2.3',
  modules: '11',
  openssl: '1.0.1h',
  npm: '1.4.23',
  test: '0.0.0' }

[DaftMonk]

You need to do npm run update-webdriver

[Kageetai]

I had to do the same on Windows. Is that ´update-webdriver´ not run when initial generating?

[riddla]

Had the same problem on OS X today. npm run update-webdriver should really be integrated in the setup process. Is this possible?

[noahbuscher]

+1 for integrating it into the setup process