interchaintest

Table Of Contents

• Branch Versioning
• Use Cases:
  • Importing as a Module
    • Chain Integration and GitHub CI
    • Running Conformance Tests
  • Running as a Binary
    • Building Binary
    • Running Conformance Tests - Suite of built-in tests that test high-level IBC compatibility
• Write Custom Tests
• Environment Variable Options
• Retaining Data on Failed Tests

Maintained Branches

Depreciated Branches

These are branches that we no longer actively update or maintain but may be of use if a chain is running older versions of the Cosmos SDK or IBC Go. Please see the Backport Policy below.

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.

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