Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Guidance for address management when fork testing #872

Open
PaulRBerg opened this issue Apr 20, 2023 · 3 comments
Open

Guidance for address management when fork testing #872

PaulRBerg opened this issue Apr 20, 2023 · 3 comments
Labels
T-enhancement Type: enhance existing docs T-new Type: new docs

Comments

@PaulRBerg
Copy link
Contributor

If you want to fork test a single chain, hard coding your dependencies' addresses in the Solidity tests is a simple and effective approach. However, it doesn't scale well the more chains you want to support for fork testing.

It would be nice if users were given a few tips and tricks about this topic in the Fork Testing tutorial.

For instance, MakerDAO is using JSON configuration files (as per the discussion in foundry-rs/forge-std#268).
@wminshew
Copy link
Contributor

wminshew commented Jun 1, 2023

adding a link to Uniswap's universal router usage as well (base deploy script inherited by other scripts which define the params)

@PaulRBerg
Copy link
Contributor Author

Sharing Matt Solomon's insights from the Foundry Support group:

Screenshot 2023-07-02 at 9 53 59 PM

This was referenced Jul 2, 2023
Closed
Closed
@zerosnacks zerosnacks added T-enhancement Type: enhance existing docs T-new Type: new docs labels Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-enhancement Type: enhance existing docs T-new Type: new docs
Projects
No open projects
Foundry Book
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
4 participants
@PaulRBerg @wminshew @zerosnacks and others