Add cargo-fuzz test harness for the qos_p256 crate #439
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
cr-tk
force-pushed
the
christian/qos_p256_fuzz1
branch
3 times, most recently
from
3591636 to
2bb6cc1
Compare
…rage guided testing
cr-tk
force-pushed
the
christian/qos_p256_fuzz1
branch
from
2bb6cc1 to
2416339
Compare
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.
Summary & Motivation (Problem vs. Solution)
Add some fuzzing test coverage of basic
qos_p256functions.How I Tested These Changes
Running the fuzz tests locally.
No change to production code.
Pre merge check list
Does not apply.