Port fuzz testing to Go 1.18 native fuzzing #508
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Go 1.18, due to be released in February 2022, adds built-in fuzz testing capabilities. Please see the latest documentation at https://go.dev/doc/fuzz/ (note that the corpus directory structure has changed somewhat since the initial proposal and implementation).
This PR ports @alisdair's work on fuzz testing from the go-fuzz library to the new native fuzzing. Once this is merged, oss-fuzz and internal fuzzing efforts will be updated.
The main changes this PR makes are:
testdata/fuzz/<fuzz test name>fuzz_test.gotesting.FTests will fail until this repo's CI uses Go 1.18. To test this PR, you can use gotip, or just wait until Go 1.18 is released.