Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Converting OpenCover to Lcov missing branch coverage #309

Closed
Cjewett opened this issue Jan 13, 2020 · 3 comments
Closed

Converting OpenCover to Lcov missing branch coverage #309

Cjewett opened this issue Jan 13, 2020 · 3 comments

Comments

@Cjewett
Copy link

Cjewett commented Jan 13, 2020

When converting from OpenCover to Lcov the Lcov file is missing branch coverage. Also, the test name is only populated for the first file and ignored for the rest.

Questions:

  1. Is there anything stopping Lcov from populating branch coverage if you're converting an OpenCover file which has branch coverage included?
  2. Should we not be putting TN: at the beginning of every file for coverage? My knowledge on this subject comes from istanbul which populates it and leaves the value empty (like "TN:") and it's good because it lets the user know a new fragment or file for coverage has started.
@danielpalme
Copy link
Owner

Will have a look within the next days.

@danielpalme
Copy link
Owner

Regarding 1:
Latest release 4.4.1 will also emit additional information, including branch coverage. The following elements are now available:

  • FNDA
  • FNF
  • FNH
  • BRDA
  • BRF
  • BRH

Regarding 2:
Every file starts with an SF element and end with end_of_record.
The TN element is intended for the overall test name and appears only once per file.
See: http://ltp.sourceforge.net/coverage/lcov/geninfo.1.php

@Cjewett
Copy link
Author

Cjewett commented Jan 14, 2020

@danielpalme Thank you for adding this!

Regarding 2: Understood. Not a huge deal so I'm okay to close this.

@Cjewett Cjewett closed this as completed Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants