doc: cmake: prepend and explain "build/" where needed

This commit is contained in:
Larry Ruane 2024-09-09 21:42:57 -06:00
parent df3f63ccfa
commit e64b2f1a16
2 changed files with 4 additions and 2 deletions

View File

@ -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 There are also [regression and integration tests](/test), written
in Python. 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, 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. and that unit/sanity tests are run automatically.

View File

@ -10,7 +10,8 @@ that file and modify to fit your needs.
#### Coverage #### 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 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.