mirror of https://github.com/dashpay/dash.git synced 2024-12-27 21:12:48 +01:00

History

Wladimir J. van der Laan f34cdcbd80 Merge #9294 : Use internal HD chain for change outputs (hd split) `4115af7` Fix rebase issue where pwalletMain was used instead of pwallet Ser./Deser. nInternalChainCounter as last element (Jonas Schnelli) `9382f04` Do not break backward compatibility during wallet encryption (Jonas Schnelli) `1df08d1` Add assertion for CanSupportFeature(FEATURE_HD_SPLIT) (Jonas Schnelli) `cd468d0` Define CWallet::DeriveNewChildKey() as private (Jonas Schnelli) `ed79e4f` Optimize GetOldestKeyPoolTime(), return as soon as we have both oldest keys (Jonas Schnelli) `771a304` Make sure we set the wallets min version to FEATURE_HD_SPLIT at the very first point (Jonas Schnelli) `1b3b5c6` Slightly modify fundrawtransaction.py test (change getnewaddress() into getrawchangeaddress()) (Jonas Schnelli) `003e197` Remove FEATURE_HD_SPLIT bump TODO (Jonas Schnelli) `d9638e5` Overhaul the internal/external key derive switch (Jonas Schnelli) `1090502` Fix superfluous cast and code style nits in RPC wallet-hd.py test (Jonas Schnelli) `58e1483` CKeyPool avoid "catch (...)" in SerializationOp (Jonas Schnelli) `e138876` Only show keypoolsize_hd_internal if HD split is enabled (Jonas Schnelli) `add38d9` GetOldestKeyPoolTime: if HD & HD Chain Split is enabled, response max(oldest-internal-key, oldest-external-key) (Jonas Schnelli) `dd526c2` Don't switch to HD-chain-split during wallet encryption of non HD-chain-split wallets (Jonas Schnelli) `79df9df` Switch to 100% for the HD internal keypool size (Jonas Schnelli) `bcafca1` Make sure we always generate one keypool key at minimum (Jonas Schnelli) `d0a627a` Fix issue where CDataStream->nVersion was taken a CKeyPool record version (Jonas Schnelli) `9af8f00` Make sure we hand out keypool keys if HD_SPLIT is not enabled (Jonas Schnelli) `469a47b` Make sure ReserveKeyFromKeyPool only hands out internal keys if HD_SPLIT is supported (Jonas Schnelli) `05a9b49` Fix wrong keypool internal size in RPC getwalletinfo help (Jonas Schnelli) `01de822` Removed redundant IsLocked() check in NewKeyPool() (Jonas Schnelli) `d59531d` Immediately return setKeyPool's size if HD or HD_SPLIT is disabled or not supported (Jonas Schnelli) `02592f4` [Wallet] split the keypool in an internal and external part (Jonas Schnelli) Tree-SHA512: 80d355d5e844b48c3163b56c788ab8b5b5285db0ceeb19858a3ef517d5a702afeca21dbae526d7b8fb4101c2a745af1d92bf557c40cf516780f17992bf678c1a		2017-03-29 12:51:06 +02:00
..
functional	Merge #9294 : Use internal HD chain for change outputs (hd split)	2017-03-29 12:51:06 +02:00
util	Move src/test/bitcoin-util-test.py to test/util/bitcoin-util-test.py	2017-03-20 10:40:31 -04:00
README.md	Move src/test/bitcoin-util-test.py to test/util/bitcoin-util-test.py	2017-03-20 10:40:31 -04:00

README.md

This directory contains integration tests that test bitcoind and its utilities in their entirety. It does not contain unit tests, which can be found in /src/test, /src/wallet/test, etc.

There are currently two sets of tests in this directory:

functional which test the functionality of bitcoind and bitcoin-qt by interacting with them through the RPC and P2P interfaces.
util which tests the bitcoin utilities, currently only bitcoin-tx.

The util tests are run as part of make check target. The functional tests are run by the travis continuous build process whenever a pull request is opened. Both sets of tests can also be run locally.

Functional Test dependencies

The ZMQ functional test requires a python ZMQ library. To install it:

on Unix, run sudo apt-get install python3-zmq
on mac OS, run pip3 install pyzmq

Running tests locally

Functional tests

You can run any single test by calling

test/functional/test_runner.py <testname>

Or you can run any combination of tests by calling

test/functional/test_runner.py <testname1> <testname2> <testname3> ...

Run the regression test suite with

test/functional/test_runner.py

Run all possible tests with

test/functional/test_runner.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 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 test/functional/test_runner.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 bitcoind

Util tests

Util tests can be run locally by running test/util/bitcoin-util-test.py. Use the -v option for verbose output.

Writing functional tests

You are encouraged to write functional tests for new or existing features. Further information about the functional test framework and individual tests is found in test/functional.