Bump webdriver-manager to v12 #4033
Milestone
Comments
|
See #4042 |
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 31, 2017
Running `webdriver-manager update` will now by default grab the latest versions of all binaries (standalone, chromedriver, iedriver, gecko driver). You can continue to pin to a specific versions using the command line option. Example `webdriver-manager update --versions.chrome 2.20`. As of this release the latest versions are: - gecko v0.14.0 - selenium-standalone 3.0.1; however, 3.0.0-beta4 appears to work for Firefox - chromedriver 2.27 - iedriver 3.0.0 closes angular#4033
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 31, 2017
Running `webdriver-manager update` will now by default grab the latest versions of all binaries (standalone, chromedriver, iedriver, gecko driver). You can continue to pin to a specific versions using the command line option. Example `webdriver-manager update --versions.chrome 2.20`. As of this release the latest versions are: - gecko v0.14.0 - selenium-standalone 3.0.1; however, 3.0.0-beta4 appears to work for Firefox - chromedriver 2.27 - iedriver 3.0.0 closes angular#4033
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 31, 2017
Running `webdriver-manager update` will now by default grab the latest versions of all binaries (standalone, chromedriver, iedriver, gecko driver). You can continue to pin to a specific versions using the command line option. Example `webdriver-manager update --versions.chrome 2.20`. As of this release the latest versions are: - gecko v0.14.0 - selenium-standalone 3.0.1 is the latest jar file; however, 3.0.0-beta4 appears to work for Firefox - chromedriver 2.27 - iedriver 3.0.0 closes angular#4033
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 31, 2017
Running `webdriver-manager update` will now by default grab the latest versions of all binaries (standalone, chromedriver, iedriver, gecko driver). You can continue to pin to a specific versions using the command line option. Example `webdriver-manager update --versions.chrome 2.20`. As of this release the latest versions are: - gecko v0.14.0 - selenium-standalone 3.0.1 is the latest jar file; however, we recommend 3.0.0-beta4. See note below on Firefox support. - chromedriver 2.27 - iedriver 3.0.0 A note on FireFox support: Selenium standalone 3.0.1 has a bug which prevents it from working with any version of FireFox. We have tested version 3.0.0-beta4 and know that it works with FireFox 51, and we expect that the 3.0.2 release will also work. closes angular#4033
igniteram
pushed a commit
to igniteram/protractor
that referenced
this issue
Feb 21, 2017
Running `webdriver-manager update` will now by default grab the latest versions of all binaries (standalone, chromedriver, iedriver, gecko driver). You can continue to pin to a specific versions using the command line option. Example `webdriver-manager update --versions.chrome 2.20`. As of this release the latest versions are: - gecko v0.14.0 - selenium-standalone 3.0.1 is the latest jar file; however, we recommend 3.0.0-beta4. See note below on Firefox support. - chromedriver 2.27 - iedriver 3.0.0 A note on FireFox support: Selenium standalone 3.0.1 has a bug which prevents it from working with any version of FireFox. We have tested version 3.0.0-beta4 and know that it works with FireFox 51, and we expect that the 3.0.2 release will also work. closes angular#4033
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This will get us on to selenium standalone @3 and later versions of chromedriver and friends, which should keep code more up to date with recent browsers. It'll also allow the latest firefox to work with direct connect again!
Note that if you are testing with old firefox 47, you'll need to pin to an older version of selenium standalone, 2.53.
The text was updated successfully, but these errors were encountered: