18950f923e
* Allow sub-batch verification in CBLSInsecureBatchVerifier * Implement batch verification of CDKGDebugStatus messages * Use uint8_t for statusBitset in CDKGDebugMemberStatus and CDKGDebugSessionStatus No need to waste one byte per member and per LLMQ type. * Reserve 4k of buffer for CSerializedNetMsg buffer Profiling has shown that a lot of time is spent in resizing the data vector when large messages are involved. * Remove nHeight from CDKGDebugStatus This field changes every block and causes all masternodes to propagate its status for every block, even if nothing DKG related has changed. * Leave out session statuses when we're not a member of that session Otherwise MNs which are not members of DKG sessions will spam the network * Remove receivedFinalCommitment from CDKGDebugSessionStatus This is not bound to a session and thus is prone to spam the network when final commitments are propagated in the finalization phase. * Add "minableCommitments" to "quorum dkgstatus" * Hold cs_main while calling GetMinableCommitment * Abort processing of pending debug messages when spork18 gets disabled * Don't ask for debug messages when we've already seen them "statuses" only contains the current messages but none of the old messages, so nodes kept re-requesting old messages. |
||
|---|---|---|
| .. | ||
| pull-tester | ||
| rpc-tests | ||
| 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.