question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider adding coverage reports (e.g. for lcov format)

See original GitHub issue

Hey there,

first, thanks for your work, this github action is awesome!

Nevertheless, it would be even more awesome, if one could see code coverage information next to the test reports. Maybe an additional property coverage-files could be added (see this one as an example), which takes lcov files as an input and displays the information if the property is set? What are your thoughts about that?

Thanks in advance. Best regards, Alex

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:2
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
dornycommented, May 23, 2021

Thanks, that makes sense.

For the beginning, I would like to support lcov and cobetura formats. Results should be in the form of a table - either by files, classes, or whole projects. I’m not sure if it should be in the same check run as test results or a separate one. Check run summaries are limited to 65k bytes - there might be not enough space for both test results and coverage results.

Existing actions, including the one you linked, just wrap other tools that convert coverage files into HTML. Here I would have to do parsing and visualization from scratch. It will need some time. I will put this on my to-do list but unfortunately, it won’t be done anytime soon. I just got a new job and my availability for this project is quite limited now. In the next months, I will focus rather on bug fixes and simpler improvements than a completely new feature.

0reactions
PavanMudigondaTRcommented, Oct 31, 2021

Hi Dorny, I have the same request. If you could add Jacoco and Corbetura icov support by parsing XML and displaying in table similar to test results display. I understand you are busy with new job. Just when ever you can get to it.

Thank you for this awesome github action you have created.

Read more comments on GitHub >

github_iconTop Results From Across the Web

LCOV Code Coverage - The Document Foundation Wiki
This short tutorial aims to describe how to generate lcov reports. ... Create an ~/.lcovrc file in your home directory and add the...
Read more >
Coverage support for LCOV? · Issue #797 · onsi/ginkgo - GitHub
I've improved how coverage reporting works in V2 and could imagine adding this as an additional flag/option (e.g. -cover-format=lcov ). after v2 ships....
Read more >
How to use LCOV for analyzing the test coverage ... - EDB
Prabhat Sahu walks step by step through the process of using LCOV for analyzing the test coverage against PostgreSQL.
Read more >
Generating Code Coverage Report Using GNU Gcov & Lcov.
This will create a coverage report by taking . gcno and . gcda files from '. ' i.e. current folder where these files...
Read more >
Support lcov for cfamily code coverage reports - Sonar
Before considering adding support for lcov format, it would be nice to understand the benefits. Is it because lcov is easier to use...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found