Skip to content
This repository was archived by the owner on Feb 8, 2019. It is now read-only.
This repository was archived by the owner on Feb 8, 2019. It is now read-only.

report command using coverage dir data generates incorrect report #3

Open
@scottnonnenberg

Description

@scottnonnenberg
git clone [email protected]:istanbuljs/sample-mocha-compilers.git
npm install # with npm v3.8.2, node v4.3.2
npm run test
node ./node_modules/istanbul/lib/cli.js report --dir ./report
open report/lcov-report/index.html

The resultant report is broken:

screen shot 2016-03-19 at 4 59 49 pm

I've tried a number of things:

  • turning on inline babel sourceMaps
  • running the report command with babel-node
  • adding the --embed-source option to the npm run test command. Did this option get removed for v1?

This additional processing step is important because I'm trying to combine server and client results - not just for an overall number, but also for a combined HTML report. And the babel processing seems to be making it difficult. I'm also looking into updating karma-coverage to output something that istanbul report can understand; sad that they are not immediately compatible!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions