The documentation was pretty sparse on fuzzing.

First I had a tough time finding where my corpus was because no testdata dir was being generated- so I though "aha, must be an environment variable, something like GOFUZZCORPUS, but. nothing.

Then I started looking in go help test, took me a while to skim though and find that I needed to check out go help testfunc for more details only to find there was barely anything on fuzzing.

Relevant go help test output:

These additional files can contain test functions, benchmark functions, fuzz
tests and example functions. See 'go help testfunc' for more.

Relevant go help testfunc output:

A fuzz test is one named FuzzXxx and should have the signature,

	func FuzzXxx(f *testing.F) { ... }
// ...
The entire test file is presented as the example when it contains a single
example function, at least one other function, type, variable, or constant
declaration, and no tests, benchmarks, or fuzz tests.

There is no way to make out how the fuzzing command works from this. Please add better documentation of:

• Where the non-crashign fuzz corpus is located (GOCACHE)
• Where the crashing corpus is located
• What the differences are between both
• Fuzzing by default goes on forever
• How to add non crashing fuzz corpus to unit tests