ctest_test([BUILD <build-dir>] [APPEND] [START <start-number>] [END <end-number>] [STRIDE <stride-number>] [EXCLUDE <exclude-regex>] [INCLUDE <include-regex>] [EXCLUDE_LABEL <label-exclude-regex>] [INCLUDE_LABEL <label-include-regex>] [EXCLUDE_FIXTURE <regex>] [EXCLUDE_FIXTURE_SETUP <regex>] [EXCLUDE_FIXTURE_CLEANUP <regex>] [PARALLEL_LEVEL <level>] [TEST_LOAD <threshold>] [SCHEDULE_RANDOM <ON|OFF>] [STOP_TIME <time-of-day>] [RETURN_VALUE <result-var>] [CAPTURE_CMAKE_ERROR <result-var>] [QUIET] )
Run tests in the project build tree and store results in
Test.xml for submission with the
The options are:
CTEST_BINARY_DIRECTORYvariable is used.
Test.xmlfor append to results previously submitted to a dashboard server since the last
ctest_start()call. Append semantics are defined by the dashboard server in use. This does not cause results to be appended to a
.xmlfile produced by a previous call to this command.
<regex>. Note that all other fixture behavior is retained, including test dependencies and skipping tests that have fixture setup tests that fail.
EXCLUDE_FIXTUREexcept only matching setup tests are excluded.
EXCLUDE_FIXTUREexcept only matching cleanup tests are excluded.
CTEST_TEST_LOADvariable will be checked, and then the
--test-loadcommand-line argument to
ctest(1). See also the
TestLoadsetting in the CTest Test Step.
0if all tests passed. Store non-zero if anything went wrong.
<result-var>variable -1 if there are any errors running the command and prevent ctest from returning non-zero if an error occurs.
© 2000–2019 Kitware, Inc. and Contributors
Licensed under the BSD 3-clause License.