We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Fuzzing raw input is generally easier, but fuzzing the decisions would be more useful (but probably more involved/intrusive).
Some potentially helpful links:
https://github.com/pingcap/fail-rs https://rust-fuzz.github.io/book/introduction.html https://github.com/BurntSushi/quickcheck https://github.com/altsysrq/proptest
and might as well add this link from @lu-zero for posterity: https://doc.rust-lang.org/std/num/struct.Wrapping.html
The text was updated successfully, but these errors were encountered:
fail-rs let us leverage failpoints to force decisions that would be hard to trigger by simple input fuzzing.
proptest and quickcheck can simulate fuzzing effectively, while cargo-fuzz is sort of easy to access the functionalities offered by LLVM libFuzzer.
cargo-fuzz
Sorry, something went wrong.
Currently the decode/integration tests use random inputs, we can possibly expand them using cargo-fuzz.
Successfully merging a pull request may close this issue.
Fuzzing raw input is generally easier, but fuzzing the decisions would be more useful (but probably more involved/intrusive).
Some potentially helpful links:
https://github.com/pingcap/fail-rs
https://rust-fuzz.github.io/book/introduction.html
https://github.com/BurntSushi/quickcheck
https://github.com/altsysrq/proptest
and might as well add this link from @lu-zero for posterity:
https://doc.rust-lang.org/std/num/struct.Wrapping.html
The text was updated successfully, but these errors were encountered: