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

glunit

v0.1.0

Published

No-nonsense object oriented JavaScript unit testing.

Readme

gltest

No-nonsense object oriented JavaScript unit testing.

This library provides you with simple and unbloated yet powerful test classes. They can easily be extended with domain-specific test functionality.

Usage

Here is a simple example of a test suite:

var suite = new TestSuite("My tests",
    
    new Test("foo() returns bar", function() {
        this.assertEquals("bar", foo());
    });
    
    new Test("bar() does not return foo", function() {
        this.assertNotEquals("foo", bar());
    });
    
});

Available assertions are:

  • assert(booleanishValue)
  • assertEquals(expected, actual)
  • assertNotEquals(notExpected, actual)
  • assertException(callback)
  • assertType(typeStringOrConstructor, object)

The amount of assertions is intentionally kept small. If you need additional assertions for convenience and brevity, or have other common code between tests, you can easily subclass Test with your own extension methods:

function MyTest() {
    Test.apply(this, arguments);
}

extend(Test, MyTest);

MyTest.prototype.prepare = function() {
    this.testObject = new MyObject("foo", true);
};

MyTest.prototype.assertIsHTMLElement = function(element) {
this.assertType(Element, element);
    this.assertEquals("http://www.w3.org/1999/xhtml", element.namespaceURI);
};

Now all tests instantiated as MyTest will have a prepare() method they can invoke to do common set-up, and an assertIsHTMLElement() method to check if an XML node is an HTML element.

It can also be useful to implement a shared test function; for example, this is how a Test subclass is used to test an URI resolving library:

new URITest('http://a/b/c/d;p?q', 'g?y'    , 'http://a/b/c/g?y'),
new URITest('http://a/b/c/d;p?q', '..'     , 'http://a/b/'),
new URITest('http://a/b/c/d;p?q', '../../g', 'http://a/g')

This URITest class looks like this:

function MyTest(base, relative, expected) {
    Test.call(this, "Resolving " + relative + " against " + base);
    this._base = base;
    this._relative = relative;
    this._expected = expected;
}

extend(Test, MyTest);

MyTest.prototype.test = function() {
var resolved = URI.resolve(this._base, this._relative);
    this.assertEquals(this._expected, resolved);
};

This way you can represent your repetitive tests in a compact and readable way.

Developer information

If you would like to do some hacking on gltest, clone the source code into your development environment using Mercurial:

hg clone https://bitbucket.org/grauw/gltest

To contribute, contact me with a link to a repository with your changes and a description. Please adhere to the existing code style, and make small commits with good commit messages. If you like, send in your changes for review early, so we can discuss them and agree on their direction.

Authors

Source code

https://bitbucket.org/grauw/gltest

License

Copyright 2012 Laurens Holst

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.