tendermint/test
Ethan Buchman fb9d3842e4 test: p2p.seeds and p2p.pex 2017-05-05 01:28:43 -04:00
..
app test: jq .result[1] -> jq .result 2017-04-28 22:31:30 -04:00
docker postmerge 2017-04-21 18:09:47 -04:00
net postmerge 2017-04-21 18:09:47 -04:00
p2p test: p2p.seeds and p2p.pex 2017-05-05 01:28:43 -04:00
persist test: jq .result[1] -> jq .result 2017-04-28 22:31:30 -04:00
utils postmerge 2017-04-21 18:09:47 -04:00
README.md postmerge 2017-04-21 18:09:47 -04:00
run_test.sh postmerge 2017-04-21 18:09:47 -04:00
test.sh postmerge 2017-04-21 18:09:47 -04:00
test_cover.sh postmerge 2017-04-21 18:09:47 -04:00
test_libs.sh test: test_libs all use Makefile 2017-04-25 18:35:22 -04: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