grunt-jasmine-node-coverage

Runs jasmine with Istanbul code coverage

A Grunt task to run your Jasmine feature suite using jasmine-npm and Istanbul for code coverage reports.

The minimum supported Node.js version is 4.2.0 (LTS), and while works also in 0.10.x, no quarantees are given.

Getting Started

Install this grunt plugin next to your project's Gruntfile.js with:

1npm install grunt-jasmine-node-coverage --save-dev

Then add these lines to your project's Gruntfile.js configuration file:

1grunt.initConfig({
2  jasmine_node: {
3    task_name: {
4      options: {
5        forceExit: true,
6        coverage: {
7          includeAllSources: true
8        },
9        jasmine: {
10          spec_dir: 'tests',
11          spec_files: [
12            '**/*spec.js'
13          ]
14        }
15      },
16      src: ['src/**/*.js']
17    }
18  }
19});
20
21grunt.loadNpmTasks('grunt-jasmine-node-coverage');
22
23grunt.registerTask('default', 'jasmine_node');

Configuring tasks

Grunt tasks should be configured by following the multi task configuration form, thus wrapping each configuration in an object inside the jasmine_node root object.

Task configuration options

options.jasmine

Type: object

Default: see below

Jasmine specific configuration. Use empty object, {} to use the defaults that are shown below.

1{
2  spec_dir: 'spec',
3  spec_files: ['**/*[sS]pec/.js'],
4  helpers: [],
5  reporters: {
6    spec: {}
7  }
8}

See the jasmine docs for more information on the supported configuration.

The reporters property allows the following properties:

• spec: used to configure the Jasmine spec reporter.
• teamcity set it to true in order to use Jasmine Reporters - TeamCityReporter.
• junitXml set it to a object to use Jasmine Reporters - JUnitXmlReporter. See the jasmine-reporters documentation for additional configuration options.

If teamcity reporter is set spec reporter will be disabled and teamcity reporter will be added to the coverage reporters as well.

Example of using teamcity reporter:

1{
2  spec_dir: 'spec',
3  spec_files: ['**/*[sS]pec/.js'],
4  helpers: [],
5  reporters: {
6    teamcity: true
7  }
8}

Example of using junitXml reporter:

1{
2  spec_dir: 'spec',
3  spec_files: ['**/*[sS]pec/.js'],
4  helpers: [],
5  reporters: {
6    junitXml: {
7      savePath: "reports",
8      consolidateAll: true
9    }
10  }
11}

options.coverage

Type: object

Default: see below

Istanbul specific configuration. Use empty object, {} to use the defaults that are shown below.

1{
2  reportFile: 'coverage.json',
3  relativize: true,
4  thresholds: {
5    statements: 0,
6    branches: 0,
7    lines: 0,
8    functions: 0
9  },
10  watermarks: {
11    statements: [50, 80],
12    lines: [50, 80],
13    functions: [50, 80],
14    branches: [50, 80],
15  },
16  includeAllSources: false,
17  reportDir: 'coverage',
18  report: [
19    'lcov',
20    'text-summary'
21  ],
22  collect: [ // false to disable, paths are relative to 'reportDir'
23    '*coverage.json'
24  ],
25  excludes: []
26}

Notes:

• The excludes list will automatically include '**/node_modules/**' internally.
• Setting the thresholds values greater than 0 will cause the task to fail if the specified threshold is not met.
• The watermarks config changes the thresholds at which the reports are displayed in red, yellow and green. It does not affect the outcome of the task.
• Setting the report list will allow different types of istanbul report to be set.

options.projectRoot

Type: string

Default: process.cwd()

See http://nodejs.org/api/process.html#process_process_cwd

options.forceExit

Type: boolean

Default: false

Exit on failure by skipping any asynchronous tasks pending.

options.captureExceptions

Type: boolean

Default: false

If set to true, will log all uncaught exceptions.

options.isVerbose

Type: boolean

Default: false

When true, istanbul will print more information when running.

Bugs

Help us to squash them by submitting an issue that describes how you encountered it; please be as specific as possible including operating system, node, grunt, and grunt-jasmine-node-coverage versions.

1npm --versions

Migration notes

v1.x -> v2.x

The spec reporter configuration has changed for v2 of this plugin. The following is an example of the change in configuration that is needed. This is not an exhaustive list: refer to the jasmine-spec-reporter for a full reference of the configuration options.

1// v1
2reporters: {
3  spec: {
4    colors: true,
5    displayStacktrace: 'summary',
6    displaySuccessfulSpec: true
7  }
8}
9
10// v2
11reporters: {
12  spec: {
13    colors: {
14      enabled: true
15    },
16    summary: {
17      displayStacktrace: true
18    },
19    spec: {
20      displaySuccessful: true
21    }
22  }
23}

v0.x -> v1.x

If you are updating to v1.x, you'll need to update your Gruntfile.

The following example outlines the changes needed. It assumes the following folder structure:

app/
├── src/
│   ├── abacus.js
│   └── calculator.js
└── test/
    ├── helpers.js
    └── specs/
        ├── abacus.spec.js
        └── calculator.spec.js

1// v0.5.0 config
2{
3  jasmine_node: {
4    task_name: {
5      options: {
6        match: '.',
7        matchAll: true,
8        specFolders: ['test'],
9        extensions: 'js',
10        specNameMatcher: 'spec',
11        useHelpers: true
12      }
13    }
14  }
15}
16
17// v1.0.0 config
18{
19  jasmine_node: {
20    task_name: {
21      options: {
22        jasmine: {
23          spec_dir: 'test',
24          spec_files: [
25            'specs/*.spec.js'
26          ],
27          helpers: [
28            'helpers.js'
29          ]
30        }
31      }
32    }
33  }
34}

Please note that the junit reporter is no longer available. If you are using this reporter and wish to update to v1, please open a new issue and we'll see if we can get it added back in. Even better, submit a PR :smile:

Release History

• v2.0.1 (2017-09-20)
  • Looks like the compatibility between different dependencies requires to use jasmine of version 2.5.2, which is not the latest (2.5.3)
• v2.0.0 (2017-09-20)
  • Breaking changes alert! Ensure you read the migration guide before updating from previous versions
  • Updated to jasmine-spec-reporter v3.3.0. Older style configuration needs to be updated, see migration guide for more details.
  • Removed support for Node.js v0.10
• v1.2.0 (2017-04-30)
  • Was compatible with Grunt 0.4 all the time, hence lowering the dependency requirement #60
• v1.1.1 (2016-08-29)
  • Istanbul v0.4.5 and using data.src instead of fileSrc for compatibility #59
• v1.1.0 (2016-08-23)
  • Add Node.js v0.10.0 support back by using var instead of const and let, #55
  • Teamcity reporter for Jasmine, #56
• v1.0.0 (2016-07-23)
  • Breaking changes alert! Ensure you read the migration guide before updating from previous versions
  • Minimum supported Node.js version is 4.2.0 (LTS), removed testing against 0.10
  • Migrated from jasmine-node to jasmine-npm #35 #48
  • Support includeAllSources istanbul coverage option #45 #50
  • Support thresholds for passing/failing build #25
  • Removed junit reporter
• v0.5.0 (2016-05-03)
  • Grunt.js version 1.0 support
  • ESLint configuration migration to 2.0
  • Remove bin path #29
  • Update license property for todays requirements
  • Do not always make lcov output
• v0.4.1 (2015-02-27)
  • Reports should be collected from where they were written #42
• v0.4.0 (2015-02-19)
  • Other Grunt tasks were not ran when this failed, #40
• v0.3.2 (2015-02-04)
  • Fixes for failure cases and documentation, #33, #36, #37 and #38
• v0.3.1 (2014-11-21)
  • Installation failed
  • Should fix #30
• v0.3.0 (2014-11-09)
  • Grunt usage as multi task
  • Fixes #12 and #18
• v0.2.0 (2014-11-03)
  • Better Grunt API usage
  • Fixes #10, #13, #14, #16, #19 and #20
• v0.1.11 (2014-05-15)
  • Task name fix for grunt.renametask use case
• v0.1.10 (2014-04-07)
  • JSHint configuration and task exit fixes
• v0.1.9 (2014-04-02)
  • Configuration for jasmine_node.options.isVerbose was not working
• v0.1.8 (2014-03-03)
  • Add captureExceptions support and quit on exception
• v0.1.7 (2013-12-13)
  • Istanbul update, threshold configuration and JUNit output
• v0.1.6 (2013-07-26)
  • Change isVerbose option to verbose
• v0.1.5 (2013-07-15)
  • Initial coverage with Istanbul release, originally forked from grunt-jasmine-node

License

Copyright (c) 2013 "jribble" Jarrod Ribble & contributors. Based on grunt-jasmine-node.

Copyright (c) 2012 "s9tpepper" Omar Gonzalez & contributors. Licensed under the MIT license.