Support baseline to display zero coverage for "untouched" files

[vojtajina]

Currently, files that are never executed are not included in the report (even if they are instrumented).

This can be implemented using BaselineCollector gotwarlost/istanbul@092f336

[vojtajina]

One possible solution:

• preprocessor will patch the instrumenter in a similar to way to what gotwarlost/istanbul@092f336#L0R26 does
• preprocessor will create a hash object with all baseline data (similar to coverage object in gotwarlost/istanbul@092f336#L0R32)
• this "baseline" coverage will be published as "x:baselineCoverage" or something and the reporter will get it injected
• the reporter will add the baseline coverage data to each collector (after https://github.com/karma-runner/karma-coverage/blob/master/lib/reporter.js#L69 do something like collector.add(baselineCoverage)).

[vijtad]

Can you give an example how this switch includeBaseline can be used.
Is this switch true by default ?

[vijtad]

I found, we need to add the following switch in karma config js file.

includeBaseline : true,

[vijtad]

I used following package for these changes and I don't see your code changes.

Can you pls. let me know the correct command to pull your karma-coverage changes

{
"name": "ng-directive-testing",
"version": "0.0.0",
"description": "An example of testing AngularJS directives with Karma.",
"main": "",
"scripts": {
"test": "karma start --single-run --no-auto-watch"
},
"repository": {
"type": "git",
"url": "git://github.com/vojtajina/ng-directive-testing.git"
},
"author": "Vojta Jina vojta.jina@gmail.com",
"license": "MIT",
"devDependencies": {
"karma": "~0.10.8",
"karma-jasmine": "~0.1.3",
"karma-chrome-launcher": "~0.1.1",
"karma-phantomjs-launcher": "~0.1.1",
"karma-ng-html2js-preprocessor": "~0.1.0",
"karma-coverage": "~0.1.4",
"karma-junit-reporter": "~0.2.1"
}
}

Thanks,
Vijay

[robmcguinness]

+1

[dnoler]

+1

[nchase]

@vojtajina can you take a look at my pull request here? This issue is old but people are still commenting on the pull request as it is something they want.

[arkist]

+1. is there anything wrong with @nchase's PR?

[czers]

+1 - this feature is clearly missing from karma-coverage