History

Alexander Block 7ee31cbd65 Speed up integration tests with masternodes (#2642 ) * Implement copy_datadir to allow easy copying of state from one node to another * Instead of starting with a fresh datadir for MNs, reuse a copy of the faucet * Start masternodes in parallel instead of waiting for the previous to finish * Allow specifying of window and threshold with -bip9params * Implement -dip3activationheight for regtests * Implement fast DIP3 activation in DashTestFramework * Speed up activation of DIP3 in dip3-deterministicmns.py * Update qa/rpc-tests/test_framework/test_framework.py Co-Authored-By: codablock <ablock84@gmail.com> * Always assign fast_dip3_activation		2019-01-23 19:36:51 +03:00
..
pull-tester	Add llmq-signing.py tests	2019-01-21 14:42:08 +01:00
rpc-tests	Speed up integration tests with masternodes (#2642 )	2019-01-23 19:36:51 +03:00
README.md	Backports 0.15 pr1 (#2590 )	2019-01-03 12:18:47 +03: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 --jobs=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.