#browser-automation #cross-browser-testing ## Documentation entry points ^35b529 - [Docs](https://docs.saucelabs.com/overview/) - [Platform configurator](https://saucelabs.com/platform/platform-configurator) (needed for Selenium/Appium) ^sauce-labs-platform-configurator - [Support Center](https://support.saucelabs.com/hc/en-us) (especially the knowledge base) - [Example projects on GitHub](https://github.com/saucelabs-training) - [JavaScript example projects](https://github.com/saucelabs-training/demo-js) ## Browser version shortcuts For Selenium-based Chrome, Firefox and Edge configurations, it is possible to just specify `latest` as version instead of providing the actual version number. When Sauce Labs introduced that feature, they called it "browser version shortcut" if I recall correctly. Other possible options are relative versions like `latest-1`, `latest-2` as well as `beta` and `dev`. See also the [Test Configuration Options](https://docs.saucelabs.com/dev/test-configuration-options/#browserversion) in the Sauce Labs docs. ## Error messages and mitigations - Long wait times for a new browser session may lead to a „Test did not see a new command for 90 seconds. Timing out.“ error. See [Sauce Labs knowledge base: Queuing Tests on Sauce Labs](https://support.saucelabs.com/hc/en-us/articles/360002048214-Queuing-Tests-on-Sauce-Labs) ## Sauce Testrunner Toolkit [[Sauce Testrunner Toolkit]] ## Sauce To Go A Docker-based local Selenium Grid, which uploads screenshots and video recordings of test runs to Sauce Labs. [Sauce To Go docs](https://opensource.saucelabs.com/sauce-togo/) ## Interesting articles and ideas - [Query Sauce Labs REST API for available browsers and then create WebDriver capabilities out of that](https://github.com/saucelabs/node-saucelabs/issues/111)