Fix bugs in Foundry test generation#1516
Merged
gustavo-grieco merged 8 commits intocrytic:dev-improve-foundry-supportfrom Jan 26, 2026
Merged
Fix bugs in Foundry test generation#1516gustavo-grieco merged 8 commits intocrytic:dev-improve-foundry-supportfrom
gustavo-grieco merged 8 commits intocrytic:dev-improve-foundry-supportfrom
Conversation
Member
|
I think the second bug might be the one we solved here: #1514 |
Contributor
Author
|
@elopez Thanks! Checked and it looks fine. I think the end-to-end null byte test brings value, because it is checking if the generated test actually compiles with forge. However, I'll leave the final decision up to @gustavo-grieco and you. |
e34cff3
into
crytic:dev-improve-foundry-support
1 check passed
gustavo-grieco
added a commit
that referenced
this pull request
Mar 13, 2026
* improved support for foundry tests * Extend Foundry support testing (#1512) * Fix lint failures * ci: bump python version to 3.10, clone submodules * some fixes when using foundry mode * Update hevm to `542986dea3bec4f5898731ff48877a7a21811bf4` * Fix bugs in Foundry test generation (#1516) * Fix fallback function bug in Foundry test generation * Fix null byte in argument bug in Foundry test generation * Remove unnecessary config file * Remove unused/redundant imports * Disable Slither in Foundry test gen tests * Conditionally run forge-std tests based on the solc version * Reduce unnecessary test grouping and improve failed assertion messages --------- Co-authored-by: Emilio López <[email protected]> * Update hevm to `41e6d1304411749ea8c816d131991663b5dca67a` * Fix linter and build errors (#1521) * improve foundry stateful invariant testing * fix * Fix foundry test generation linter hints and tests (#1522) * Foundry updates (#1525) * Rename dapptest to foundry and support foundry assertX in assertion mode * Rename basic foundry test contracts dir to `foundry-basic` * Add testing modes to `README` * fixes * fixes * Add support for Foundry assume (#1528) * flake: sync hevm version with stack.yaml * Clarify `optimization` test mode in `README` (#1529) * IS_TEST fix --------- Co-authored-by: Radu Bahmata <[email protected]> Co-authored-by: Emilio López <[email protected]> Co-authored-by: Emilio López <[email protected]>
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
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.
This PR fixes two Foundry test generation bugs reported in #1465:
Target.()-> now generatesaddress(Target).call("")hex"<nul><nul><nul>"-> now generates proper hex likehex"000102"Both fixes include tests that verify the generated code compiles with
forge build.