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

Track coverage of fuzz targets #10

Open
Crypt-iQ opened this issue Jun 20, 2023 · 0 comments
Open

Track coverage of fuzz targets #10

Crypt-iQ opened this issue Jun 20, 2023 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Crypt-iQ
Copy link
Collaborator

  • We should get a visual output of the fuzz coverage for each target individually and combined. This can let us know if certain branches aren't taken.
  • This could be done via go coverage files.
  • Once we are fuzzing continuously, we can then take the coverage files and update a website daily with updated fuzzing coverage. In my mind, it would sort of look like this bitcoind fuzzing coverage webpage I made: https://crypt-iq.github.io/19379_fuzz_cov/
@Crypt-iQ Crypt-iQ added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Jun 20, 2023
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 help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant