History

Patrick Lodder d3d688deae rpc: configure auxpow rpc methods to use Namecoin-compatible API Allows easy integration with mining software that expects either a "_target" (Namecoin) or a "target" (Dogecoin) field when creating auxpow blocks using the -rpcnamecoinapi startup arg. This saves pools effort in integrating the API they need whenever a new Dogecoin Core release comes out.		2021-11-01 15:59:23 -04:00
..
pull-tester	qa: add qa test for createauxblock	2021-10-30 15:59:45 -04:00
rpc-tests	rpc: configure auxpow rpc methods to use Namecoin-compatible API	2021-11-01 15:59:23 -04:00
README.md	update qa/README.md to reflect working installation instructions	2021-07-28 16:12:52 -07:00

README.md

The pull-tester folder contains a script to call multiple tests from the rpc-tests folder.

Every pull request to the dogecoin 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

python3-zmq and ltc_scrypt are required. On Ubuntu or Debian they can be installed via:

sudo apt-get update && apt-get install -y curl python3-zmq python3-dev gcc
cd qa/pull-tester/ && ./install-deps.sh

OS X

brew install curl
pip3 install pyzmq
cd qa/pull-tester && ./install-deps.sh

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 bitcoinds and test.* datadir on exit or error
  --noshutdown          Don't stop bitcoinds after the test execution
  --srcdir=SRCDIR       Source directory containing bitcoind/bitcoin-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*50=1250 BTC) 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 dogecoind

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.