The Default Chrome Version on Sauce Labs is Changing

[Justin Raczak]

Hello! We're writing to give you a heads up about a change to specifying Chrome versions on Sauce Labs that will take effect on Monday, March 9th. 
 What's changing? 
 Today, to specify the latest version of Chrome on Sauce Labs you must explicitly declare the version number in your capabilities. Beginning Monday, March 9th, the method for specifying the latest version of Chrome will be the same as it is for all other browsers. Rather than specifying an explicit version number, you can test against the latest version of Chrome by excluding the version capability or by setting the value to an empty string, like so: 
 caps.setCapability("version", ""); 
 We recommend testing against the latest version of Chrome (40) before Monday, March 9th, to ensure the switch will not break any of your existing tests. 
 Why the change? 
 Last year, Chrome versions later than 35 presented issues with Chromedriver 2. To avoid these issues, we locked the default version of Chrome to version 35. The issues with Chromedriver have been resolved so we are bringing the Chrome version specification into parity with all other browsers. 
 If you have any questions or concerns, please drop us a note at help at saucelabs.com.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-gui/attachments/20150306/d58c95e1/attachment.html>