Add Foundry for Manual Integration Testing #208
No reviewers
Labels
No Label
bug
critical
duplicate
enhancement
epic
help wanted
in progress
invalid
low priority
question
rebase
v1
v5
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/go-ethereum#208
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/gh-208-add-foundry"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR imbeds foundry into
vulcanize-geth
. Currently there is only one project under thefoundry/projects
directory. In the future, developers can add smart contract testing using foundry. Or they can simply leverage the local network created using the current project.This is great! Directions were easy to follow, and based on my limited test run it feels a lot faster than dapptools.
If you can go ahead and fix that linting error, which is left over from me, that'd be nice. Just need to remove
makeLightNode
func in cmd/geth/config.go.Also we should target this PR to this branch: https://github.com/vulcanize/go-ethereum/tree/v1.10.16-statediff-v3
General workflow for merges and releases goes:
statediff
)Which root versioned branch we maintain parity with on
statediff
is whatever major version we consider canonical at the time.@i-norden - Thanks for the insight, I made the updates. Going to let CI/CD run and then hopefully we can merge :D
@i-norden - Can I get a final sign off please
LGTM, thanks!