Run Nodeunit unit tests
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-contrib-nodeunit --save-dev
Run this task with the
grunt nodeunit command.
Task targets, files and options may be specified according to the grunt Configuring tasks guide.
There may be a few differences versus running
nodeunit on the command line:
Nodeunit's reporters (such as
default) are in charge of tracking tests that do not complete. They often hook
grunt is handling the runtime, it does not exit, so the reporter's clean-up code
that monitors undone tests does not fire. Additionally, the reporters do not expose the number of "Undone" tests in their
This can cause problems. For example, if an exception is thrown in an undone test, the exception might bubble up into the
grunt runtime if it's still running. This would cause
grunt to exit, while
nodeunit command line would show the undone
If you're getting strange
grunt runtime errors or seeing
grunt exit, check for "undone" tests.
Specifies the reporter you want to use. For example,
Specifies the file the
reporter's output should be saved to. For example,
Specifies the options passed to the
reporter. For example, the
junit reporter requires the
to be set:
In this example,
grunt nodeunit:all or
grunt nodeunit will test all files ending with
_test.js in the
With a slight modification,
grunt nodeunit:all will test files matching the same pattern in the
test directory and all subdirectories.
To use a reporter other than the default one, you can specify the
Task submitted by "Cowboy" Ben Alman
This file was generated on Fri Mar 04 2016 15:41:50.