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

testling-bl2

v1.7.4

Published

write tests for browser code. bcmd, x option modified for browser-launcher2. Modification of original testling by @substack

Downloads

2

Readme

testling

Run testling-ci tests locally.

example

write a test:

var test = require('tape');

test('beep boop', function (t) {
    t.plan(2);
    t.equal(1+1, 2);
    t.ok(true);
});

run your test in a local headless browser:

$ browserify example/test.js | testling

TAP version 13
# beep boop
ok 1 should be equal
ok 2 (unnamed assert)

1..2
# tests 2
# pass  2

# ok

with an exit code of 0 for successes and non-zero for failures like a good unix citizen

Once you have a package.json with a configured "testling" field, you can just type:

$ testling

to run all your tests locally just like they will be run on testling-ci. This includes mocha harnesses, scripts, and files parameters.

usage

usage: testling {DIRECTORY|-} {OPTIONS}

If there (is no DIRECTORY and stdin is a tty) or the DIRECTORY is "-",
javascript will be read from stdin and executed.

Otherwise, DIRECTORY (or the $CWD) will be checked for a package.json with a
testling field.

OPTIONS are:

     --html  Instead of launching a server, show the generated html.

  --no-show  Don't render the console.log() output to the document body.

         -u  Instead of launching a browser, print the url to visit so you can
             open the browser yourself.

         -x  Launch a browser available in your system ($PATH is not required).
             Choose between firefox, chrome, safari, ie, phantomjs, opera

testling field

Read more about how the package.json "testling" field works.

code coverage

To compute code coverage, just use the coverify transform with -t coverify when you run browserify.

coverify writes coverage data with console.log(), so you can pipe the output of testling through to the coverify command to parse the results and give human-readable output:

$ browserify -t coverify test.js | testling | coverify

TAP version 13
# beep boop
ok 1 should be equal

1..1
# tests 1
# pass  1

# ok

# /home/substack/projects/coverify/example/test.js: line 7, column 16-28

  if (err) deadCode();
           ^^^^^^^^^^^

# /home/substack/projects/coverify/example/foo.js: line 3, column 35-48

  if (i++ === 10 || (false && neverFires())) {
                              ^^^^^^^^^^^^

The exit code of coverify is non-zero when there are unreachable expressions.

install

First, install browserify globally so that the testling command can find it when there is no browserify in ./node_modules/.bin:

npm install -g browserify

then do:

npm install -g testling

license

MIT

attack of the testlings!