karma-sauce-launcher

Run your unit tests on Sauce Labs' browser cloud!

Installation

Install karma-sauce-launcher as a devDependency in your package.json:

1npm install karma-sauce-launcher --save-dev

Usage

This launcher is typically used in CI to run your unit tests across many browsers and platforms on Sauce Labs. However, you can also use it locally to debug tests in browsers not available on your machine. It is expected that you are already familiar with Karma when configuring this launcher, so if you are new to Karma, head over to the Karma website.

Adding karma-sauce-launcher to an existing Karma config

To configure this launcher, you need to add two properties to your top-level Karma config, sauceLabs and customLaunchers, set the browsers array to use Sauce Labs browsers, and add the sauceLabs reporter.

The sauceLabs object defines global properties for each browser/platform while the customLaunchers object configures individual browsers. The sauceLabs reporter allows your tests results to be properly displayed on https://saucelabs.com. Here is a sample Karma config to get the launcher running:

1module.exports = function(config) {
2  // Example set of browsers to run on Sauce Labs
3  // Check out https://saucelabs.com/platforms for all browser/platform combos
4  var customLaunchers = {
5    sl_chrome: {
6      base: 'SauceLabs',
7      browserName: 'chrome',
8      platform: 'Windows 7',
9      version: '35'
10    },
11    sl_firefox: {
12      base: 'SauceLabs',
13      browserName: 'firefox',
14      version: '30'
15    },
16    sl_ios_safari: {
17      base: 'SauceLabs',
18      browserName: 'iphone',
19      platform: 'OS X 10.9',
20      version: '7.1'
21    },
22    sl_ie_11: {
23      base: 'SauceLabs',
24      browserName: 'internet explorer',
25      platform: 'Windows 8.1',
26      version: '11'
27    }
28  }
29
30  config.set({
31
32    // The rest of your karma config is here
33    // ...
34    sauceLabs: {
35        testName: 'Web App Unit Tests'
36    },
37    customLaunchers: customLaunchers,
38    browsers: Object.keys(customLaunchers),
39    reporters: ['dots', 'saucelabs'],
40    singleRun: true
41  })
42}

Note: this config assumes that process.env.SAUCE_USERNAME and process.env.SAUCE_ACCESS_KEY are set.

Example karma-sauce-launcher configs

For example configs using this launcher (using Travis CI), check out this repo's karma file, the karma-sauce-example repo (which demonstrates how to use Sauce locally), or AngularJS' Karma config.

sauceLabs config properties shared across all browsers

username

Type: String Default: process.env.SAUCE_USERNAME

Your Sauce Labs username (if you don't have an account, you can sign up here).

accessKey

Type: String Default: process.env.SAUCE_ACCESS_KEY

Your Sauce Labs access key which you will see on your account page.

proxy

Type: String

Proxy for connecting to Sauce REST API, which is used to communicate job updates of pass/fail.

startConnect

Type: Boolean Default: true

If true, Sauce Connect will be started automatically. Set this to false if you are launching tests locally and want to start Sauce Connect via a binary or the Mac app in the background to improve test speed.

connectOptions

Type: Object Default:

1{
2  username: 'yourUsername',
3  accessKey: 'yourAccessKey',
4  tunnelIdentifier: 'autoGeneratedTunnelID'
5}

Options to send to Sauce Connect. Check here for all available options.

build

Type: String Default: One of the following environment variables: process.env.BUILD_NUMBER process.env.BUILD_TAG process.env.CI_BUILD_NUMBER process.env.CI_BUILD_TAG process.env.TRAVIS_BUILD_NUMBER process.env.CIRCLE_BUILD_NUM process.env.DRONE_BUILD_NUMBER

ID of the build currently running. This should be set by your CI.

testName

Type: String Default: 'Karma test'

Name of the unit test group you are running.

tunnelIdentifier

Type: String

Sauce Connect can proxy multiple sessions, this is an id of a session.

tags

Type: Array of Strings

Tags to use for filtering jobs in your Sauce Labs account.

recordVideo

Type: Boolean Default: false

Set to true if you want to record a video of your Karma session.

recordScreenshots

Type: Boolean Default: true

Set to false if you don't want to record screenshots.

public

Type: String Default: null

Control who can view job details. Available visibility levels are documented on the SauceLabs website.

customData

Type: Object Default: {}

Send arbitrary data alongside your tests. See the SauceLabs documentation for more details.

customLaunchers config properties

The customLaunchers object has browser names as keys and configs as values. Documented below are the different properties which you can configure for each browser/platform combo.

Note: You can learn about the available browser/platform combos on the Sauce Labs platforms page, platforms configurator page and REST API page.

base

Type: String Required: true

This defines the base configuration for the launcher. In this case it should always be SauceLabs so that browsers can use the base Sauce Labs config defined at the root sauceLabs property.

browserName

Type: String Required: true

Name of the browser.

version

Type: String Default: Latest browser version for all browsers except Chrome which defaults to '27'

Version of the browser to use.

platform

Type: String Default: 'Linux' for Firefox/Chrome, 'Windows 7' for IE/Safari

Name of platform to run browser on.

deviceOrientation

Type: String Default: 'portrait'

Accepted values: 'portrait' || 'landscape'

Set this string if your unit tests need to run on a particular mobile device orientation for Android Browser or iOS Safari.

Behind the scenes

This launcher uses Sauce Connect in the background. If you are interested in security or want to see the system requirements, head over to the documentation.