i am looking for documentation about how to open/view/export the code coverage report,is there any?

[stefanaerts]

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

The log given by the failure.

Normally this include a stack trace and some more information.

Mention any other details that might be useful.

I would like to find some doc about how to view the code coverage report generated by angular-cli, i run "coverage": "lite-server -c bs-config.json"
,but is that the preferred way to do it? How can we export it to travis and watch it on some coverage reporting site(i read about coveralls, but is that what you recommend and how to do this)? Is there documentation? Thanks

---

Thanks! We'll be in touch soon.

[stefanaerts]

so in the mean time i see you use karma-coverage-istanbul-reporter,

1. what does this mean coverageIstanbulReporter: {
   reports: ['html', 'lcovonly'],
   fixWebpackSourcePaths: true

2. i see there is a file lcov.info generated in coverage folder, is there documentation on how to use this file(s) in the coverage folder to export in travis to a public website like Coveralls for example?

3. i noticed i had to add 'kjhtml' at the end of the first array to have the test report work together with the codecoverage report. ng test -cc wil not show the test results without this extra param.

reporters: config.angularCli && config.angularCli.codeCoverage
? ['progress', 'coverage-istanbul', 'kjhtml']
: ['progress', 'kjhtml'],

[filipesilva]

Heya @stefanaerts, we don't have any CLI specific documentation on how to use the generated code coverage. Instead, we mostly make sure the karma reporter can work.

How I do it is run ng test --code-coverage, and directly double click ./coverage/index.html. That is enough to see the html report.

The lvoc.info file is a common format that a lot of tools can read and generate reports from. I can't say I have a lot of experience with it though.

The original lcov tool is http://ltp.sourceforge.net/coverage/lcov.php, but you can also find a lot of lcov parsers in the NPM ecosystem: https://www.npmjs.com/browse/keyword/lcov

I tried a couple and the easiest one I found was https://www.npmjs.com/package/lcov-summary:

kamik@T460p MINGW64 /D/sandbox/master-project (master)
$ $(npm bin)/lcov-summary ./coverage/lcov.info

Code Coverage Results:

100.00% ( 3/ 3) D:\sandbox\master-project\src\polyfills.ts
100.00% (13/13) D:\sandbox\master-project\src\test.ts
100.00% ( 3/ 3) D:\sandbox\master-project\src\app\app.component.ts

Total Coverage: 100.00%

Also flagging this issue for community help to see if someone more knowledgeable can give better insight.

[stefanaerts]

when i enabled my public repo on coveralls and run
cat ./coverage/lcov.info | coveralls
i get this error -> Couldn't find a repository matching this job

[filipesilva]

Can't help you there, I don't know anything about coveralls.

[stefanaerts]

i just want to have it in travis running and published somewhere online,
for me its also new. I read about coveralls.

[filipesilva]

If I get this right, you can get a coveralls badge in github via their integration: https://github.com/integrations/coveralls

You'll have to read how to configure it though.

[stefanaerts]

i did,but not working.
i have enabled my github project and a badge is added to my readme.md from coveralls.
but i am trying to run it local on my laptop running node and npm.
coveralls -f ./coverage/lcov.info keeps hanging
cat ./coverage/lcov.info | coveralls gives the error message
I didn't run it on travis yet.

[filipesilva]

I'm sorry @stefanaerts, but I can't help you with that tool more than this. I don't have time to go learn how to use it right now.

[stefanaerts]

i understand @filipesilva ,thanks for your time and help.
I will figure it out.

[stefanaerts]

In the mean time i run it on travis and it works!
So the most important thing is that it works in the whole process with travis.
I run
after_success:

• npm run coveralls
  Then i have results on coveralls and a badge in my readme.md in github
  
  

if i want to a codecoverage report view local in a browser i can just open it local with
lite-server -c bs-config.json
"server": {
"baseDir": "./coverage"
}

or use the command line tool like you mentioned:
$(npm bin)/lcov-summary ./coverage/lcov.info