test: add fuzzing set up #1497
Open
test: add fuzzing set up #1497
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
Signed-off-by: David Korczynski <[email protected]>
nedbat
reviewed
Jan 27, 2023
| "data", | ||
| [ | ||
| b"random_data", | ||
| b"more random data" |
There was a problem hiding this comment.
I don't understand how atheris works. What does it do with these two data strings?
There was a problem hiding this comment.
I only added these strings just to make it such that the fuzzer could be tested with pytest -- to e.g. check that the fuzzer won't break.
The data from pytest.mark.parametrize( is not used in the actual fuzzing runs.
|
Are this and #1490 still valid? |
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 is an effort to migrate fuzzers from OSS-Fuzz to upstream.
I've added it such that it's also a unit test that is run by way of pytest. The reason for doing so is to make it easier to test that the fuzzers won't break during development.
If you are interested in this addition, then I can refine the build script on the OSS-Fuzz side (https://github.com/google/oss-fuzz/blob/master/projects/coveragepy/build.sh) such that it builds all files prefixed
test_fuzzin the tests/ directory as fuzzers and will run them on OSS-Fuzz accodingly. This will make it trivial to add new fuzzers to the continuous fuzzing set up.Ref:
Signed-off-by: David Korczynski [email protected]