6bdb474dc9
Some code and test cases stolen from Bryan Bishop <bryan@ledgerx.com> (pull #5524). |
||
---|---|---|
.. | ||
test_framework | ||
.gitignore | ||
bipdersig-p2p.py | ||
bipdersig.py | ||
decodescript.py | ||
forknotify.py | ||
fundrawtransaction.py | ||
getblocktemplate_longpoll.py | ||
getblocktemplate_proposals.py | ||
getchaintips.py | ||
httpbasics.py | ||
invalidateblock.py | ||
invalidblockrequest.py | ||
keypool.py | ||
listtransactions.py | ||
maxblocksinflight.py | ||
mempool_coinbase_spends.py | ||
mempool_resurrect_test.py | ||
mempool_spendcoinbase.py | ||
merkle_blocks.py | ||
nodehandling.py | ||
p2p-acceptblock.py | ||
proxy_test.py | ||
pruning.py | ||
rawtransactions.py | ||
README.md | ||
receivedby.py | ||
reindex.py | ||
rest.py | ||
rpcbind_test.py | ||
script_test.py | ||
signrawtransactions.py | ||
smartfees.py | ||
txn_clone.py | ||
txn_doublespend.py | ||
wallet.py | ||
walletbackup.py | ||
zapwallettxes.py |
Regression tests of RPC interface
python-bitcoinrpc
Git subtree of https://github.com/jgarzik/python-bitcoinrpc. Changes to python-bitcoinrpc should be made upstream, and then pulled here using git subtree.
test_framework/test_framework.py
Base class for new regression tests.
test_framework/util.py
Generally useful functions.
Notes
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:
-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 25 mature blocks (25*50=1250 BTC) 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:
rm -rf cache
killall bitcoind