Learn How To Test Across Browsers

For Cross Browser Testing, Screener integrates with Sauce Labs to provide access to additional browsers.

By default, Screener runs tests against the Chrome browser, which does not require a Sauce account. Screener provides Chrome browsers and device emulation out-of-the-box.

Important Notes
  • Cross Browser Testing with Sauce Labs will be slower than regular Screener visual regression tests, and so it is not recommended to run on every commit.
  • You may want to limit cross browser testing to certain scenarios, such as only when merging into master (see example below).
  • Requirements: A valid Sauce Labs account, and access to enough concurrency in your Sauce account to run Screener tests. Each browser/resolution combination will use minimum one concurrent machine.
  • Screener's auto-parallelization for Cross Browser Testing will be reduced based on the number of concurrent browsers available in your Sauce account.

  1. Adding Browsers
  2. Supported Browsers

Adding Browsers

To test against multiple browsers, add the browsers and sauce options to your screener.config.js file. Browsers added must match one of the supported browsers/versions in the table below.

Here is a CircleCI example that only runs cross browser tests when committing into master branch:

var config = {
  // regular screener config
// only run cross browser tests when merging into 'master' branch
if (process.env.CIRCLE_BRANCH === 'master') {
  config.browsers = [
      browserName: 'chrome'
      browserName: 'internet explorer',
      version: '11.103'
  config.sauce = {
    username: 'sauce_user',
    accessKey: 'sauce_access_key',
    maxConcurrent: 10
module.exports = config;

Supported Browsers

chrome-do not set-
internet explorer11.103

Got Questions? Ask Us