tendermint/test
Anton Kaliaev c0e7d05b5c
rename tmbase image to tendermint
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.
2017-01-30 11:59:35 +04:00
..
app Fix test/app/dummy_test.sh 2017-01-28 09:11:31 -08:00
docker test: update docker to 1.7.4 2017-01-28 00:12:39 -05:00
net rename tmbase image to tendermint 2017-01-30 11:59:35 +04:00
p2p README for local testnets [ci skip] 2017-01-28 19:25:28 -05:00
persist fix tests 2017-01-12 10:58:44 -05:00
README.md README for local testnets [ci skip] 2017-01-28 19:25:28 -05:00
run_test.sh rebase fixes and BeginBlock(hash,header) 2016-11-16 13:25:13 -05:00
test.sh test: split up test/net/test.sh 2017-01-13 17:20:03 -05:00
test_cover.sh test: circle artifacts 2016-12-19 15:42:39 -05:00
test_libs.sh fix tests 2017-01-13 00:54:01 -05:00

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