364f88efd9
This change will greatly simplify writing unit tests when a node is required but data persistence is irrelevant. I also Introduced some refactoring and unit tests for `StatusNode`. |
||
---|---|---|
.. | ||
README.md | ||
peers_test.go | ||
sync_test.go | ||
testcontroller.go |
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"