Repository navigation
Add fuzz targets and randomized round-trip tests - #19
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
tests/roundtrip.rsruns deterministic randomized checks (5000 iterationseach by default,
DATAURL_ROUNDTRIP_ITERATIONSfor more): parsing neverpanics, and anything that parses or gets set survives being serialized
and parsed again, with every combination of encoding and escaping, with
the second round being identical to the first.
The same checks (
tests/common/roundtrip.rs) back two cargo-fuzz targetsin fuzz/, which isn't part of the published crate.
Parsing can't allocate more than a small multiple of its input, since
decoded data is never larger than the input; that's now documented,
instead of adding a size limit option that wouldn't protect anything.