-
Add a fuzzy testing framework and tests.
You can start by creating a fuzzer folder, with a skeleton structure of a fuzzer, like we do in the VM
https://github.com/lambdaclass/cairo-vm/blob/95d2c88fc…
-
Use American Fuzzy Lopp fuzzer or similar.
-
I cant find any information about using gotestsum with fuzzy testing. Is there any way to use it?
https://go.dev/doc/security/fuzz/
The idea would be to set a duration for the fuzz and let it ru…
-
fuzz testing this crate would be really nice. And it also seems relatively simply to do so, because many random bytes actually yield valid EBML content, so the parser can go into different code paths.
-
Some tools: https://wiki.python.org/moin/PythonTestingToolsTaxonomy#Fuzz_Testing_Tools
sebix updated
3 years ago
-
- https://github.com/verificarlo/fuzzy
- Adding numerical perturbation to software library testing
gkiar updated
3 years ago
-
We should use fuzzy testing. That means algorithmically generate valid specs that we run through validation (they should all pass). Also, we should algorithmically generate invalid specs that we run t…
-
https://github.com/erigontech/silkworm/actions/runs/9143609277/job/25140482058
I suspect it's due to missing check on presence of non-empty `params`, but I've not analysed the stack trace properly.
-
Use Schemathesis to provide fuzzy testing on the API so that we can find and fix errors.
-
reviewing the codebase we can find a few crates that are not used neither by any other crate nor in the ci. we should decide what we do with those.
First one to discuss is `protocols/fuzz-testing`.…