From e64b2f1a16e8d0ad2cd181d84e3b70312e3cdf33 Mon Sep 17 00:00:00 2001 From: Larry Ruane Date: Mon, 9 Sep 2024 21:42:57 -0600 Subject: [PATCH] doc: cmake: prepend and explain "build/" where needed --- README.md | 3 ++- test/functional/README.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cf106ad687a..c5b6ce4588e 100644 --- a/README.md +++ b/README.md @@ -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 a4994f2e7c9..a34bf1827cb 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.