lightninglabs / lnd-fuzz Goto Github PK

@Roasbeef @Crypt-iQ

Thanks for creating the repo!

We should start by uploading the current best corpus we have for each fuzz target. The directory structure go test expects is:

brontide/
  testdata/
    fuzz/
      FuzzRandomActOne/
        <seed corpus>
      FuzzRandomActThree/
        <seed corpus>
      ...
lnwire/
  testdata/
    fuzz/
      FuzzAcceptChannel/
        <seed corpus>
      FuzzOpenChannel/
        <seed corpus>
      ...
...

If you guys don't have existing corpora to upload, I can also work on generating them for each fuzz target.

• 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/