Implement MVP implementation of Noir fuzz tests #5249
Assignees
Labels
test harness
Related to the testing of noir code through `nargo test`
Comments
5 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 18, 2024
# Description ## Problem\* Step towards #5249 ## Summary\* This PR adds a very simple fuzzer which can be used to find inputs to Noir programs which fail to execute. The motivation for this is to eventually allow `nargo test` to run on noir functions with arguments and automatically fuzz them in a similar fashion to `forge test`. It's currently very hit and miss on how quickly it can zero in on failing cases. For example, the program below is near-unfuzzable currently. ```rust fn main(x: u32, y: u32) { assert(x != y); } ``` ## Additional Context ## Documentation\* Check one: - [ ] No documentation needed. - [ ] Documentation included in this PR. - [x] **[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.
TomAFrench
added
the
test harness
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are currently using
proptestto fuzz the ABI encoding code such that given an ABI, we can generate a set of plausible inputs for it. This provides a route for us to be able to perform fuzzing of Noir programs by hooking this up to the ACVM.We can take a lot of inspiration from Foundry's fuzzing implementation as they use proptest to generate inputs as well so we can potentially reuse a fair amount of code: https://github.com/foundry-rs/foundry/blob/master/crates/evm/evm/src/executors/fuzz/mod.rs#L29
MVP Tasks
Once this is done, we can follow up with #5262
The text was updated successfully, but these errors were encountered: