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>] [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:
- Specify the top-level build directory. If not given, the
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.
- Specify the beginning of a range of test numbers.
- Specify the end of a range of test numbers.
- Specify the stride by which to step across a range of test numbers.
- Specify a regular expression matching test names to exclude.
- Specify a regular expression matching test names to include. Tests not matching this expression are excluded.
- Specify a regular expression matching test labels to exclude.
- Specify a regular expression matching test labels to include. Tests not matching this expression are excluded.
- Specify a positive number representing the number of tests to be run in parallel.
- While running tests in parallel, try not to start tests when they
may cause the CPU load to pass above a given threshold. If not
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.
- Launch tests in a random order. This may be useful for detecting implicit test dependencies.
- Specify a time of day at which the tests should all stop running.
- Store in the
0if all tests passed. Store non-zero if anything went wrong.
- Store in the
<result-var>variable -1 if there are any errors running the command and prevent ctest from returning non-zero if an error occurs.
- Suppress any CTest-specific non-error messages that would have otherwise
been printed to the console. Output from the underlying test command is not
affected. Summary info detailing the percentage of passing tests is also
unaffected by the