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 🙏

© 2026 – Pkg Stats / Ryan Hefner

selenium-mocha

v0.0.2

Published

run selenium tests in the browser

Readme

selenium-mocha

run selenium tests in the browser using generators and mocha

Build Status Dependency Status NPM version

Installation

npm install selenium-mocha

Usage

For full example see "test" folder. A fresh browser is automatically created and disposed of for each test case. Each test case runs in parallel by default (unless you use --grep which forces it into serial operation).

'use strict';

var assert = require('assert');
var chromedriver = require('chromedriver');
var browser = require('selenium-mocha');

chromedriver.start();
browser.remote('http://localhost:9515/').timeout('60s').operationTimeout('5s');
after(function () {
  chromedriver.stop();
});

describe('www.example.com', function () {
  it('Has a header that reads "Example Domain"', browser(function* (browser) {
    yield browser.get('http://www.example.com');
    var heading = yield browser.elementByTagName('h1').text();
    assert(heading.trim() == 'Example Domain');
  }));
});

Initialization. Configure the following settings:

//configure how to connect to the remote using the same arguments as `wd.remote`
browser.remote(...args);

//set a timeout for all browser test cases
browser.timeout('60s');

//set a timeout that gets reset once each `yield` statement completes
browser.operationTimeout('5s');

//optionaly force all tests to evaluate in sequence (this is typically much slower)
browser.lazy();

You can also pass any of those as options.

Enabling generators

To enable generators, install gnode via npm install gnode --save-dev then enable them by creating a mocha.otps file in the unit tests folder with the following body:

--require gnode

This will precompile files using facebook's regenerator.

License

MIT