npm install gouitest> Run Nodeunit unit tests.
~0.4.0If 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:
``shell`
npm install grunt-contrib-nodeunit --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
`js`
grunt.loadNpmTasks('grunt-contrib-nodeunit');
command._Task targets, files and options may be specified according to the grunt Configuring tasks guide.
This plugin provides server-side JavaScript unit testing via nodeunit. If you're looking to test JavaScript that uses
window or the DOM, please use the grunt-contrib-qunit pluginqunit task.
$3
#### Wildcards
In this example,
grunt nodeunit:all or grunt nodeunit will test all files ending with _test.js in the test directory.`js
// Project configuration.
grunt.initConfig({
nodeunit: {
all: ['test/*_test.js']
}
});
`With a slight modification,
will test files matching the same pattern in the test directory _and all subdirectories_.`js
// Project configuration.
grunt.initConfig({
nodeunit: {
all: ['test/*/_test.js']
}
});
`` * 2013-10-19 v0.2.2 Allow missing operators on error object.
* 2013-09-24 v0.2.1 Fix error display.
* 2013-05-23 v0.2.0 Bump nodeunit to v0.8.0
* 2013-02-15 v0.1.2 First official release for Grunt 0.4.0.
* 2013-01-18 v0.1.2rc6 Updating grunt/gruntplugin dependencies to rc6. Changing in-development grunt/gruntplugin dependency versions from tilde version ranges to specific versions.
* 2013-01-09 v0.1.2rc5 Updating to work with grunt v0.4.0rc5. Switching to this.filesSrc api.
* 2012-11-13 v0.1.1 Switch to this.file api internally.
* 2012-11-04 v0.1.0 Work in progress, not yet officially released.
---
Task submitted by "Cowboy" Ben Alman
This file was generated on Sat Oct 19 2013 14:59:01.