From 7ee5c3c5b2fb477a283df8861e28005ef514bd20 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C5=91rinc?= Date: Sun, 18 Aug 2024 20:52:45 +0200 Subject: [PATCH] Fix a few likely documentation typos --- doc/build-windows-msvc.md | 2 +- src/test/README.md | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/build-windows-msvc.md b/doc/build-windows-msvc.md index ec839724dd200..1daca1f93e258 100644 --- a/doc/build-windows-msvc.md +++ b/doc/build-windows-msvc.md @@ -46,7 +46,7 @@ cmake --list-presets CMake will put the resulting object files, libraries, and executables into a dedicated build directory. -In following istructions, the "Debug" configuration can be specified instead of the "Release" one. +In the following instructions, the "Debug" configuration can be specified instead of the "Release" one. ### 4. Building with Dynamic Linking with GUI diff --git a/src/test/README.md b/src/test/README.md index ace2b0b0cb802..a6e89aac80ae9 100644 --- a/src/test/README.md +++ b/src/test/README.md @@ -17,7 +17,7 @@ during the generation of the Bitcoin Core build system and tests weren't explicitly disabled. Assuming the build directory is named `build`, the unit tests can be run -with `ctests --test-dir build`, which includes unit tests from subtrees. +with `ctest --test-dir build`, which includes unit tests from subtrees. To run the unit tests manually, launch `build/src/test/test_bitcoin`. To recompile after a test file was modified, run `cmake --build build` and then run the test again. If you @@ -83,7 +83,7 @@ so no leftover state is used.) ```bash $ build/src/test/test_bitcoin --run_test=getarg_tests/doubledash -- -testdatadir=/somewhere/mydatadir -Test directory (will not be deleted): "/somewhere/mydatadir/test_common_Bitcoin Core/getarg_tests/doubledash/datadir +Test directory (will not be deleted): "/somewhere/mydatadir/test_common_Bitcoin Core/getarg_tests/doubledash/datadir" Running 1 test case... *** No errors detected @@ -112,8 +112,8 @@ see `uint256_tests.cpp`. ### Logging and debugging in unit tests -`ctest --test-dir build` will write to a log file `build/Testing/Temporary/LastTest.log`. You can -additionaly use the `--output-on-failure` option to display logs of the failed tests automatically +`ctest --test-dir build` will write to the log file `build/Testing/Temporary/LastTest.log`. You can +additionally use the `--output-on-failure` option to display logs of the failed tests automatically on failure. For running individual tests verbosely, refer to the section [above](#running-individual-tests). @@ -150,5 +150,5 @@ You can then explore the core dump using ```bash gdb build/src/test/test_bitcoin core -(gbd) bt # produce a backtrace for where a segfault occurred +(gdb) bt # produce a backtrace for where a segfault occurred ```