Generate code coverage using Istanbul.
The easiest way is to keep karma-coverage as a devDependency in your package.json.
{
"devDependencies": {
"karma": "~0.10",
"karma-coverage": "~0.1"
}
}You can simple do it by:
npm install karma-coverage --save-devFollowing code shows the default configuration...
// karma.conf.js
module.exports = function(config) {
config.set({
files: [
'src/**/*.js',
'test/**/*.js'
],
// coverage reporter generates the coverage
reporters: ['progress', 'coverage'],
preprocessors: {
// source files, that you wanna generate coverage for
// do not include tests or libraries
// (these files will be instrumented by Istanbul)
'src/*.js': ['coverage']
},
// optionally, configure the reporter
coverageReporter: {
type : 'html',
dir : 'coverage/'
}
});
};Example use with a CoffeeScript project...
// karma.conf.js
module.exports = function(config) {
config.set({
files: [
'src/**/*.coffee',
'test/**/*.coffee'
],
// coverage reporter generates the coverage
reporters: ['progress', 'coverage'],
preprocessors: {
// source files, that you wanna generate coverage for
// do not include tests or libraries
// (these files will be instrumented by Istanbul via Ibrik unless
// specified otherwise in coverageReporter.instrumenter)
'src/*.coffee': ['coverage'],
// note: project files will already be converted to
// JavaScript via coverage preprocessor.
// Thus, you'll have to limit the CoffeeScript preprocessor
// to uncovered files.
'test/**/*.coffee': ['coffee']
},
// optionally, configure the reporter
coverageReporter: {
type : 'html',
dir : 'coverage/'
}
});
};Type: String
Possible Values:
html(default)lcov(lcov and html)lcovonlytexttext-summarycobertura(xml format supported by Jenkins)teamcity(code coverage System Messages for TeamCity)
If you set type to text or text-summary, you may set the file option, like this.
coverageReporter: {
type : 'text',
dir : 'coverage/',
file : 'coverage.txt'
}If no filename is given, it will write the output to the console.
Type: String
Description: This will be used to output coverage reports. When
you set a relative path, the directory is resolved against the basePath.
You can use multiple reporters, by providing array of options.
coverageReporter: {
reporters:[
{type: 'html', dir:'coverage/'},
{type: 'teamcity'},
{type: 'text-summary'}
],
}Karma-coverage infers the instrumenter regarding of the file extension. The .coffee files are by default covered using Ibrik (an Istanbul analog for CoffeeScript files). It is possible to override this behavior and point out an instrumenter for the files matching a specific pattern. To do so, you need to declare an object under with the keys representing the pattern to match, and the instrumenter to apply. The matching will be done using minimatch. If two patterns match, the last one will take the precedence.
coverageReporter: {
instrumenter: {
'**/*.coffee': 'istanbul' // Force the use of the Istanbul instrumenter to cover CoffeeScript files
},
// ...
}For more information on Karma see the homepage.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent