fuzz-utils
fuzz-utils copied to clipboard
crytic
A tool to automatically generate Foundry unit test cases from Echidna and Medusa failed properties
### Describe the desired feature This could be a solution/workaround for this Echidna issue: https://github.com/crytic/echidna/issues/1231#issuecomment-2095509581
### Describe the issue: When multiple contracts have functions with the same signature fuzz-utils will generate the same function multiple times, preventing compilation. We should: - Add a prefix to...
### Describe the desired feature In case of upgradeable contracts we might want to deploy the contracts as proxies and initialize them. This should be automatically handled if we can...
### Describe the issue: Echidna allows contracts to be deployed to specific addresses using the `deployContracts` configuration option. However, when the tests are generated, only the harness is constructed and...
### Describe the desired feature For example: - Include only call sequences whose names are contained in a user provided list - Include only call sequences that contain a call...
### Describe the desired feature I would like to get a coverage report chart by parsing Echidna/Medusa logs Example ``` echidna . --target CryticTester --config echidna.yaml | fuzz-utils --chart ```...
### Describe the issue: It can happen that in the corpus a function call has the address of the echidna contract as a parameter, for example `callSomething(24, 17, 0x00a329c0648769A73afAc7F9381E08FB43dBEA72)`. In...
### Describe the desired feature The `template` command assumes the project uses Foundry, we should add hardhat support.
### Describe the desired feature - [x] Fix failing Medusa tests by: - [x] Adding a medusa corpus for value transfer - [x] Removing non-failing call sequences from the corpora...
### Describe the issue: It is possible for echidna reproducers or corpus entries to have transactions that revert. When those transactions are converted to a foundry test, the whole test...