coredns/plugin/cache/fuzz.go

// +build fuzz

package cache

import (
	"github.com/coredns/coredns/plugin/pkg/fuzz"
)

// Fuzz fuzzes cache.
func Fuzz(data []byte) int {
	return fuzz.Do(New(), nil, data)
}
fuzz: put fuzzing stuff in own build tag (#1215) No need to have this build all the time. 2017-11-10 13:59:42 +00:00			`// +build fuzz`

Add fuzzing infrastructure (#1118) Fix file/fuzz.go build and docs in Makefile.fuzz Each plugin can add a fuzz.go to join the fuzzing craze. pkg/fuzz/do.go could be made a lot smarter, but is probably good enough for starters. $ make -f Makefile.fuzz <plugin> will build with go-fuzz-build and then execute a go-fuzz run. Each plugin's fuzz run uses a per-plugin directory to store the fuzz data. 2017-09-29 22:28:13 +01:00			`package cache`

			`import (`
			`"github.com/coredns/coredns/plugin/pkg/fuzz"`
			`)`

			`// Fuzz fuzzes cache.`
			`func Fuzz(data []byte) int {`
fuzzing: allow setup function to be called (#3175) This allows to fuzzing of more interesting targets that require setup. Signed-off-by: Miek Gieben <miek@miek.nl> 2019-08-24 18:13:47 +00:00			`return fuzz.Do(New(), nil, data)`
Add fuzzing infrastructure (#1118) Fix file/fuzz.go build and docs in Makefile.fuzz Each plugin can add a fuzz.go to join the fuzzing craze. pkg/fuzz/do.go could be made a lot smarter, but is probably good enough for starters. $ make -f Makefile.fuzz <plugin> will build with go-fuzz-build and then execute a go-fuzz run. Each plugin's fuzz run uses a per-plugin directory to store the fuzz data. 2017-09-29 22:28:13 +01:00			`}`