Not working from CLI with mocha-phantomjs

[treyhunner]

I was trying to add code coverage to Parsley.js (on this branch).

I tried running the tests with the mocha-phantomjs-istanbul hook:

mocha-phantomjs -k mocha-phantomjs-istanbul test/index.html 

The tests executed but no files were generated. I ran istanbul report afterward and istanbul generated an empty report (0% coverage, no files).

I think I'm missing something. Do I need to tell mocha-phantomjs-istanbul which files need to be istanbul-instrumented or anything?

[danvk]

Try downgrading to mocha-phantomjs 3.x. I think mocha-phantomjs-istanbul needs to be updated for mocha-phantomjs 4.x.

[arnoudius]

I had the same issue and I solved it like so:

1. First I had to generate the instrumented version of the source via
   istanbul instrument -i ./src -o ./instrumented
2. For this project I am using RequireJS so I had to point to the instrumented code (instead of the actual code) in the RequireJS config file of my test project (using the baseUrl property).
3. Then I ran mocha-phantomjs -k mocha-phantomjs-istanbul ./test/test-runner.html which then generated the coverage.json file
4. Finally I ran istanbul report to generate the HTML report

[juancarlosfarah]

The steps described by @arnoudius worked for me too.

[hepabolu]

It's more than a year later, istanbul became nyc, mocha-phantomjs became mocha-phantomjs-core and my code is converted from ES6 using Babel. If anyone could help to update the steps outlined by @arnoudius I'd be very grateful.

[sakshij]

@arnoudius The steps mentioned by you worked like a charm. However, istanbul only checks files which are included in the tests instead of looking at all instrumented files when reporting coverage.
I have added include-all-sources: true to .istanbul.yml but that does not help.
Kindly suggest a solution for this.