Detect and execute fuzz targets as tests #1132
Merged
Conversation
This file contains hidden or 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
flimzy
reviewed
Aug 1, 2022
This should de-clutter tool.go a bit and help with maintainability in future.
One of the helper functions requires generics to work correctly. Until they are properly supported we have to stub it out. Generics support is tracked in gopherjs#1013.
flimzy
approved these changes
Aug 1, 2022
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.
This change adds support for discovering fuzz targets and executing them in unit test mode. The tests are executed with seed inputs only, since we don't have the
libfuzzerinfrastructure to actually perform fuzzing.While at it, I also factored out test function discovery into its own internal package, which is a step towards decluttering
tool.goand testing logic in it.Updates #1092.