The main reason is people usually expect docker image to have the same name as the repo. Plus, tendermint is cleaner than tmbase. tmbase would make sense if we had multiple docker images within tendermint, but we don't. |
||
---|---|---|
.. | ||
app | ||
docker | ||
net | ||
p2p | ||
persist | ||
README.md | ||
run_test.sh | ||
test.sh | ||
test_cover.sh | ||
test_libs.sh |
README.md
Tendermint Tests
The unit tests (ie. the go test
s) can be run with make test
.
The integration tests can be run wtih make test_integrations
.
Running the integrations test will build a docker container with local version of tendermint and run the following tests in docker containers:
- go tests, with --race
- includes test coverage
- app tests
- dummy app over socket
- counter app over socket
- counter app over grpc
- persistence tests
- crash tendermint at each of many predefined points, restart, and ensure it syncs properly with the app
- p2p tests
- start a local dummy app testnet on a docker network (requires docker version 1.10+)
- send a tx on each node and ensure the state root is updated on all of them
- crash and restart nodes one at a time and ensure they can sync back up (via fastsync)
- crash and restart all nodes at once and ensure they can sync back up
If on a release-x.x.x
branch, we also run
go test
for all our dependency libs (test/test_libs.sh)- network_testing - benchmark a mintnet based cloud deploy using netmon