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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@kano/web-tester

v1.0.0-alpha.20

Published

Runs front-end mocha tests using puppeteer

Downloads

17

Readme

Web Tester

Runs front-end mocha tests using puppeteer

Installation

The web tester should always be installed as a local dependency, and the binary using npm scripts.

This ensures that the required tools are a dependency of your project

Install with:

yarn add --dev @kano/web-tester

Usage

Place your test files in a directory e.g. test. web-tester wil look for all .js files in a given directory.

Run your tests with either:

# run tests with puppeteer and print the results to the console
web-tester run **/*test.js

# Serve a web page that runs the tests
web-tester serve **/*test.js

# Generate a coverage report
web-tester cover **/*test.js

You can create a .web-tester.conf.json to configure both mocha and puppeteer:

{
    "mocha": {
        "ui": "tdd"
    },
    "puppeteer": {
        "slowMo": 1000
    }
}

In your package.json add a test script as follow to automate your tests

{
    "scripts": {
        "test-ci": "web-tester run ./test -r xunit > test-results.xml"
    }
}

Options

|Command|Options| |---|---| |serve|--port: Specifiy which port to use. Default: 8000| |run|--no-headless: Run puppeteer in no-headless mode. Displays the browser. Default: false| | |--reporter, -r: Sepecify which reporter to use, spec or xunit. Default: spec| |cover|--no-headless: Run puppeteer in no-headless mode. Displays the browser. Default: false| | |--reporter, -r: Specify which reporter to use. All istanbul reporters are available. An additional markdown reporter is available to generate a markdown summary table. You can add multiple reports. Default: text-summary|

Helpers

The default assertion library is assert from chai. You can access it with:

import { assert } from '@kano/web-tester/helpers.js';

assert.equal(2, 2);

The fixture helper allows you to prepare HTML Templates, access their elements directly and takes care of adding/removing them from the DOM automatically:

import { fixture } from '@kano/web-tester/helpers.js';

const basic = fixture`
    <my-el></my-el>
`;

suite('my-el', () => {
    test('constructor', () => {
        // Returns the first element in the fixture.
        // These will be removed at the end of the test
        const el1 = basic();
        const el2 = basic();
    });
});