Open zetanumbers opened 2 years ago
Happy to receive a PR doing this.
Would need to run each of the fuzz targets on CI (in separate jobs so we get parallelism) for ~5 minutes as well.
For now i made it possible to not enable quickcheck
via similarly named feature in #168.
I think it could be better to not switch to cargo-fuzz
if we would run 1 test in quickcheck. This would allow to check UB in the quickcheck!
code. However it would be desirable to write some predefined values to increase code coverage and for determinism.
quickcheck
tests are super long for miri (14m24s
enabled vs.1m48s
disabled). Perhaps it is better to separate "try to break the program by massaging input for a while" tests and usual tests?cargo-fuzz
defines fuzz targets, which already are separate from tests.