status-go/t/destructive
Pedro Pombeiro 6cdea4ef97
Update codebase to leverage Whisper v6 (#703)
* Update project to use Whisper v6. Part of #638

* Revert "Add patch to downgrade usage of Whisper v6 to v5 in some geth 1.8.1 vendor files. Part of #665" - this reverts commit 6aefb4c8fd02dbcfffac6b69e8bb22b13ef86b6b.

* Enable light mode on Whisper v6 for non-mail servers. Part of #638

* Fix race condition in whisperv6/peer.go. Part of #665 (PR already accepted upstream for 1.8.2)

* Update bootnode addresses in staticnodes.json. Part of #638

* Add `shh.lightclient` flag and tests for bloom filter setting logic. Part of #638

* Move MakeTestNodeConfig to utils. Part of #638

* Reduce PoW in `whisper_jail_test.go` to fix flaky test. Part of #638
2018-03-02 10:25:30 +01:00
..
README.md Add destructive tests (#646) 2018-02-19 17:32:58 +02:00
peers_test.go Update codebase to leverage Whisper v6 (#703) 2018-03-02 10:25:30 +01:00
sync_test.go Update codebase to leverage Whisper v6 (#703) 2018-03-02 10:25:30 +01:00
testcontroller.go Add destructive tests (#646) 2018-02-19 17:32:58 +02:00

README.md

Destructive tests

The goal is to test behaviour of status-go and underlying protocols under erroneous conditions, such as losing network connection.

Test could cause unpredictable side effects, such as change of network configuration. I don't advice to run them locally on your machine, just use docker container. Also note that tests are relying on real data, such as number of peers.

make docker-test ARGS="./t/destructive/ -v -network=3"