grunt-contrib-jasmine/README.md

279 lines
8.5 KiB
Markdown
Raw Normal View History

2013-09-03 02:03:05 +08:00
# grunt-contrib-jasmine v0.5.1 [![Build Status](https://travis-ci.org/gruntjs/grunt-contrib-jasmine.png?branch=master)](https://travis-ci.org/gruntjs/grunt-contrib-jasmine)
2012-11-02 13:03:09 +08:00
> Run jasmine specs headlessly through PhantomJS.
2013-02-16 07:53:59 +08:00
2012-11-02 13:03:09 +08:00
## Getting Started
2013-02-18 21:42:28 +08:00
This plugin requires Grunt `~0.4.0`
2013-02-16 07:53:59 +08:00
If you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
2012-11-02 13:03:09 +08:00
```shell
2012-11-02 13:03:09 +08:00
npm install grunt-contrib-jasmine --save-dev
```
2013-02-21 01:42:59 +08:00
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
2013-02-18 21:42:28 +08:00
```js
grunt.loadNpmTasks('grunt-contrib-jasmine');
```
2013-02-16 07:53:59 +08:00
2012-11-02 13:03:09 +08:00
## Jasmine task
_Run this task with the `grunt jasmine` command._
2012-11-02 13:03:09 +08:00
2013-02-16 07:53:59 +08:00
Automatically builds and maintains your spec runner and runs your tests headlessly through phantomjs.
2013-08-13 00:59:02 +08:00
Substantial credit goes to [Camille Reynders](http://www.creynders.be/) (@creynders) for the first decent implementation
of jasmine through grunt which served as motivation for all the future work.
#### Run specs locally or on an ad hoc server
Run your tests on your local filesystem or via a server task like [grunt-contrib-connect][].
#### Customize your SpecRunner with templates
Supply your templates that will be used to automatically build the SpecRunner.
##### AMD Support
Supports AMD tests via the [grunt-template-jasmine-requirejs](https://github.com/jsoverson/grunt-template-jasmine-requirejs) module
##### Third party templates
- [RequireJS](https://github.com/jsoverson/grunt-template-jasmine-requirejs)
- [Code coverage output with Istanbul](https://github.com/maenu/grunt-template-jasmine-istanbul)
- [StealJS](https://github.com/jaredstehler/grunt-template-jasmine-steal)
[grunt-contrib-connect]: https://github.com/gruntjs/grunt-contrib-connect
2012-11-02 13:03:09 +08:00
### Options
#### src
Type: `String|Array`
*Minimatch* - Your source files. These are the files that you are testing.
2012-11-02 13:03:09 +08:00
#### options.specs
Type: `String|Array`
2012-11-02 13:03:09 +08:00
*Minimatch* - Your Jasmine specs.
2012-11-02 13:03:09 +08:00
#### options.vendor
Type: `String|Array`
2012-11-02 13:03:09 +08:00
*Minimatch* - Third party libraries, generally loaded before anything else happens in your tests. Libraries
like jQuery and Backbone.
2012-11-02 13:03:09 +08:00
#### options.helpers
Type: `String|Array`
2012-11-02 13:03:09 +08:00
*Minimatch* - Non-source, non-spec helper files. In the default runner these are loaded after `vendor` files
#### options.styles
Type: `String|Array`
*Minimatch* - CSS files that get loaded after the jasmine.css
2012-11-02 13:03:09 +08:00
2013-04-05 01:57:11 +08:00
#### options.version
2013-06-16 03:25:30 +08:00
Type: `String`
2013-04-05 01:57:11 +08:00
Default: '1.3.1'
This is the jasmine-version which will be used. currently available versions are:
* 1.0.0
* 1.1.0
* 1.2.0
* 1.3.0
* 1.3.1
#### options.outfile
2013-06-16 03:25:30 +08:00
Type: `String`
Default: `_SpecRunner.html`
2012-11-02 13:03:09 +08:00
The auto-generated specfile that phantomjs will use to run your tests.
Automatically deleted upon normal runs
#### options.keepRunner
2013-06-16 03:25:30 +08:00
Type: `Boolean`
Default: `false`
Prevents the auto-generated specfile used to run your tests from being automatically deleted.
#### options.junit.path
2013-06-16 03:25:30 +08:00
Type: `String`
Default: undefined
Path to output JUnit xml
#### options.junit.consolidate
2013-06-16 03:25:30 +08:00
Type: `Boolean`
Default: `false`
Consolidate the JUnit XML so that there is one file per top level suite.
#### options.host
2013-06-16 03:25:30 +08:00
Type: `String`
Default: ''
The host you want phantomjs to connect against to run your tests.
e.g. if using an ad hoc server from within grunt
2012-11-02 13:03:09 +08:00
```js
host : 'http://127.0.0.1:8000/'
```
Or, using templates
```js
host : 'http://127.0.0.1:<%= connect.port %>/'
```
Not defining a host will mean your specs will be run from the local filesystem.
#### options.template
2013-06-16 03:25:30 +08:00
Type: `String` `Object`
Default: undefined
Custom template used to generate your Spec Runner. Parsed as underscore templates and provided
the expanded list of files needed to build a specrunner.
You can specify an object with a `process` method that will be called as a template function.
2013-01-10 13:14:50 +08:00
See the [Template API Documentation](https://github.com/gruntjs/grunt-contrib-jasmine/wiki/Jasmine-Templates) for more details.
#### options.templateOptions
2013-06-16 03:25:30 +08:00
Type: `Object`
Default: `{}`
Options that will be passed to your template via an 'options' hash. Used to pass settings to the template.
### Flags
Name: `build`
Turn on this flag in order to rebuild the specrunner without deleting it. This is useful when troubleshooting templates,
running in a browser, or as part of a watch chain e.g.
```js
watch: {
pivotal : {
files: ['src/**/*.js', 'specs/**/*.js'],
tasks: 'jasmine:pivotal:build'
}
}
```
2013-09-03 02:03:05 +08:00
### Filtering specs
**filename**
`grunt jasmine --filter=foo` will run spec files that have `foo` in their file name.
**folder**
`grunt jasmine --filter=/foo` will run spec files within folders that have `foo*` in their name.
**wildcard**
`grunt jasmine --filter=/*-bar` will run anything that is located in a folder `*-bar`
**comma separated filters**
`grunt jasmine --filter=foo,bar` will run spec files that have `foo` or `bar` in their file name.
**flags with space**
`grunt jasmine --filter="foo bar"` will run spec files that have `foo bar` in their file name.
`grunt jasmine --filter="/foo bar"` will run spec files within folders that have `foo bar*` in their name.
#### Example application usage
- [Pivotal Labs' sample application](https://github.com/jsoverson/grunt-contrib-jasmine-example)
2012-11-02 13:03:09 +08:00
#### Basic Use
Sample configuration to run Pivotal Labs' example Jasmine application.
```js
// Example configuration
grunt.initConfig({
jasmine: {
pivotal: {
src: 'src/**/*.js',
options: {
specs: 'spec/*Spec.js',
helpers: 'spec/*Helper.js'
}
}
}
});
```
#### Supplying a custom template
Supplying a custom template to the above example
```js
// Example configuration
grunt.initConfig({
jasmine: {
customTemplate: {
src: 'src/**/*.js',
options: {
specs: 'spec/*Spec.js',
2013-04-05 01:57:11 +08:00
helpers: 'spec/*Helper.js',
template: 'custom.tmpl'
}
}
}
});
```
2013-01-10 13:14:50 +08:00
#### Sample RequireJS/NPM Template usage
2013-01-10 13:14:50 +08:00
```js
// Example configuration
grunt.initConfig({
jasmine: {
yourTask: {
src: 'src/**/*.js',
options: {
specs: 'spec/*Spec.js',
template: require('grunt-template-jasmine-requirejs')
}
}
}
});
2013-01-10 13:14:50 +08:00
```
NPM Templates are just node modules, so you can write and treat them as such.
Please see the [grunt-template-jasmine-requirejs](https://github.com/jsoverson/grunt-template-jasmine-requirejs) documentation
for more information on the RequireJS template.
2012-11-02 13:03:09 +08:00
## Release History
2013-09-03 02:05:30 +08:00
* 2013-08-02v0.5.2Fixed breakage with iframes /44 Added filter flag / 70 Fixed junit failure output /77
2013-06-19 01:24:52 +08:00
* 2013-06-18v0.5.1Merged /69 grunt async not called when tests fail OR keepRunner is true
* 2013-06-15v0.5.0updated rimraf made teardown async, added Function.prototype.bind polyfill breaking (templates) changed input options for getRelativeFileList breaking (usage) failing task on phantom error (SyntaxError, TypeError, et al)
2013-06-16 00:38:39 +08:00
* 2013-04-03v0.4.2bumped grunt-lib-phantomjs to 0.3.0/1.9 (closes merged addressed
* 2013-03-08v0.4.0bumped grunt-lib-phantomjs to 0.2.0/1.8 allowed spec/vendor/helper list to return non-matching files (e.g. for remote, http) merged merged
* 2013-02-24v0.3.3Added better console output (via Gabor Kiss @Neverl)
* 2013-02-17v0.3.2Ensure Gruntfile.js is included on npm.
* 2013-02-15v0.3.1First official release for Grunt 0.4.0.
* 2013-01-22v0.3.1rc7Exposed phantom and sendMessage to templates
* 2013-01-22v0.3.0rc7Updated dependencies for grunt v0.4.0rc6/rc7
* 2013-01-08v0.3.0rc5Updating to work with grunt v0.4.0rc5. Switching to this.filesSrc api. Added JUnit xml output (via Kelvin Luck @vitch) Passing console.log from browser to verbose grunt logging Support for templates as separate node modules Removed internal requirejs template (see grunt-template-jasmine-requirejs)
* 2012-12-03v0.2.0Generalized requirejs template config Added loader plugin Tests for templates Updated jasmine to 1.3.0
* 2012-11-24v0.1.2Updated for new grunt/grunt-contrib apis
* 2012-11-07v0.1.1Fixed race condition in requirejs template
* 2012-11-07v0.1.0Ported grunt-jasmine-runner and grunt-jasmine-task to grunt-contrib
---
2012-11-02 13:03:09 +08:00
Task submitted by [Jarrod Overson](http://jarrodoverson.com)
2012-11-02 13:03:09 +08:00
2013-09-03 02:05:30 +08:00
*This file was generated on Mon Sep 02 2013 11:05:17.*