status-go/t/destructive
Adrià Cidre 359b3621e9 [#797] Simplify node.Manager public api and rename it to StatusNode
- [x] [#797] : Remove unused methods PopulateStaticPeers, ReconnectStaticPeers, removeStaticPeers, removePeer
- [x] [#797] : Rename node.Manager to node. StatusNode and simplify its public api
- [x] [#797] : Rename all references to nodeManager to statusNode
2018-04-05 16:47:27 +02:00
..
README.md Add destructive tests (#646) 2018-02-19 17:32:58 +02:00
peers_test.go [#797] Simplify node.Manager public api and rename it to StatusNode 2018-04-05 16:47:27 +02:00
sync_test.go [#797] Simplify node.Manager public api and rename it to StatusNode 2018-04-05 16:47:27 +02: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"