cosmos-sdk/systemtests
mergify[bot] 59019212f0
chore: all modules use v0.53.0 (backport #24614) (#24615)
Co-authored-by: Alex | Interchain Labs <alex@interchainlabs.io>
2025-04-29 19:23:16 +00:00
..
CHANGELOG.md chore: prep systemstest (#24514) 2025-04-14 21:43:50 +00:00
cli.go refactor(client): change flag for unordered tx timeouts (#24561) 2025-04-24 14:22:06 -04:00
genesis_io.go test: add systemtests (#23686) 2025-02-14 17:27:03 -05:00
GETTING_STARTED.md chore: prep systemstest (#24514) 2025-04-14 21:43:50 +00:00
go.mod chore: all modules use v0.53.0 (backport #24614) (#24615) 2025-04-29 19:23:16 +00:00
go.sum chore: all modules use v0.53.0 (backport #24614) (#24615) 2025-04-29 19:23:16 +00:00
io_utils.go test: add systemtests (#23686) 2025-02-14 17:27:03 -05:00
node_utils.go test: add systemtests (#23686) 2025-02-14 17:27:03 -05:00
README.md chore: prep systemstest (#24514) 2025-04-14 21:43:50 +00:00
rest_support.go test: add systemtests (#23686) 2025-02-14 17:27:03 -05:00
rpc_client.go chore: set proto/cosmos/autocli to main (#23725) 2025-02-21 13:39:12 -05:00
system.go feat: add x/protocolpool (#23933) 2025-03-29 19:45:39 +00:00
test_runner.go feat: add x/protocolpool (#23933) 2025-03-29 19:45:39 +00:00
testnet_init.go fix: tx compat (#23850) 2025-03-17 17:51:33 +00:00

System Tests

This package contains the testing framework for black-box system tests. It includes a test runner that sets up a multi-node blockchain locally for use in tests. The framework provides utilities and helpers for easy access and setup in tests.

Components

  • CLI: Command-line interface wrapper for interacting with the chain or keyring
  • Servers: Server instances to run the blockchain environment.
  • Events: Event listeners
  • RPC: Remote Procedure Call setup for communication.

Dependencies

  • testify: Testing toolkit.
  • gjson: JSON parser.
  • sjson: JSON modifier.

Server and client-side operations are executed on the host machine.

Developer

Test strategy

System tests cover the full stack via cli and a running (multi node) network. They are more expensive (in terms of time/ cpu) to run compared to unit or integration tests. Therefore, we focus on the critical path and do not cover every condition.

How to use

Read the GETTING_STARTED guide to get started.

Execute a single test

go test -tags system_test -count=1 -v . --run TestStakeUnstake  -verbose

Test cli parameters

  • -verbose verbose output
  • -wait-time duration - time to wait for chain events (default 30s)
  • -nodes-count int - number of nodes in the cluster (default 4)

Port ranges

With n nodes:

  • 26657 - 26657+n - RPC
  • 1317 - 1317+n - API
  • 9090 - 9090+n - GRPC
  • 16656 - 16656+n - P2P

For example Node 3 listens on 26660 for RPC calls

Resources

Disclaimer

This is based on the system test framework in wasmd built by Confio.