Document proptest support for property tests - #2765
Draft
leighmcculloch wants to merge 2 commits into
Draft
Conversation
|
Preview is available here: |
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.
What
Add a "How to Write Property Tests" section to the fuzzing guide, and expand the fuzzing example's property-test section, covering how to bridge
SorobanArbitrary/Arbitraryprototypes toproptestStrategys withproptest-arbitrary-interop.Why
The fuzzing docs only ever discussed
cargo-fuzz, so developers writing property tests found nothing onproptestand reasonably concluded it wasn't supported; stellar/rs-soroban-sdk#2011 fixed this gap in the SDK's own rustdoc, and this PR brings the docs site's guides in line with it.