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
At Strangelove we have done quite a bit work lately on building ibctest. The purpose of this framework is to:
Provide a conformance test for IBC that enables us to understand which chains have which IBC features and to ensure that new releases are compatible.
Provide a library of reusable components that allow easy spin up of different primitives in the the IBC environment such as relayers and other chains.
The core libs have also been used to do fun stuff like reproduce a juno halt and help test the restart. They amount to an extremely powerful network simulation tool for cosmos sdk based applications that can be used as an e2e testing framework. The only API the test framework relies on is the ones exposed by the binaries. This method allows for testing of features such as upgrade handlers and state sync in a CI environment. They also allow for networks to be started from predefined genesis files with rich state.
Currently IBC has been focused on feature development focused on IBC usecases however the cosmos chain package can easily be expanded to meet the sdk's needs allowing for a lot code reuse.
We have spent the last 5 months building out the core functionality and building test cases and the repo is now ready for more collaborators and usecases. Strangelove engineers are currently working with multiple teams to help them implement testing in IBC test and are building out more examples. We would love to help the SDK with the e2e work we have done here.
The text was updated successfully, but these errors were encountered:
@jackzampolin any chance we can get a demo of ibc test at work? we are looking at e2e and testing in general and would like to see ibc test and how you recommend developing against it.
starship did the integration and it helping us with redesigning a few things around e2e simulations and different form of tests. IBCtest has a dependency on us as well. We dont want to have circular dependencies
At Strangelove we have done quite a bit work lately on building
ibctest
. The purpose of this framework is to:The core libs have also been used to do fun stuff like reproduce a juno halt and help test the restart. They amount to an extremely powerful network simulation tool for cosmos sdk based applications that can be used as an e2e testing framework. The only API the test framework relies on is the ones exposed by the binaries. This method allows for testing of features such as upgrade handlers and state sync in a CI environment. They also allow for networks to be started from predefined genesis files with rich state.
Currently IBC has been focused on feature development focused on IBC usecases however the
cosmos
chain package can easily be expanded to meet the sdk's needs allowing for a lot code reuse.We have spent the last 5 months building out the core functionality and building test cases and the repo is now ready for more collaborators and usecases. Strangelove engineers are currently working with multiple teams to help them implement testing in IBC test and are building out more examples. We would love to help the SDK with the e2e work we have done here.
The text was updated successfully, but these errors were encountered: