As you all know, the Selenium team moves crazy fast and we do our best to keep up. 
This time, we have the pleasure to announce we now support Selenium 2.18.0! This releases is packed with bug fixes and improvements. Here’s the changelog for more information.
Along with the Selenium upgrade, we included upgrades to out browsers. That includes Firefox 10.0, Chrome 16.0.912.77 and Opera 11 for both Selenium 1 and Selenium 2 users. To use these browsers, make sure you specify 2.18.0 as the Selenium version to use, as our current default (2.6.0) won’t support them.
You can start using this new versions right now by adding the following Desired Capabilities/JSON key-value:
"selenium-version": "2.18.0"
During the next few weeks we’ll testing and considering moving our default version to this version. If you see any issues after moving your tests to it, we definitely want to hear about it.
For more information about the current Selenium version that is used by Sauce, how to use other Selenium versions, and the selenium-version flag, have a look at our docs in the Sauce OnDemand additional configuration section.
Related posts:
Announcing Selenium 2.6.0, Firefox 6 and 7 support
Announcing Support For Selenium 2.16.1, ChromeDriver 18.0.995.0 and Firefox 8 and 9
Announcing Selenium 2.7.0 support
Announcing Selenium 2.8.0 support
Announcing support for Selenium 2.2.0 and 2.3.0
I know this post is about 2.18.0, but when I was updating my tests to use 2.18.0, I noticed in your ‘additional configuration’ section that 2.19.0 was a supported version so I figured I’d try that out.
Using 2.19.0, I was unable to access any sites via https over Sauce Connect. I also tried the -Dhttps configuration for launching Sauce Connect as specified in the docs, but that didn’t help either. IE browsers were refusing to display the page. FF was asking for confirmation of a security exception, as the certificate wasn’t trusted. Manual tests were not showing any problems with the certs in any browsers.
I wasn’t seeing the issue in Scout, and specifying 2.18.0 in my Desired Capabilities seems to have made the issue go away. Do y’all have any idea why that might be happening?
Looks like it’s a problem with Selenium 2.19.0: http://code.google.com/p/selenium/issues/detail?id=3373
Hi Daniel,
This is indeed an issue in 2.19.0. We’re planning to make 2.20.0 available soon. Sorry for the inconvenience.
Hi while running this code — I am getting error [0330/112545:ERROR:automation_proxy.cc(387)] Channel error in AutomationProxy.
service = new ChromeDriverService.Builder()
.usingChromeDriverExecutable(new File(“C:UsersSumit.S.Saxenachromedriver.exe”))
.usingAnyFreePort()
.build();
try
{
service.start();
} catch(Exception e){ e.printStackTrace();}
driver = new RemoteWebDriver(service.getUrl(),
DesiredCapabilities.chrome());