Explore >> Select a destination
|
You are here 
|
ha.nnes.dev | ||
| | | | |
hypothesis.works
|
|
| | | | | The Encode/Decode invariant One of the simplest types of invariant to find once you move past just fuzzing your code is asserting that two different operations should produce the same result, and one of the simplest instances of that is looking for encode/decode pairs. That is, you have some function that takes a value and encodes it as another value, and another that is supposed to reverse the process. This is ripe for testing with Hypothesis because it has a natural completely defined specification: Encoding and then decoding should be exactly the same as doing nothing. Lets look at a concrete example. Test faster, fix more | |
| | | | |
unicode-explorer.com
|
|
| | | | | Copy and paste U+3164 HANGUL FILLER to send an invisible, blank, empty WhatsApp message. | |
| | | | |
blog.trailofbits.com
|
|
| | | | | By Matt Schwager Trail of Bits is excited to introduce Ruzzy, a coverage-guided fuzzer for pure Ruby code and Ruby C extensions. Fuzzing helps find bugs in software that processes untrusted input. In pure Ruby, these bugs may result in unexpected exceptions that could lead to denial of service, and in Ruby C extensions, they... | |
| | | | |
blog.suborbital.dev
|
|
| | | A bit about me I'm Philippe, and I'm Technical Account Manager at GitLab. I am french, but you cannot hear my lovely accent. I love a lot speaking in front of people, mainly in French (it's, of course, easier for me), so I wrote this blog post like i... | ||
