saucelabs

[gauntface]

See https://github.com/saucelabs-sample-scripts/Node-Selenium/blob/master/selenium-webdriver/selenium-webdriver-simple.js

@addyosmani @philipwalton

Selenium Assistant has been useful for local testing and running tests on Travis CI via download browsers. One of the biggest issues at the moment is lack of windows support and the download times (as well as automated Safari support).

I'm thinking it would be relatively easy to add saucelabs support, would just require changes with some of the method names, some additional methods.

I'm questioning if it's useful or not beyond making it easy to do local vs remote testing.

API Changes

• [x] getBrowser(browserId, release) => getLocalBrowser(browserId, release)
• [x] getAvailableBrowsers() => getLocalBrowsers()
• [x] downloadBrowser() => downloadLocalBrowser()

Addition

• [x] setSaucelabsCredentials()
• [x] getSaucelabsBrowser(browserId, release, options)

Minor Details

• [ ] printAvailableBrowserInfo() - Flag whether saucelabs is supported or not
• [x] killWebDriver() Would need to kill connection with saucelabs etc

[philipwalton]

+1

In my experience the hardest part about webdriver testing is writing the tests and dealing with the flakiness/driver inconsistencies. But If you already have code that runs the tests locally, it's relatively simple to just set the selenium server URL to point to the Sauce Labs cloud.

The one other thing you'll want to remember to do is update the Sauce Labs tests with the results, since that doesn't happen automatically. Here's some code I wrote to do that prior to webdriver.io supporting this in their runner: