/explore
|
You are here 
|
blog.nelhage.com | ||
| | | | |
ha.nnes.dev
[AI summary] The author used a generic fuzzer to discover a crash trigger in a Roc program's grapheme splitting logic caused by unexpected zero-width joiner handling in Unicode strings. |
|
| | | | | ||
| | | | |
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 |
|
| | | | | ||
| | | | |
arne-mertz.de
Contents Inmy last post I have written about the main and secondary usesof unit tests and how they compare to other kinds of automated tests. This time I will explore [...] |
|
| | | | | ||
| | | | |
ivaylopavlov.com
On my quest to make shorter videos on programming fundamentals, I'm kicking this initiative with a video explaining the mechanics of compiled and interpreted programming languages and the trade-offs associated with each. The presentation inside Read more... |
|
| | | |||
