interchaintest
IBC tester
A framework for testing blockchain functionality and interoperability between chains, primarily with the Inter-Blockchain Communication (IBC) protocol.
e2e testing framework for the interchain
189 stars
8 watching
122 forks
Language: Go
last commit: 9 days ago
Linked from 1 awesome list
cosmosgoibctesting
Related projects:
Repository | Description | Stars |
---|---|---|
batate/shouldi | Provides Elixir testing libraries with nested contexts and improved test naming conventions | 135 |
steinfletcher/apitest | A simple and extensible library for behavioural testing of Go web applications. | 796 |
emicklei/forest | A package for writing integration tests in Go using REST API testing | 123 |
antonboom/testifylint | A tool that checks the usage of the testify testing framework in Go programs | 101 |
nethereum/testchains | Pre-configured environments for fast and secure development of blockchain projects with PoA consensus | 29 |
go-bdd/gobdd | A BDD testing framework for Go that uses the gherkin syntax and aims to provide more flexibility and customization than existing alternatives. | 115 |
orijtech/cosmosloadtester | A tool for simulating high load on blockchain-based applications to test their performance under heavy traffic | 5 |
jemc/qmlspec | An integrated QML testing framework with extensibility and customizability features. | 6 |
bscotch/olympus | A testing framework designed specifically for GameMaker projects with features such as test result recording and recovery. | 16 |
earthboundkid/be | A testing library with generic assertions and helpers for Go tests | 102 |
antonmi/espec | A BDD testing framework for Elixir | 808 |
matryer/is | A testing framework for Go with simple and readable API | 1,782 |
cleanunicorn/karl | Monitors smart contracts for security vulnerabilities on blockchain networks | 315 |
jimrobinson/kvbench | A benchmarking tool to evaluate the performance of key/value stores by generating and consuming data in parallel. | 26 |
sashamelentyev/usestdlibvars | Detects potential misuse of standard library variables in Go code | 43 |