diff options
| author | merge-script <fanquake@gmail.com> | 2024-10-15 11:10:20 +0100 |
|---|---|---|
| committer | merge-script <fanquake@gmail.com> | 2024-10-15 11:10:20 +0100 |
| commit | 15563d3388efccd48db688753c97fde1acf75e86 (patch) | |
| tree | 5bd3998459c32d854ca0a0dd752af678e8a6e80a | |
| parent | 2ac5ba24bf09446a44e7552c8e1be8ce9ee00849 (diff) | |
| parent | e64b2f1a16e8d0ad2cd181d84e3b70312e3cdf33 (diff) | |
Merge bitcoin/bitcoin#30859: doc: cmake: prepend "build" to functional/test_runner.py
e64b2f1a16e8d0ad2cd181d84e3b70312e3cdf33 doc: cmake: prepend and explain "build/" where needed (Larry Ruane)
Pull request description:
This is a small follow-on to #30741, prepend `build/` to the path for `test_runner.py`.
ACKs for top commit:
jonatack:
ACK e64b2f1a16e8d0ad2cd181d84e3b70312e3cdf33
maflcko:
lgtm ACK e64b2f1a16e8d0ad2cd181d84e3b70312e3cdf33
tdb3:
re ACK e64b2f1a16e8d0ad2cd181d84e3b70312e3cdf33
Tree-SHA512: 80943d4f342987bf060adacb1c7db2e9ff8de5a6da592846ba23f230281d3a5b306162c4c86e61739a29323eaa4abf09f69f41302996d5809f448e5788a74a87
| -rw-r--r-- | README.md | 3 | ||||
| -rw-r--r-- | test/functional/README.md | 3 |
2 files changed, 4 insertions, 2 deletions
@@ -53,7 +53,8 @@ and extending unit tests can be found in [/src/test/README.md](/src/test/README. There are also [regression and integration tests](/test), written in Python. -These tests can be run (if the [test dependencies](/test) are installed) with: `test/functional/test_runner.py` +These tests can be run (if the [test dependencies](/test) are installed) with: `build/test/functional/test_runner.py` +(assuming `build` is your build directory). The CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically. diff --git a/test/functional/README.md b/test/functional/README.md index a4994f2e7c..a34bf1827c 100644 --- a/test/functional/README.md +++ b/test/functional/README.md @@ -10,7 +10,8 @@ that file and modify to fit your needs. #### Coverage -Running `test/functional/test_runner.py` with the `--coverage` argument tracks which RPCs are +Assuming the build directory is `build`, +running `build/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 can be used (along with the `--extended` argument) to find out which RPCs we don't have test cases for. |