8ea40102c0
* Remove leftover RBF code from BTC * remove rbf #include * remove rbf in rpc-tests * removes replace-by-fee.py * remove help text related to rbf * remove comment text relating to rbf * remove "-mempoolreplacement" cli option * Remove (effectively dead) RBF code which would never have been called anyway and some assosiated variables * since `setConflicts` is always empty, this is dead code * Since we don't have RBF, don't have to do this check. Also, since `setConflicts` is always empty this is dead code * removes unneccesary if as it will always be true * remove unused `set<uint256> setConflicts` * Removes replacement of conflicting txs, as conflicting txs are never accepted * removes RBF from `validForFeeEstimation` * removes (probably) unnecessary lock * remove replacing part of the AcceptToMemoryPool and AcceptToMemoryPoolWIthTime * fixes err in ps.cpp, didn't remove arg * RBF in net_processing.cpp * remove arg in ps-server.cpp * removes another arg in PS code * removes rawtx.c AcceptToMemoryPool arg * removes arg in txvalidationcache_tests.cpp * remove extra args * forgot an arg * fix typo in 82898b0 * remove unused fEnableReplacement in validation.h * remove the removal reason REPLACED in txmempool.h * removed unused variable * comment typo |
||
|---|---|---|
| .. | ||
| 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 -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.