interchaintest

-- Features --

• Built-in suite of conformance tests to test high-level IBC compatibility between chain sets
• Easily construct customized tests in highly configurable environments
• Deployable as CI tests in production workflows

Maintained Branches

Backport Policy:

Strangelove maintains n and n - 1 branches of interchaintest, n being current main.

We strive to keep interchaintest inline with the latest from the ibc-go and cosmos sdk teams. Once an alpha versions of the next major ibc-go version is released, we will discontinue n - 1 and branch off a new n.

Recommendation: Even if your chain uses an older version of ibc-go, try importing from main. This should work unless you are decoding transactions that require a specific ibc-go version.

If there is a feature you would like backported to an older branch, make an issue! We are happy to work with you.

Table Of Contents

• Building Binary
• Usage:
  • Running Conformance Tests - Suite of built-in tests that test high-level IBC compatibility
  • Write Custom Tests
• Retaining Data on Failed Tests
• Deploy as GitHub CI Tests

Building Binary

While it is not necessary to build the binary, sometimes it can be more convenient, specifically when running conformance test with custom chain sets.

Building binary:

git clone https://github.com/agoric-labs/interchaintest.git
cd interchaintest
make interchaintest

This places the binary in interchaintest/.bin/interchaintest

Note that this is not in your Go path.

Contributing

Contributing is encouraged.

Please read the logging style guide.

Trophies

Significant bugs that were more easily fixed with interchaintest:

• Juno network halt reproduction
• Juno network halt fix confirmation