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.
Description
Initialize a stateful fuzz harness at pkg/vault/test/foundry/fuzz/FuzzHarness.sol plus medusa & echidna config files, gitignore updates, and package.json scripts.
To run, we'll need to install either medusa or echidna. Note that we need to use a version of medusa that includes a recent bugfix. Installing the
master
branch from source will work, but a new release that includes this fix will be published soon. Echidna's performance may be degraded slightly due to slither failures (slither works with hardhat but echidna needs foundry).Unfortunately, this PR re-introduces a copy of the legacy
VaultMockDeployer
foundry test util. Medusa's cheatcode support is not up to parity with foundry, so replacing this with the newVaultContractsDeployer
util may require some adjustment.When you're ready, run
yarn run fuzz:medusa
oryarn run fuzz:echidna
from the vault package to kick off a fuzzing campaign.By default, this will run optimization fuzz tests. Change the
ASSERT_MODE
constant in the FuzzHarness contract to true to switch to assertion mode.Enjoy!
Type of change
Checklist:
main
, or there's a description of how to merge