Wrapper around the Sauce Labs REST APIs for Node.js (v8 or higher).

To install the package run:

npm install saucelabs

Your Sauce Labs username.

Type: string
Default: process.env.SAUCE_USERNAME

Your Sauce Labs access key.

Type: string
Default: process.env.SAUCE_ACCESS_KEY

Your Sauce Labs datacenter region. The following regions are available:

• us-west-1 (short us)
• eu-central-1 (short eu)

Type: string
Default: us

If set to true you are accessing the headless Sauce instances (this discards the region option).

Type: boolean
Default: false

All accessible API commands with descriptions can be found here. In order to route requests through a proxy set HTTP_PROXY, HTTPS_PROXY or NO_PROXY as environment variable. For more information on this, read here. Alternatively you can pass the proxy to be used during initialization:

import SauceLabs from 'saucelabs'; ... const myAccount = new SauceLabs({ proxy: 'http://localproxy.com' });

This package if installed globally can be used as CLI tool to access the API from the command line:

$ npm install -g saucelabs ... $ sl listJobs $SAUCE_USERNAME --limit 5 --region eu { jobs: [ { id: '19dab74f8fd848518f8d2c2cee3a6fbd' }, { id: 'dc08ca0c7fa14eee909a093d11567328' }, { id: '5bc6f70c777b4ae3bf7909a40f5ee41b' }, { id: 'f40fe7b044754eaaa5f5a130406549b5' }, { id: 'd1553f71f910402893f1e82a4dcb6ca6' } ] }

You can find all available commands and options with description by calling:

sl --help # show description for specific command sl listJobs --help

or update the job status by calling:

sl updateJob cb-onboarding 690c5877710c422d8be4c622b40c747f "{\"passed\":false}"

The following example shows how to access details of the last job you were running with your account that is being exposed as environment variables as SAUCE_USERNAME and SAUCE_ACCESS_KEY. Alternatively you can pass the credentials via options to the constructor:

import SauceLabs from 'saucelabs'; // if imports are not supported by your Node.js version, import the package as follows: // const SauceLabs = require('saucelabs').default; (async () => { const myAccount = new SauceLabs(); // using constructor options // const myAccount = new SauceLabs({ user: "YOUR-USER", key: "YOUR-ACCESS-KEY"}); // get job details of last run job const job = await myAccount.listJobs( process.env.SAUCE_USERNAME, { limit: 1, full: true } ); console.log(job); /**  * outputs:  * { jobs:  [ { browser_short_version: '72',  video_url:  'https://assets.saucelabs.com/jobs/dc08ca0c7fa14eee909a093d11567328/video.flv',  creation_time: 1551711453,  'custom-data': null,  browser_version: '72.0.3626.81',  owner: '<username-redacted>',  id: 'dc08ca0c7fa14eee909a093d11567328',  record_screenshots: true,  record_video: true,  build: null,  passed: null,  public: 'team',  end_time: 1551711471,  status: 'complete',  log_url:  'https://assets.saucelabs.com/jobs/dc08ca0c7fa14eee909a093d11567328/selenium-server.log',  start_time: 1551711454,  proxied: false,  modification_time: 1551711471,  tags: [],  name: null,  commands_not_successful: 1,  consolidated_status: 'complete',  manual: false,  assigned_tunnel_id: null,  error: null,  os: 'Windows 2008',  breakpointed: null,  browser: 'googlechrome' } ] }  */ })()

You may wonder why listJobs requires a username as first parameter since you've already defined the process.env. The reason for this is that Sauce Labs supports a concept of Team Accounts, so-called sub-accounts, grouped together. As such functions like the mentioned could list jobs not only for the requesting account, but also for the individual team account. Learn more about it here

Public APIs have changed from v1 to v2. Methods in v1 accepted a callback trailing parameter which is no more available with v2, instead all methods now return a Promise which can be awaited or then'd.

Below, you can find the list of the mapped method names:

To run the test suite, first invoke the following command within the repo, installing the development dependencies:

npm install

Then run the tests:

npm test

This module was originally created by Dan Jenkins with the help of multiple contributors (Daniel Perez Alvarez, Mathieu Sabourin, Michael J Feher, and many more). We would like to thank Dan and all contributors for their support and this beautiful module.