You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These would be basic tests where one side has a docker image of wasmd running and the other side is ibc-go's simd. We would be able to test compatibility of changes with smart contracts. This testing package will be useful for testing adr8 changes as well
Problem Definition
We don't have any frame work to test smart contract handshakes, applications, serialization, and callbacks.
Proposal
I've implemented a test between wasmd and ibc-go before. The idea is to have one of the chains run a vanilla wasmd docker image and simply test handshakes and responses. This wouldn't require any major modifications to the current testing package.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged/assigned
The text was updated successfully, but these errors were encountered:
I can see this helping us in many ways. In this repository, that's going to help us test against IBC code written in CW and in projects that use CW to do i recruit, what you're describing here sounds totally fantastic and highly applicable.
Summary
These would be basic tests where one side has a docker image of wasmd running and the other side is ibc-go's simd. We would be able to test compatibility of changes with smart contracts. This testing package will be useful for testing adr8 changes as well
Problem Definition
We don't have any frame work to test smart contract handshakes, applications, serialization, and callbacks.
Proposal
I've implemented a test between wasmd and ibc-go before. The idea is to have one of the chains run a vanilla wasmd docker image and simply test handshakes and responses. This wouldn't require any major modifications to the current testing package.
For Admin Use
The text was updated successfully, but these errors were encountered: