9c528d5061
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: aljo242 <alex@interchainlabs.io> |
||
|---|---|---|
| .. | ||
| testdata | ||
| .gitignore | ||
| account_test.go | ||
| auth_test.go | ||
| authz_test.go | ||
| bank_test.go | ||
| circuit_test.go | ||
| cometbft_client_test.go | ||
| distribution_test.go | ||
| export_test.go | ||
| fraud_test.go | ||
| getting_started.md | ||
| go.mod | ||
| go.sum | ||
| gov_test.go | ||
| group_test.go | ||
| grpc_test.go | ||
| main_test.go | ||
| Makefile | ||
| mint_test.go | ||
| README.md | ||
| snapshots_test.go | ||
| staking_test.go | ||
| tx_test.go | ||
| unordered_tx_test.go | ||
| upgrade_test.go | ||
System tests
Go black box tests that setup and interact with a local blockchain. The system test framework works with the compiled binary of the chain artifact only. To get up to speed, checkout the getting started guide.
Beside the Go tests and testdata files, this directory can contain the following directories:
binaries- cache for binarytestnet- node files
Please make sure to not add or push them to git.
Execution
Build a new binary from current branch and copy it to the tests/systemtests/binaries folder by running system tests.
In project root:
make test-system
Or via manual steps
make build
mkdir -p ./tests/systemtests/binaries
cp ./build/simd ./tests/systemtests/binaries/
Manual test run
go test -v -mod=readonly -failfast -tags='system_test' --run TestStakeUnstake ./... --verbose
Working with macOS
Most tests should function seamlessly. However, the file upgrade_test.go includes a build annotation for Linux only.
For the system upgrade test, an older version of the binary is utilized to perform a chain upgrade. This artifact is retrieved from a Docker container built for Linux.
To circumvent this limitation locally:
- Checkout and build the older version of the artifact from a specific tag for your OS.
- Place the built artifact into the
binariesfolder. - Ensure that the filename, including the version, is correct.
With the cached artifact in place, the test will use this file instead of attempting to pull it from Docker.