History

Pieter Wuille 7ce9ac5c83 Merge #7292 : [RPC] Expose ancestor/descendant information over RPC `176e19b` Mention new RPC's in release notes (Suhas Daftuar) `7f6eda8` Add ancestor statistics to mempool entry RPC output (Suhas Daftuar) `a9b8390` Add test coverage for new RPC calls (Suhas Daftuar) `b09b813` Add getmempoolentry RPC call (Suhas Daftuar) `0dfd869` Add getmempooldescendants RPC call (Suhas Daftuar) `8f7b5dc` Add getmempoolancestors RPC call (Suhas Daftuar) `5ec0cde` Refactor logic for converting mempool entries to JSON (Suhas Daftuar)		2016-06-09 16:32:37 +02:00
..
pull-tester	[qa] Add option --portseed to test_framework	2016-05-09 19:56:24 +02:00
rpc-tests	Merge #7292 : [RPC] Expose ancestor/descendant information over RPC	2016-06-09 16:32:37 +02:00
README.md	[qa] pull-tester: Run rpc test in parallel	2016-05-09 19:56:16 +02:00

README.md

The pull-tester folder contains a script to call multiple tests from the rpc-tests folder.

Every pull request to the bitcoin repository is built and run through the regression test suite. You can also run all or only individual tests locally.

Test dependencies

Before running the tests, the following must be installed.

Unix

The python3-zmq library is required. On Ubuntu or Debian it can be installed via:

sudo apt-get install python3-zmq

Running tests

You can run any single test by calling

qa/pull-tester/rpc-tests.py <testname>

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

qa/pull-tester/rpc-tests.py

Run all possible tests with

qa/pull-tester/rpc-tests.py -extended

By default, tests will be run in parallel if you want to specify how many tests should be run in parallel, append -paralell=n (default n=4).

If you want to create a basic coverage report for the rpc test suite, append --coverage.

Possible options, which apply to each individual test run:

  -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
  --coveragedir=COVERAGEDIR
                        Write tested RPC commands into this directory

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

Writing tests

You are encouraged to write tests for new or existing features. Further information about the test framework and individual rpc tests is found in qa/rpc-tests.