Kevacoin source tree
 
 
 
 
 
 
Pieter Wuille 66ed450d77
Merge #7935: Versionbits: GBT support
9 years ago
..
test_framework Fix interrupted HTTP RPC connection workaround for Python 3.5+ 9 years ago
.gitignore Python-based regression tests 11 years ago
README.md test: remove necessity to call create_callback_map 9 years ago
abandonconflict.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
bip9-softforks.py Merge #7935: Versionbits: GBT support 9 years ago
bip65-cltv-p2p.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
bip65-cltv.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
bip68-112-113-p2p.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
bip68-sequence.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
bipdersig-p2p.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
bipdersig.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
blockchain.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
create_cache.py [qa] pull-tester: Run rpc test in parallel 9 years ago
decodescript.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
disablewallet.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
forknotify.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
fundrawtransaction.py [rpc] fundrawtransaction feeRate: Use BTC/kB 9 years ago
getblocktemplate_longpoll.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
getblocktemplate_proposals.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
getchaintips.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
httpbasics.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
importprunedfunds.py [qa] Reduce node count for some tests 9 years ago
invalidateblock.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
invalidblockrequest.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
invalidtxrequest.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
keypool.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
listtransactions.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
maxblocksinflight.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
maxuploadtarget.py [qa] Reduce node count for some tests 9 years ago
mempool_limit.py [qa] Reduce node count for some tests 9 years ago
mempool_packages.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
mempool_reorg.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
mempool_resurrect_test.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
mempool_spendcoinbase.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
merkle_blocks.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
multi_rpc.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
nodehandling.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
p2p-acceptblock.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
p2p-feefilter.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
p2p-fullblocktest.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
p2p-mempool.py Add RPC test for the p2p mempool command in conjunction with disabled bloomfilters 9 years ago
p2p-versionbits-warning.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
prioritise_transaction.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
proxy_test.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
pruning.py Merge #8056: [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
rawtransactions.py Merge #7957: [RPC][Bitcoin-TX] Add support for sequence number 9 years ago
receivedby.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
reindex.py Merge #8056: [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
replace-by-fee.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
rest.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
rpcbind_test.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
sendheaders.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
signmessages.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
signrawtransactions.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
smartfees.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
txn_clone.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
txn_doublespend.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
wallet.py Merge #8056: [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
walletbackup.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
zapwallettxes.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago
zmq_test.py [qa] Remove hardcoded "4 nodes" from test_framework 9 years ago

README.md

Regression tests

test_framework/authproxy.py

Taken from the python-bitcoinrpc repository.

test_framework/test_framework.py

Base class for new regression tests.

test_framework/util.py

Generally useful functions.

test_framework/mininode.py

Basic code to support p2p connectivity to a bitcoind.

test_framework/comptool.py

Framework for comparison-tool style, p2p tests.

test_framework/script.py

Utilities for manipulating transaction scripts (originally from python-bitcoinlib)

test_framework/blockstore.py

Implements disk-backed block and tx storage.

test_framework/key.py

Wrapper around OpenSSL EC_Key (originally from python-bitcoinlib)

test_framework/bignum.py

Helpers for script.py

test_framework/blocktools.py

Helper functions for creating blocks and transactions.

P2P test design notes

Mininode

  • mininode.py contains all the definitions for objects that pass over the network (CBlock, CTransaction, etc, along with the network-level wrappers for them, msg_block, msg_tx, etc).

  • 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.

  • NodeConn is the class used to connect to a bitcoind. If you implement a callback class that derives from NodeConnCB and pass that to the NodeConn object, your code will receive the appropriate callbacks when events of interest arrive.

  • 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.

  • Call NetworkThread.start() after all NodeConn objects 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: p2p-accept-block.py, maxblocksinflight.py.

Comptool

  • 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.

  • Set the num_nodes variable (defined in ComparisonTestFramework) to start up 1 or more nodes. If using 1 node, then --testbinary can be used as a command line option to change the bitcoind binary used by the test. If using 2 or more nodes, then --refbinary can be optionally used to change the bitcoind that will be used on nodes 2 and up.

  • Implement a (generator) function called get_tests() which yields TestInstances. Each TestInstance consists of:

    • a list of [object, outcome, hash] entries
      • object is a CBlock, CTransaction, or CBlockHeader. CBlock's and 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.
      • outcome is True, False, or None. If True or False, the tip is compared with the expected tip -- either the block passed in, or the hash specified as the optional 3rd entry. If None is specified, then the test will compare all the bitcoind's being tested to see if they all agree on what the best tip is.
      • hash is 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.
    • sync_every_block: True/False. If 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).
    • sync_every_transaction: 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 True or False, then only the last tx's acceptance is tested against the given outcome.
  • For examples of tests written in this framework, see invalidblockrequest.py and p2p-fullblocktest.py.