Tests failing due to dependency issues in npm3 #14
Description
Hey there! I've been using httpbackend at work with my automated protractor tests, and I've been very pleased with it, but we've started having problems recently as a result of dependency issues. After sorting through which dependency caused the issue, I was able to create a reduced test case that demonstrated the problem, here are the steps to reproduce:
OS: Windows 7 (although this may happen on Mac OS X too, I haven't tested)
Node Version: 4.2.2
NPM Version: 3.3.12
- Go to https://angularjs.org/ and create the 2 files described in the tutorial.
- In the project directory, run
npm install http-backend protractor - Run the tests using the version of protractor that was installed, like so:
./node_modules/.bin/protractor ./config.js - You should see the following error message, followed by a stack trace that lads to
\node_modules\selenium-webdriver\lib\webdriver\promise.js:112:9:
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver
Started
F
Failures:
1) angularjs homepage todo list should add a todo
Message:
Failed: Unimplemented function: "then"
I think this may have to do with some of the dependencies that your project is relying on, which seem to include an old version of protractor.
I'm also getting errors when performing installs with npm3, which indicate that grunt-connect relies on grunt as a peerDependency. Looking through your package.json, it looks like you may be able to move the grunt and mocha related dependencies into devDependencies and make the most recent version of protractor into a peerDependency.
If you'd like, I can do this myself and submit a Pull Request.
Thanks for all the hard work!
-Chris