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

testster

v0.0.11

Published

A simple in-browser behavior test driver.

Downloads

6

Readme

testster.js

A simple in-browser behavior test driver. Clicks and such are simulated with javascript rather than a true browser driver that generates the native events (like selenium). While this is a somewhat less realistic testing environment, it is a hell of a lot simpler and more reliable.

Usage:

On each webpage to be tested, initialize testster.js and configure the test files. Assuming you are building your client-side JS with browserify:

require('testster')({
  login: require('./login.test.js'),
  todos: require('./todos.test.js')
});

The *.test.js files are of the following format:

module.exports = {
  'Shows sign in form': function(test) {
    test
      .open('http://localhost:3000/login')
      .waitFor('.login-form')
      .assert.title('Login')
      .assert.text('h2', 'Login')
      .done();
  },
  'User can log in': function(test) {
    test
      .open('http://localhost:3000/login')
      .waitFor('.login-form')
      .type('input[name=username]', 'testuser')
      .type('input[name=password]', 'password')
      .click('button[type=submit]')
      .waitFor('.todos-app')
      .assert.title('Todos')
      .assert.text('h2', 'My Todos')
      .done();
  }
};

Reference the source for a full list of functions and assertions.

Running Tests

Open the javascript console on your webpage. Make sure to check "preserve log" so that the log doesn't clear when navigating between pages.

Run all tests: testster.run()

Run a module: testster.run('login')

Stop the tests: testster.reset()