Git subtree of https://github.com/jgarzik/python-bitcoinrpc. Changes to python-bitcoinrpc should be made upstream, and then pulled here using git subtree.
Base class for new regression tests.
Generally useful functions.
Basic code to support p2p connectivity to a bitcoind.
Framework for comparison-tool style, p2p tests.
Utilities for manipulating transaction scripts (originally from python-bitcoinlib)
Implements disk-backed block and tx storage.
Wrapper around OpenSSL EC_Key (originally from python-bitcoinlib)
Helpers for script.py
Helper functions for creating blocks and transactions.
You can run any single test by calling
Or you can run any combination of tests by calling
qa/pull-tester/rpc-tests.py <testname1> <testname2> <testname3> ...
Run the regression test suite with
Run all possible tests with
-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.py 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
P2P test design notes
mininode.pycontains all the definitions for objects that pass over the network (
CTransaction, etc, along with the network-level wrappers for them,
P2P tests have two threads. One thread handles all network communication with the bitcoind(s) being tested (using python's asyncore package); the other implements the test logic.
NodeConnis the class used to connect to a bitcoind. If you implement a callback class that derives from
NodeConnCBand pass that to the
NodeConnobject, your code will receive the appropriate callbacks when events of interest arrive. NOTE: be sure to call
self.create_callback_map()in your derived classes'
__init__function, so that the correct mappings are set up between p2p messages and your callback functions.
You can pass the same handler to multiple
NodeConn's if you like, or pass different ones to each -- whatever makes the most sense for your test.
NodeConnobjects are created to start the networking thread. (Continue with the test logic in your existing thread.)
RPC calls are available in p2p tests.
Can be used to write free-form tests, where specific p2p-protocol behavior is tested. Examples:
Testing framework for writing tests that compare the block/tx acceptance behavior of a bitcoind against 1 or more other bitcoind instances, or against known outcomes, or both.
num_nodesvariable (defined in
ComparisonTestFramework) to start up 1 or more nodes. If using 1 node, then
--testbinarycan be used as a command line option to change the bitcoind binary used by the test. If using 2 or more nodes, then
--refbinarycan be optionally used to change the bitcoind that will be used on nodes 2 and up.
Implement a (generator) function called
- a list of
[object, outcome, hash]entries
CTransaction's are tested for acceptance.
CBlockHeaders can be used so that the test runner can deliver complete headers-chains when requested from the bitcoind, to allow writing tests where blocks can be delivered out of order but still processed by headers-first bitcoind's.
False, the tip is compared with the expected tip -- either the block passed in, or the hash specified as the optional 3rd entry. If
Noneis specified, then the test will compare all the bitcoind's being tested to see if they all agree on what the best tip is.
hashis the block hash of the tip to compare against. Optional to specify; if left out then the hash of the block passed in will be used as the expected tip. This allows for specifying an expected tip while testing the handling of either invalid blocks or blocks delivered out of order, which complete a longer chain.
False, then all blocks are inv'ed together, and the test runner waits until the node receives the last one, and tests only the last block for tip acceptance using the outcome and specified tip. If
True, then each block is tested in sequence and synced (this is slower when processing many blocks).
True/False. Analogous to
sync_every_block, except if the outcome on the last tx is "None", then the contents of the entire mempool are compared across all bitcoind connections. If
False, then only the last tx's acceptance is tested against the given outcome.
- a list of
For examples of tests written in this framework, see