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

coverage tool: also save coverage summary for lcov #16

Open
fuzzah opened this issue Apr 27, 2022 · 1 comment
Open

coverage tool: also save coverage summary for lcov #16

fuzzah opened this issue Apr 27, 2022 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@fuzzah
Copy link
Member

fuzzah commented Apr 27, 2022

For golang we save coverage summary file, for lcov we don't.
Summary file is easier to store and easier to parse by external tools.

@fuzzah fuzzah added enhancement New feature or request good first issue Good for newcomers labels Apr 27, 2022
@fuzzah
Copy link
Member Author

fuzzah commented Sep 13, 2023

Having fuzzed lots of different apps I've come to conclusion we'd need more flexibility regarding these options. Some programs are that huge, so it takes a lot of time to create a coverage report be it HTML or TXT. Forcefully creating both reports would waste a lot of time.
User should be in charge of what reports to create, e.g. by specifying some option with available choices: html, txt, both

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant