Browse Source

[qa] Split README.md to /qa and /qa/rpc-tests

+ Update with new -help message
tags/v0.15.1
MarcoFalke 6 years ago
parent
commit
cc975745d5
2 changed files with 46 additions and 43 deletions
  1. 46
    0
      qa/README.md
  2. 0
    43
      qa/rpc-tests/README.md

+ 46
- 0
qa/README.md View File

@@ -0,0 +1,46 @@
Notes
=====

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`

Possible options:

```
-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:

```bash
rm -rf cache
killall bitcoind
```

Further information about the test framework and individual rpc
tests is found in [qa/rpc-tests/README.md](/qa/rpc-tests/README.md).

+ 0
- 43
qa/rpc-tests/README.md View File

@@ -33,49 +33,6 @@ Helpers for script.py
### [test_framework/blocktools.py](test_framework/blocktools.py)
Helper functions for creating blocks and transactions.


Notes
=====

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`

Possible options:

```
-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
```

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:

```bash
rm -rf cache
killall bitcoind
```

P2P test design notes
---------------------


Loading…
Cancel
Save