zcash-patched-for-explorer/qa/rpc-tests/README.md

47 lines
1.4 KiB
Markdown
Raw Permalink Normal View History

Regression tests of RPC interface
=================================
2015-05-02 04:25:03 -07:00
### [test_framework/test_framework.py](test_framework/test_framework.py)
Base class for RPC regression tests.
2015-05-02 04:25:03 -07:00
### [test_framework/util.py](test_framework/util.py)
Generally useful functions.
Notes
=====
2015-05-02 04:25:03 -07:00
You can run a single test by calling `qa/pull-tester/rpc-tests.sh <testname>`.
Run all possible tests with `qa/pull-tester/rpc-tests.sh -extended`.
Possible options:
```
2015-05-02 04:25:03 -07:00
-h, --help show this help message and exit
--nocleanup Leave bitcoinds and test.* datadir on exit or error
--noshutdown Don't stop bitcoinds after the test execution
--srcdir=SRCDIR Source directory containing bitcoind/bitcoin-cli (default:
../../src)
--tmpdir=TMPDIR Root directory for datadirs
--tracerpc Print out all RPC calls as they are made
```
If you set the environment variable `PYTHON_DEBUG=1` you will get some debug output (example: `PYTHON_DEBUG=1 qa/pull-tester/rpc-tests.sh wallet`).
A 200-block -regtest blockchain and wallets for four nodes
is created the first time a regression test is run and
is stored in the cache/ directory. Each node has the miner
subsidy from 25 mature blocks (25*10=250 ZEC) in its wallet.
After the first run, the cache/ blockchain and wallets are
copied into a temporary directory and used as the initial
test state.
If you get into a bad state, you should be able
to recover with:
```bash
rm -rf cache
killall zcashd
```