npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

sauce-tap-runner

v0.1.2

Published

Automate running TAP browser unit tests on Sauce Labs

Downloads

45

Readme

sauce-tap-runner

NPM

Run TAP unit tests in the browser using Sauce Labs hosted browsers. This helper takes care of setting up the tunnel to Sauce Labs servers and provides the test page and TAP parsing. It will also set the test result status on Sauce Labs so that you can use the awesome status images. (Note that you must also set the build field on the desired capabilities object for the images to work.)

Example

var Runner = require('sauce-tap-runner'),
    browserify = require('browserify'),
    async = require('async');

var tests = new Runner(sauceUser, sauceKey),
    // Browserify is not required, can use either a string or stream of JS code
    src = browserify().add('tests.js').bundle();

async.series([run('chrome'), run('firefox')], closeTests);

function run(browser) {
    // Return a function that when called will run tests in the specified
    // browser

    return function(callback) {
        tests.run(src, { browserName: browser }, function(err, results) {
            if (err) {
                return callback(err);
            }

            console.log(results);
            callback();
        });
    };
}

function closeTests(err) {
    if (err) {
        console.error(err);
    } else {
        console.log('Tests completed');
    }

    tests.close(function() {
        // Runner is closed
    });
}

Reference

new Runner(sauceUser, sauceKey)

Creates a new test runner. A single test runner maintains a single Sauce Connect tunnel. Using a single runner for all your tests will improve speed as it takes time to setup the tunnel. A tunnel will only be created when you run the tests.

sauceUser and sauceKey must be your Sauce Labs username and key.

#run(src, desiredCapabilities, [options], [callback])

Runs the tests in a new browser. It will create a new WebDriver connection to the browser and run the JS tests provided. It is not able to run tests in parallel; you must wait till one test is completed before running the next.

src can be a string or stream containing the JS code for the tests. The tests should output TAP-compatible results to the browser console using console.log.

desiredCapabilities is an object that will be passed to the Sauce Labs server when creating the browser. See the docs for information on what options you can provide. The username and password is automatically set.

options is an optional object containing the options for the test runner. See the wd-tap-runner docs for valid options.

callback is an optional function that will be called with the error if any occurred and the test results. Note that failed tests are not considered errors; they will be reported in the results. The results are the same as for wd-tap-runner.

#close([callback])

Closes the Sauce Connect tunnel. Will call callback when everything is closed. All tests must be finished before closing.

Events

Runner inherits from EventEmitter. It will emit the following events:

  • tunnel-connect: Starting to connect the Sauce Connect tunnel
  • tunnel(tunnel): The Sauce Connect tunnel has been connected
  • tunnel-error(err): An error occurred when connecting the Sauce Connect tunnel
  • browser(browser): Successfully connected to a new browser
  • results(results): A test run has finished
  • close: The runner has been closed