You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tom Harding
defd2d55b7
|
10 years ago | |
|---|---|---|
| .. | ||
| python-bitcoinrpc | ||
| .gitignore | ||
| README.md | 10 years ago | |
| bipdersig.py | 10 years ago | |
| conflictedbalance.sh | 10 years ago | |
| forknotify.py | 10 years ago | |
| getblocktemplate_longpoll.py | 10 years ago | |
| getblocktemplate_proposals.py | 10 years ago | |
| getchaintips.py | 10 years ago | |
| httpbasics.py | 10 years ago | |
| invalidateblock.py | 10 years ago | |
| keypool.py | ||
| listtransactions.py | 10 years ago | |
| mempool_coinbase_spends.py | 10 years ago | |
| mempool_resurrect_test.py | 10 years ago | |
| mempool_spendcoinbase.py | 10 years ago | |
| netutil.py | ||
| receivedby.py | 10 years ago | |
| rest.py | 10 years ago | |
| rpcbind_test.py | ||
| send.sh | ||
| smartfees.py | 10 years ago | |
| test_framework.py | 10 years ago | |
| txn_doublespend.py | 10 years ago | |
| util.py | 10 years ago | |
| util.sh | ||
| wallet.py | 10 years ago | |
| walletbackup.py | 10 years ago | |
| zapwallettxes.py | 10 years ago | |
README.md
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.py
Base class for 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