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

grunt-qunitnode

v1.0.0

Published

A Grunt task plugin to execute QUnit tests in Node.js.

Downloads

20

Readme

grunt-qunitnode Build Status: Linux

A Grunt task plugin to execute QUnit tests in Node.js.

Getting Started

This plugin requires Grunt ~0.4.0

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-qunitnode --save-dev

Using

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks( 'grunt-qunitnode' );

grunt.initConfig({
	qunitnode: {
		src: [ "test/mylib_test_a.js", "test/mylib_test_b.js" ]
	}
});

Source/Test Files

You should call your test files here. As in Node you can require the files to be tested in your test files, it's not necessary to load those via grunt. Otherwise, simply add them first.

This next example calls the source file that will be tested as well:

grunt.initConfig({
	qunitnode: {
		all: [ "src/mymodule.js", "test/mymodule.js" ]
	}
});

Globbing Patterns a.k.a. Wildcards

This plugin support Grunt Globbing Patterns, as seen in the example below:

// Project configuration.
grunt.initConfig({
	qunitnode: {
		all: [ "test/**/*.js" ]
	}
});

Node QUnit task

Run this task with the grunt qunitnode command.

Task targets, files and options may be specified according to the grunt Configuring tasks guide.

Options

force

Type: boolean Default: false

When true, the whole task will not fail when there are individual test failures, or when no assertions for a test have run. This can be set to true when you always want other tasks in the queue to be executed.