aboutsummaryrefslogtreecommitdiff
path: root/test/functional
diff options
context:
space:
mode:
authorAnthony Towns <aj@erisian.com.au>2017-11-30 19:51:32 +1000
committerAnthony Towns <aj@erisian.com.au>2017-11-30 19:59:39 +1000
commit7250b4e5630ec6e440652855876ba83b0365a15a (patch)
treeb82a094bd32bbdd68ded7047ce952e5aad1b4042 /test/functional
parent82b2712a6677f489b8a9a50f9ca739418e18fcc9 (diff)
[tests] README.md nit fixes
Diffstat (limited to 'test/functional')
-rw-r--r--test/functional/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/test/functional/README.md b/test/functional/README.md
index f352837858..8d2cd02345 100644
--- a/test/functional/README.md
+++ b/test/functional/README.md
@@ -39,7 +39,7 @@ don't have test cases for.
- `wallet` for tests for wallet features, eg `wallet_keypool.py`
- use an underscore to separate words
- exception: for tests for specific RPCs or command line options which don't include underscores, name the test after the exact RPC or argument name, eg `rpc_decodescript.py`, not `rpc_decode_script.py`
-- Don't use the redundant work `test` in the name, eg `interface_zmq.py`, not `interface_zmq_test.py`
+- Don't use the redundant word `test` in the name, eg `interface_zmq.py`, not `interface_zmq_test.py`
#### General test-writing advice
@@ -87,7 +87,7 @@ start the networking thread. (Continue with the test logic in your existing
thread.)
- Can be used to write tests where specific P2P protocol behavior is tested.
-Examples tests are `p2p-accept-block.py`, `p2p-compactblocks.py`.
+Examples tests are `p2p-acceptblock.py`, `p2p-compactblocks.py`.
#### Comptool