summaryrefslogtreecommitdiffstats
path: root/Help
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2024-07-26 14:34:46 (GMT)
committerBrad King <brad.king@kitware.com>2024-07-26 14:37:35 (GMT)
commitca39258a66c53b531b07d3bb51fa8166b5c5977f (patch)
tree600ec52396cbb4b455db4d81f7ce3a399c52d704 /Help
parentaad3ee074b1a0025247ea9cb0df9bff2417f5042 (diff)
downloadCMake-ca39258a66c53b531b07d3bb51fa8166b5c5977f.zip
CMake-ca39258a66c53b531b07d3bb51fa8166b5c5977f.tar.gz
CMake-ca39258a66c53b531b07d3bb51fa8166b5c5977f.tar.bz2
Help: Fix typo in add_test documentation
Diffstat (limited to 'Help')
-rw-r--r--Help/command/add_test.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Help/command/add_test.rst b/Help/command/add_test.rst
index 557c858..2a3c759 100644
--- a/Help/command/add_test.rst
+++ b/Help/command/add_test.rst
@@ -80,7 +80,7 @@ directory the test is created in.
If the test command exits with code ``0`` the test passes. Non-zero exit code
is a "failed" test. The test property :prop_test:`WILL_FAIL` inverts this
logic. Note that system-level test failures such as segmentation faults or
-heap errors will still fail the test even if ``WILL_FALL`` is true. Output
+heap errors will still fail the test even if ``WILL_FAIL`` is true. Output
written to stdout or stderr is captured by :manual:`ctest(1)` and only
affects the pass/fail status via the :prop_test:`PASS_REGULAR_EXPRESSION`,
:prop_test:`FAIL_REGULAR_EXPRESSION`, or :prop_test:`SKIP_REGULAR_EXPRESSION`