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

chore(release): update selenium-webdriverjs and bump version number #4538

Merged
merged 1 commit into from
Oct 13, 2017

Conversation

qiyigg
Copy link
Contributor

@qiyigg qiyigg commented Oct 11, 2017

1.Update selenium-webdriverjs and bump version number
2.Solve compatibility problem: new webdriver has a more strict method when setting script timeout. If no script timeout was specified, set timeout to 0.

package.json Outdated
@@ -23,7 +23,7 @@
"optimist": "~0.6.0",
"q": "1.4.1",
"saucelabs": "~1.3.0",
"selenium-webdriver": "3.0.1",
"selenium-webdriver": "3.5.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @vikerman @qiyigg

Don't we want to go to 3.6.0 that's released a few weeks ago?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It there any new features in 3.6.0 that you rely on?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was trying to search for the post of Simon Stewart but I couldn't find it. He said they didn't update the changelog (https://github.com/SeleniumHQ/selenium/blob/selenium-3.6.0/javascript/node/selenium-webdriver/CHANGES.md#vnext) but it was wise to update to 3.6.0 (on of the last versions before they are going to release version 4.0)

So if it's not to much effort I would advice to go to version 3.6.0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I will try it right now. If it is easy to upgrade to 3.6, I will upgrade protractor to 3.6 directly; otherwise, I 'll do it in a separate PR later on.

1.Update selenium-webdriverjs and bump version number
2.Solve compatibility problem: new webdriver has a more strict method
when setting script timeout. If no script timeout was specified, set timeout to 0.
@vikerman vikerman merged commit 0fbc2c0 into angular:master Oct 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants