From 2f5606358014f6cc3c0c9c21c4fcc609fe7b8a03 Mon Sep 17 00:00:00 2001 From: Pasta Date: Fri, 12 Jul 2019 11:37:59 -0500 Subject: [PATCH] dashify test/README.md Signed-off-by: Pasta --- test/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/test/README.md b/test/README.md index f0d4715f51..074d98c80f 100644 --- a/test/README.md +++ b/test/README.md @@ -103,7 +103,7 @@ functional test is run and is stored in test/cache. This speeds up test startup times since new blockchains don't need to be generated for each test. However, the cache may get into a bad state, in which case tests will fail. If this happens, remove the cache directory (and make -sure bitcoind processes are stopped as above): +sure dashd processes are stopped as above): ```bash rm -rf cache @@ -120,7 +120,7 @@ default: - when run directly, *all* logs are written to `test_framework.log` and INFO level and above are output to the console. - when run on Travis, no logs are output to the console. However, if a test - fails, the `test_framework.log` and bitcoind `debug.log`s will all be dumped + fails, the `test_framework.log` and dashd `debug.log`s will all be dumped to the console to help troubleshooting. To change the level of logs output to the console, use the `-l` command line @@ -153,7 +153,7 @@ import pdb; pdb.set_trace() ``` anywhere in the test. You will then be able to inspect variables, as well as -call methods that interact with the bitcoind nodes-under-test. +call methods that interact with the dashd nodes-under-test. ### Util tests