History

Alexander Block 28a6007a40 Prepare DIP3 for testnet and reuse DIP3 deployment for autoix deployment (#2389 ) * Add BIP9 parameters for DIP3 deployment on testnet * Remove autoix BIP9 deployment and reuse DIP3 deployment * Add BIP9CheckMasternodesUpgraded to chain params This controls if miners should check for upgraded masternodes first before adding BIP9 bits to the block version. This only makes sense in network where masternodes are up and running before BIP9 activation, which is not necessarely the case in regtest and devnet. Also refactor ComputeBlockVersion to use fCheckMasternodesUpgraded instead of the inverse fAssumeMasternodeIsUpgraded. It is set to false by default and only set to true in CreateNewBlock. * Check for upgraded masternodes for DIP3 activation (only mainnet and testnet) * Bump PROTOCOL_VERSION and DMN_PROTO_VERSION We probably have nodes with 70211 already running on testnet.		2018-10-26 19:42:52 +03:00
..
pull-tester	M-of-N-like sporks (#2288 )	2018-09-30 20:01:33 +03:00
rpc-tests	Prepare DIP3 for testnet and reuse DIP3 deployment for autoix deployment (#2389 )	2018-10-26 19:42:52 +03:00
README.md	Merge #8625 : [doc] - clarify statement about parallel jobs in rpc-tests.py	2018-01-09 14:04:21 +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 Dash Core 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. To specify how many jobs to run, 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 dashds and test.* datadir on exit or error
  --noshutdown          Don't stop dashds after the test execution
  --srcdir=SRCDIR       Source directory containing dashd/dash-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*500=12500 DASH) 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 dashd

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.