Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps(selenium-webdriver): upgrade to 3.0.0 #63

Merged
merged 5 commits into from Nov 8, 2016

Conversation

cnishina
Copy link
Member

@cnishina cnishina commented Nov 7, 2016

No description provided.

@heathkit
Copy link
Contributor

heathkit commented Nov 7, 2016

Looks like selenium-webdriver uses rest parameters, which are only in Node > 6. Their package.json also shows that they require Node 6.9.0 or greater.

- use promise object's isPending `deferred.promise.isPending`
- `deferred.isPending` has been deprecated as of selenium-webdriver 3.0.0
- see SeleniumHQ/selenium@e5d67a7#diff-08a6a8d91f29fca8cebfc8671e4ffc3d
- selenium-webdriver 3.0.0 requires node >= 6.9.0
@cnishina
Copy link
Member Author

cnishina commented Nov 7, 2016

Adding requirements for node >= 6.9.0 per selenium-webdriver 3.0.0.

- isPending exists in lib/promise but it is not exported
- the return object was a ManagedPromise and isPending is not a class method
- wrote my own isPending similar to selenium-webdriver in common.js
@cnishina cnishina merged commit 5fe36a6 into angular:beta Nov 8, 2016
cnishina added a commit to cnishina/jasminewd that referenced this pull request Jan 6, 2017
fix test "should wait till the expect to run the flow"

- `isPending` exists but it is no longer part of `ManagedPromise`
- `isPending` also is no longer exported in `lib/promise.js`
- wrote an `isPending` similar to selenium-webdriver in common.js

require a minimum node version

- selenium-webdriver 3.0.0 requires node >= 6.9.0
- update travis test to use node 6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants