I'd like to do a blog post on writing fuzzable code, what did I leave out of my list?pic.twitter.com/hZ7KseXTrn
-
Might be worth exploring DeepState from
@trailofbits for fuzzable unit testing.
I gave a somewhat entertaining keynote on testability at HCSS this year: https://github.com/trailofbits/publications/tree/master/presentations/What%20blockchain%20got%20right … DeepState is here btw:https://github.com/trailofbits/deepstate …
-
-
Agree with your point #1: Global mutable state is the root of all evil: break programs into smaller units. I would further stress reproducible builds, CI, containers, and sandboxing or declarative pkg managers. And use types ffs.
-
This forum post is a great case study in writing testable code, and the contortions that fuzzers must go through to work in many cases:https://forum.openzeppelin.com/t/using-automatic-analysis-tools-with-makerdao-contracts/1021/2 …
End of conversation
New conversation -
-
-
thanks!
-
Strongly agreed: Most of the same things that make code unit-testable make it fuzzable. Create entrypoints for testing each different type of input. (And fuzz those input types separately, the mutators work better that way - e.g., separate out PNG testing from JPG testing).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.