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

History

Wladimir J. van der Laan d612837814 Merge #8149 : Segregated witness rebased `f852813` BIP9 parameters for testnet (Johnson Lau) `070dbc4` --- [SEGWIT] begin: deployment --- (Pieter Wuille) `fdb43df` [qa] Add GetTransactionSigOpCost unit tests (Jonas Nick) `d846e02` [qa] script_tests: witness tests can specify tx amount (Suhas Daftuar) `330b0f3` [qa] p2p segwit tests (Suhas Daftuar) `4f7ff00` [qa] Add rpc test for segwit (Alex Morcos) `66cca79` [qa] Autogeneration support for witness in script_tests (Pieter Wuille) `06d3805` [qa] Add segwit support to script_tests (Pieter Wuille) `00f46cb` [qa] Add transaction tests for segwit (NicolasDorier) `0aa9207` [qa] Witness version 0 signing unit tests (Pieter Wuille) `978e200` --- [SEGWIT] begin: tests --- (Pieter Wuille) `745eb67` [RPC] signrawtransaction can sign P2WSH (NicolasDorier) `f4691ab` [RPC] Add wallet support for witness transactions (using P2SH) (Pieter Wuille) `605e847` BIP143: Signing logic (Pieter Wuille) `9757b57` --- [SEGWIT] begin: wallet --- (Pieter Wuille) `af87a67` Do not use compact blocks when segwit is enabled (Pieter Wuille) `6032f69` Add rewind logic to deal with post-fork software updates (Pieter Wuille) `b7dbeb2` [libconsensus] Script verification API with amounts (Thomas Kerin) `2b1f6f9` BIP141: Other consensus critical limits, and BIP145 (Pieter Wuille) `7c4bf77` [RPC] Return witness data in blockchain RPCs (Johnson Lau) `3dd4102` BIP143: Verification logic (Pieter Wuille) `0ef1dd3` Refactor script validation to observe amounts (Pieter Wuille) `b8a9749` BIP144: Handshake and relay (receiver side) (Pieter Wuille) `8b49040` BIP141: Commitment structure and deployment (Pieter Wuille) `449f9b8` BIP141: Witness program (Pieter Wuille) `7030d9e` BIP144: Serialization, hashes, relay (sender side) (Pieter Wuille) `ecacfd9` --- [SEGWIT] begin: P2P/node/consensus --- (Pieter Wuille)		2016-06-24 18:07:44 +02:00
..
pull-tester	[qa] p2p segwit tests	2016-06-22 15:43:02 +02:00
rpc-tests	[qa] p2p segwit tests	2016-06-22 15:43:02 +02:00
README.md	[doc] Add OS X ZMQ requirement to QA readme	2016-06-24 15:32:48 +08: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

OS X

pip3 install pyzmq

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