dash/qa/rpc-tests
Gavin Andresen cb4bdd18a7 Have pull-tester run the listtransactions.py regression test
This should show how to run a python-based regression test
successfully in the pull-tester environment.
2014-04-02 19:59:17 -04:00
..
python-bitcoinrpc Fix regression tests 2014-03-24 19:14:51 +01:00
.gitignore Python-based regression tests 2014-02-28 15:24:31 -05:00
conflictedbalance.sh Add licenses for tests and test data 2014-03-18 10:20:55 +01:00
listtransactions.py Fix regression tests 2014-03-24 19:14:51 +01:00
README.md Python-based regression tests 2014-02-28 15:24:31 -05:00
send.sh Add licenses for tests and test data 2014-03-18 10:20:55 +01:00
skeleton.py Fix regression tests 2014-03-24 19:14:51 +01:00
txnmall.sh Add licenses for tests and test data 2014-03-18 10:20:55 +01:00
util.py Have pull-tester run the listtransactions.py regression test 2014-04-02 19:59:17 -04:00
util.sh Add licenses for tests and test data 2014-03-18 10:20:55 +01:00
wallet.sh Add licenses for tests and test data 2014-03-18 10:20:55 +01:00
walletbackup.sh Add licenses for tests and test data 2014-03-18 10:20:55 +01:00

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

skeleton.py : Copy this to create new regression tests.

listtransactions.py : Tests for the listtransactions RPC call

util.py : generally useful functions

Bash-based tests, to be ported to Python:

wallet.sh : Exercise wallet send/receive code. walletbackup.sh : Exercise wallet backup / dump / import txnmall.sh : Test proper accounting of malleable transactions conflictedbalance.sh : More testing of malleable transaction handling

Notes

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 their 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