47 seconds of fuzzing in CI (opens in new tab)
Anytime I fuzz a piece of code for the first time I’m always surprised by how trivially broken it is. The first fuzzing run always finds bugs within a few seconds of starting. Maybe I’m just bad at programming, but I suspect that experience is common. In case you’re not familiar, fuzzing is a testing technique where your program is fed (purposefully) random inputs. The goal is to remove our own biases in deciding what to test and automatically exercise all possible paths through our program. ...
Read the original article