README
¶
Getting started with a new system test
Overview
The systemtests suite is an end-to-end test suite that runs the evmd process and sends RPC requests from separate Ethereum/Cosmos clients. The systemtests for cosmos/evm use the cosmossdk.io/systemtests package by default. For more details, please refer to https://github.com/cosmos/cosmos-sdk/tree/main/tests/systemtests.
Preparation
Build a new binary from current branch and copy it to the tests/systemtests/binaries folder by running system tests.
make test-system
Or via manual steps
make build
mkdir -= ./tests/systemtests/binaries
cp ./build/evmd ./tests/systemtests/binaries
cp ./build/evmd ./tests/systemtests/binaries/v0.4
Run Individual test
Each scenario now has its own Test… wrapper in main_test.go, so you can target a specific flow directly. For example, to exercise the mempool ordering suite:
cd tests/systemtests
go test -failfast -mod=readonly -tags=system_test ./... -run TestMempoolTxsOrdering \
--verbose --binary evmd --block-time 3s --chain-id local-4221
Mempool scenarios:
| Test name | Description |
|---|---|
TestMempoolTxsOrdering |
Ordering of pending transactions across nodes |
TestMempoolTxsReplacement |
Replacement behaviour for EVM transactions |
TestMempoolTxsReplacementWithCosmosTx |
Replacement when Cosmos transactions are present |
TestMempoolMixedTxsReplacementEVMAndCosmos |
Mixed Cosmos/EVM replacement coverage |
TestMempoolTxRebroadcasting |
Rebroadcasting and nonce-gap handling |
TestMempoolCosmosTxsCompatibility |
Cosmos-only transactions interacting with the mempool |
EIP-712 scenarios:
| Test name | Description |
|---|---|
TestEIP712BankSend |
Single transfer signed via EIP-712 |
TestEIP712BankSendWithBalanceCheck |
Transfer plus balance assertions |
TestEIP712MultipleBankSends |
Sequential transfers with nonce management |
Account abstraction:
| Test name | Description |
|---|---|
TestAccountAbstractionEIP7702 |
Account abstraction (EIP-7702) flow |
Chain lifecycle:
| Test name | Description |
|---|---|
TestChainUpgrade |
End-to-end upgrade handling |
ℹ️ The shared system test suite keeps a single chain alive across multiple tests when the node arguments are identical. Running several tests back-to-back therefore re-uses the same process unless a scenario explicitly changes the node configuration.
Run all tests
make test
Updating Node's Configuration
New in systemtests v1.4.0, you can now update the config.toml of the nodes. To do so, the system under test should be set up like so:
s := systemtest.Sut
s.ResetChain(t)
s.SetupChain("--config-changes=consensus.timeout_commit=10s")
Directories