Go Fuzz Testing

That first example is deceptive. In this line:<p><pre><code> for i := 0; i &lt;= n; i++ { </code></pre> The &quot;&lt;=&quot; character just looks like a &quot;&lt;&quot; character due to the typeface that the author chose. I&#x27;m going to assume that wasn&#x27;t an accident because it perfectly masks the obvious bug in the for loop.<p>When I did a quick scan of that code it looked good to me. Then he claimed it should panic and I felt crazy. So I copy&#x2F;pasted the code into an editor to see wtf was going on and sure enough it was &quot;&lt;=&quot;.

<p><pre><code> go test fuzz v1 string(&quot;000000000000000000000000000000Ö00000000000000000000000000000&quot;) rune(&#x27;\u0083&#x27;) int(60) </code></pre> Interesting that the minimization engine wasn&#x27;t able to shrink this further.

It’s a bit surprising to have fuzzing as part of the standard tool chain, but not property based testing.<p>I guess we still need to rely on something like gopter.

I&#x27;m pretty sure fmt.Println(&quot;HELLO&quot;, str, len(str), len(result), n) isn&#x27;t supposed to be in the final solution? :)

Neat, Andrei. Good luck with this venture!

Curious if fuzzing is a common thing in network programming, does fuzzing plays nicely with binary inputs?

What’s the rationale behind bundling a fuzzing library in the language instead of as a separate library?