-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
feat: add e2e test suite with evm contracts deployments #9
base: main
Are you sure you want to change the base?
Conversation
0efffb2
to
3a745be
Compare
run-latest.json |
the reason I had to pull in the FastTransferGateway contract and it dependencies here is because we dont have access to the test deployer private key to use as auth for deploying the contract using the generated go bindings. @thal0x please let me know if you have ideas of a better way to do this |
abbaa65
to
56a3df2
Compare
db74327
to
ad21be6
Compare
1264d5e
to
9bf9d65
Compare
6e4ea2f
to
5735c31
Compare
v1.9.4
2569b47
to
5fc418a
Compare
1a73bec
to
5e9379f
Compare
{ | ||
// TODO: Save this image to skip repository and import it from there instead | ||
Repository: "ghcr.io/cosmos/ibc-go-simd", // FOR LOCAL IMAGE USE: Docker Image Name | ||
Version: "poc-solidity-ibc-eureka", // FOR LOCAL IMAGE USE: Docker Image Tag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it make sense to use a different docker image here?
This PR creates an E2E test suite framework and deploys the following resources/contracts:
The corresponding resources for the Cosmos chain and deployment of the solver in a test container to simulate user transfer and add test assertions, will be added in followup PRs