Add support for lcov output #643
Comments
do you have the XML to LCOV converter - perhaps we can just chain that in. |
I tried searching for it but couldn't find anything useful. |
I assumed from this statement it was something you were doing already - no worries. |
The LCOV format is really as simple as documented here -- a whole lot of sections, starting with a |
Here's a quick and dirty powershell script that should do OpenCover to lcov format; the main thing that might need tweaking is the branch block-number, which I've used the offset value for. If this has to be unique across more than a single method, then it would want to be something like (offset + 1000 * line number) to make unique per file
|
It will be great, because on vscode there is only Coverage plugins that use lcov format and no one other support xml report from Open Coverage. |
Please provide the following information when submitting an issue, where appropriate replace the
[ ]
with a[X]
My Framework
My Environment
I have already...
My issue is related to (check only those which apply):
Expected Behavior
Many of the modern projects have a lot of the logic written on front-end in a javascript framework. Most of the javascript testing framework and coverage frameworks generate lcov file for coverage. When, we use code coverage reporter service like coveralls. They take a single file as input. It can either be OpenCover.xml or coverage.lcov. If we want to combine both files, we wither have to do XML to lcov or lcov to XML conversion and merge both files and submit it to the service. It becomes hectic for each project. It would be a nice feature we could specify lcov format of output in opencover. Then we are left with the task of merging the files only.
Just to summarise, I am looking for support of lcov output format.
Actual Behavior
Fill me in...
Steps to reproduce the problem:
Fill me in...
The text was updated successfully, but these errors were encountered: