mirrors/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-01-19 05:45:05 +01:00
Code Issues Projects Releases Wiki Activity

doc: Describe log files + consistent paths in test READMEs

Browse Source
This commit is contained in:
Martin Erlandsson 2019-04-16 14:49:42 +02:00 committed by Fabian Jahr
parent 561a7d3047
commit 9576614d2d
2 changed files with 31 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
test/README.md
View File

@ -88,7 +88,7 @@ By default, up to 4 tests will be run in parallel by test_runner. To specify
how many jobs to run, append `--jobs=n` how many jobs to run, append `--jobs=n`
The individual tests and the test_runner harness have many command-line The individual tests and the test_runner harness have many command-line
options. Run `test_runner.py -h` to see them all. options. Run `test/functional/test_runner.py -h` to see them all.
#### Troubleshooting and debugging test failures #### Troubleshooting and debugging test failures
@ -101,7 +101,7 @@ killed all its bitcoind nodes), then there may be a port conflict which will
cause the test to fail. It is recommended that you run the tests on a system cause the test to fail. It is recommended that you run the tests on a system
where no other bitcoind processes are running. where no other bitcoind processes are running.
On linux, the test_framework will warn if there is another On linux, the test framework will warn if there is another
bitcoind process running when the tests are started. bitcoind process running when the tests are started.
If there are zombie bitcoind processes after test failure, you can kill them If there are zombie bitcoind processes after test failure, you can kill them
@ -130,7 +130,7 @@ tests will fail. If this happens, remove the cache directory (and make
sure bitcoind processes are stopped as above): sure bitcoind processes are stopped as above):
```bash ```bash
rm -rf cache rm -rf test/cache
killall bitcoind killall bitcoind
``` ```
@ -149,6 +149,15 @@ levels using the logger included in the test_framework, e.g.
fails, the `test_framework.log` and bitcoind `debug.log`s will all be dumped fails, the `test_framework.log` and bitcoind `debug.log`s will all be dumped
to the console to help troubleshooting. to the console to help troubleshooting.
These log files can be located under the test data directory (which is always
printed in the first line of test output):
- `<test data directory>/test_framework.log`
- `<test data directory>/node<node number>/regtest/debug.log`.
The node number identifies the relevant test node, starting from `node0`, which
corresponds to its position in the nodes list of the specific test,
e.g. `self.nodes[0]`.
To change the level of logs output to the console, use the `-l` command line To change the level of logs output to the console, use the `-l` command line
argument. argument.
@ -157,7 +166,7 @@ aggregate log by running the `combine_logs.py` script. The output can be plain
text, colorized text or html. For example: text, colorized text or html. For example:
``` ```
combine_logs.py -c <test data directory> | less -r test/functional/combine_logs.py -c <test data directory> | less -r
``` ```
will pipe the colorized logs from the test into less. will pipe the colorized logs from the test into less.

33
test/functional/README.md
View File

@ -4,13 +4,13 @@
#### Example test #### Example test
The [example_test.py](example_test.py) is a heavily commented example of a test case that uses both The file [test/functional/example_test.py](example_test.py) is a heavily commented example
the RPC and P2P interfaces. If you are writing your first test, copy that file of a test case that uses both the RPC and P2P interfaces. If you are writing your first test, copy
and modify to fit your needs. that file and modify to fit your needs.
#### Coverage #### Coverage
Running `test_runner.py` with the `--coverage` argument tracks which RPCs are Running `test/functional/test_runner.py` with the `--coverage` argument tracks which RPCs are
called by the tests and prints a report of uncovered RPCs in the summary. This called by the tests and prints a report of uncovered RPCs in the summary. This
can be used (along with the `--extended` argument) to find out which RPCs we can be used (along with the `--extended` argument) to find out which RPCs we
don't have test cases for. don't have test cases for.
@ -82,7 +82,7 @@ P2P messages. These can be found in the following source files:
#### Using the P2P interface #### Using the P2P interface
- `messages.py` contains all the definitions for objects that pass - [messages.py](test_framework/messages.py) contains all the definitions for objects that pass
over the network (`CBlock`, `CTransaction`, etc, along with the network-level over the network (`CBlock`, `CTransaction`, etc, along with the network-level
wrappers for them, `msg_block`, `msg_tx`, etc). wrappers for them, `msg_block`, `msg_tx`, etc).
@ -96,32 +96,35 @@ the Bitcoin Core node application logic. For custom behaviour, subclass the
P2PInterface object and override the callback methods. P2PInterface object and override the callback methods.
- Can be used to write tests where specific P2P protocol behavior is tested. - Can be used to write tests where specific P2P protocol behavior is tested.
Examples tests are `p2p_unrequested_blocks.py`, `p2p_compactblocks.py`. Examples tests are [p2p_unrequested_blocks.py](p2p_unrequested_blocks.py),
[p2p_compactblocks.py](p2p_compactblocks.py).
### test-framework modules ### Test framework modules
The following are useful modules for test developers. They are located in
[test/functional/test_framework/](test_framework).
#### [test_framework/authproxy.py](test_framework/authproxy.py) #### [authproxy.py](test_framework/authproxy.py)
Taken from the [python-bitcoinrpc repository](https://github.com/jgarzik/python-bitcoinrpc). Taken from the [python-bitcoinrpc repository](https://github.com/jgarzik/python-bitcoinrpc).
#### [test_framework/test_framework.py](test_framework/test_framework.py) #### [test_framework.py](test_framework/test_framework.py)
Base class for functional tests. Base class for functional tests.
#### [test_framework/util.py](test_framework/util.py) #### [util.py](test_framework/util.py)
Generally useful functions. Generally useful functions.
#### [test_framework/mininode.py](test_framework/mininode.py) #### [mininode.py](test_framework/mininode.py)
Basic code to support P2P connectivity to a bitcoind. Basic code to support P2P connectivity to a bitcoind.
#### [test_framework/script.py](test_framework/script.py) #### [script.py](test_framework/script.py)
Utilities for manipulating transaction scripts (originally from python-bitcoinlib) Utilities for manipulating transaction scripts (originally from python-bitcoinlib)
#### [test_framework/key.py](test_framework/key.py) #### [key.py](test_framework/key.py)
Test-only secp256k1 elliptic curve implementation Test-only secp256k1 elliptic curve implementation
#### [test_framework/bignum.py](test_framework/bignum.py) #### [bignum.py](test_framework/bignum.py)
Helpers for script.py Helpers for script.py
#### [test_framework/blocktools.py](test_framework/blocktools.py) #### [blocktools.py](test_framework/blocktools.py)
Helper functions for creating blocks and transactions. Helper functions for creating blocks and transactions.
### Benchmarking with perf ### Benchmarking with perf