Fuzz tests for inclusion and consistency proofs

[hickford]

Fuzz tests for inclusion and consistency proofs

[codecov-commenter]

Codecov Report

Merging #33 (45167fc) into main (ca422cf) will increase coverage by 0.40%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   88.93%   89.33%   +0.40%     
==========================================
  Files           7        7              
  Lines         497      497              
==========================================
+ Hits          442      444       +2     
+ Misses         50       48       -2     
  Partials        5        5              

Impacted Files	Coverage Δ
testonly/tree.go	91.52% <0.00%> (+3.38%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ca422cf...45167fc. Read the comment docs.

[mhutchinson]

What's the motivation behind removing the 1.17 tests? The go.mod file still lists this version as 1.16 compatible. I'm up for bumping this to go1.17 to be consistent with trillian (and soon, trillian-examples: google/trillian-examples#669), but jumping to 1.18 invites using newer language features that may exclude people on older tooling. Not to say we absolutely can't do it, as we don't have an explicit policy, but we've tried to keep support for go versions in the order of a year old thus far.

[AlCutter]

It's the fuzz testing support - it's new in go1.18 testing lib, so the test would no-longer compile with older releases.

Agreed we should chat about the trade off.

[mhutchinson]

I've just seen #32 and think that this PR with the changes to keep support for 1.17 would make this a super 👍

[mhutchinson]

@AlCutter we could do with making a call on whether the init loops added to this, or the file-based approach in #35 should be our approach to seeding fuzz tests.

[mhutchinson]

@hickford can you take a look at & respond to the open comments on this PR. Once addressed one way or another, I can merge this.