* Merge #9744: Remove unused module from rpc-testsa432aa0
Remove unused module from rpc-tests (Takashi Mitsuta) * Merge #9696: [trivial] Fix recently introduced typos in comments0c9b9b7
[trivial] Fix recently introduced typos in comments (practicalswift) * Merge #9657: Improve rpc-tests.pya6a3e58
Various review markups for rpc-tests.py improvements (John Newbery)3de3ccd
Refactor rpc-tests.py (John Newbery)afd38e7
Improve rpc-tests.py arguments (John Newbery)91bffff
Use argparse in rpc_tests.py (John Newbery)1581ecb
Use configparser in rpc-tests.py (John Newbery) * Merge #9724: Qt/Intro: Add explanation of IBD processf6d18f5
Qt/Intro: Explain a bit more what will happen first time (Luke Dashjr)50c5657
Qt/Intro: Storage shouldn't grow significantly with pruning enabled (Luke Dashjr)9adb694
Qt/Intro: Move sizeWarningLabel text into C++ code (Luke Dashjr) * Merge #9794: Minor update to qrencode package builder1bfe6b4
Use package name variable inside $(package)_file_name variable (Mitchell Cash) * Merge #9726: netbase: Do not print an error on connection timeouts through proxy3ddfe29
netbase: Do not print an error on connection timeouts through proxy (Wladimir J. van der Laan)13f6085
netbase: Make InterruptibleRecv return an error code instead of bool (Wladimir J. van der Laan) * Merge #9727: Remove fallbacks for boost_filesystem < v3056aba2
Remove fallbacks for boost_filesystem < v3 (Wladimir J. van der Laan) * Merge #9485: ZMQ example using python3 and asynciob471daf
Adddress nits, use asyncio signal handling, create_task (Bob McElrath)4bb7d1b
Add python version checks and 3.4 example (Bob McElrath)5406d51
Rewrite to not use Polling wrapper for asyncio, link to python2.7 example (Bob McElrath)5ea5368
ZMQ example using python3 and asyncio (Bob McElrath) * Merge #9807: RPC doc fix-ups.851f6a3
[qa][doc] Correct rpc test options in readme (fanquake)41e7219
[trivial] Add tests_config.ini to .gitignore (fanquake) * Dashify Co-Authored-By: PastaPastaPasta <pasta@dashboost.org> * Change file permissions * update travis.yml -parallel -> --jobs
2.5 KiB
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.