SauceLabs Google Chrome

[ugate]

I noticed that bootstrap is missing the Google Chrome browser from the test cases and wanted to let you know that if you change chrome to googlechrome in sauce_browsers.yml it should start working and show up in the widget in README.md.

[cvrebert]

Hmm, that isn't in Sauce's docs. This name change announced / written-down anywhere?

[cvrebert]

Also, googlechrome is supposedly legacy: axemclion/grunt-saucelabs#28 (comment)

[cvrebert]

Okay, now I'm really confused: axemclion/grunt-saucelabs@800f5bc

[ugate]

I tried it out and googlechrome works while chrome does not.

I'm a little confused myself. I can't find anything in Sauce's docs or Selenium RC/WebDriver docs either. Although, it does look like chrome is the proper name to use for WebDriver and googlechrome for legacy Selenium RC. Sauce's website shows chrome for WebDriver and googlechrome for Selenium RC, but when I step through their code submission the "back end" name shows googlechrome for either selection. Even more perplexing is that their Rest API shows only chrome.

[cvrebert]

Switching to googlechrome indeed makes Chrome show up in the badges again.

[Jonahss]

The browser name confusion is fixed now :)

Sauce automatically chooses whether to use the older Selenium RC or Webdriver based on the browser/OS combination. chrome specifies Google chrome in Webdriver, but Firefox with Selenium RC (by design, because Firefox was originally built on a project called "chrome").

This ambiguous name case now just assumes that when you ask for chrome you wanted Google's chrome, not Firefox.

Note that requesting googlechrome will have all your tests use Selenium RC which is slower and less well supported than Webdriver, so you might want to switch back.

[ugate]

Thanks for the update!