Implement proptest strategy which derives an InputValue consistent with a given AbiType
#5226
Labels
good first issue
Good for newcomers
Comments
5 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 13, 2024
# Description ## Problem\* Resolves #5226 ## Summary\* This PR adds property testing to ABI encoding so that we can show that any valid `Abi` + `InputMap` combination can be abi encoded and decoded to return the original inputs. ## Additional Context ## Documentation\* Check one: - [x] No documentation needed. - [ ] Documentation included in this PR. - [ ] **[For Experimental Features]** Documentation to be submitted in a separate PR. # PR Checklist\* - [x] I have tested the changes locally. - [x] I have formatted the changes with [Prettier](https://prettier.io/) and/or `cargo fmt` on default settings.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #5216 we added usage of a proptest strategy which generates pairs of
AbiTypeandInputValuewhich are compatible with each other.An interesting extension for this is to instead have a strategy to generate an
InputValuewhich is compatible with an existingAbiValue. This would allow us to generate a set of plausible inputs to a Noir program given its ABI. This would then form the basis of being able to fuzz Noir test programs.The text was updated successfully, but these errors were encountered: