mirror of https://github.com/dashpay/dash.git synced 2024-12-26 12:32:48 +01:00

History

Wladimir J. van der Laan 0e935865b9 Merge pull request #6871 `63b5840` Fix usage of local python-bitcoinlib (Peter Todd) `16a2f93` Fix incorrect locking of mempool during RBF replacement (Peter Todd) `97203f5` Port test to rpc-test framework (Suhas Daftuar) `20367d8` Add test for max replacement limit (Suhas Daftuar) `73d9040` Improve RBF replacement criteria (Suhas Daftuar) `b272ecf` Reject replacements that add new unconfirmed inputs (Peter Todd) `fc8c19a` Prevent low feerate txs from (directly) replacing high feerate txs (Peter Todd) `0137e6f` Add tests for transaction replacement (Peter Todd) `5891f87` Add opt-in full-RBF to mempool (Peter Todd)		2015-11-27 13:20:39 +01:00
..
pull-tester	Merge pull request #6871	2015-11-27 13:20:39 +01:00
replace-by-fee	Fix usage of local python-bitcoinlib	2015-11-20 16:23:01 -05:00
rpc-tests	Merge pull request #6871	2015-11-27 13:20:39 +01:00
README.md	[qa] Extend README.md	2015-11-18 11:59:12 +01: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.

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

Possible options:

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