|
|
@@ -1,39 +1,79 @@
|
|
|
ctest_test
|
|
|
----------
|
|
|
|
|
|
-Run tests in the project build tree.
|
|
|
+Perform the :ref:`CTest Test Step` as a :ref:`Dashboard Client`.
|
|
|
|
|
|
::
|
|
|
|
|
|
- ctest_test([BUILD build_dir] [APPEND]
|
|
|
- [START start number] [END end number]
|
|
|
- [STRIDE stride number] [EXCLUDE exclude regex ]
|
|
|
- [INCLUDE include regex] [RETURN_VALUE res]
|
|
|
- [EXCLUDE_LABEL exclude regex]
|
|
|
- [INCLUDE_LABEL label regex]
|
|
|
- [PARALLEL_LEVEL level]
|
|
|
- [SCHEDULE_RANDOM on]
|
|
|
- [STOP_TIME time of day])
|
|
|
-
|
|
|
-Tests the given build directory and stores results in Test.xml. The
|
|
|
-second argument is a variable that will hold value. Optionally, you
|
|
|
-can specify the starting test number START, the ending test number
|
|
|
-END, the number of tests to skip between each test STRIDE, a regular
|
|
|
-expression for tests to run INCLUDE, or a regular expression for tests
|
|
|
-to not run EXCLUDE. EXCLUDE_LABEL and INCLUDE_LABEL are regular
|
|
|
-expression for test to be included or excluded by the test property
|
|
|
-LABEL. PARALLEL_LEVEL should be set to a positive number representing
|
|
|
-the number of tests to be run in parallel. SCHEDULE_RANDOM will
|
|
|
-launch tests in a random order, and is typically used to detect
|
|
|
-implicit test dependencies. STOP_TIME is the time of day at which the
|
|
|
-tests should all stop running.
|
|
|
-
|
|
|
-The APPEND option marks results for append to those previously
|
|
|
-submitted to a dashboard server since the last ctest_start. Append
|
|
|
-semantics are defined by the dashboard server in use.
|
|
|
-
|
|
|
-The QUIET option suppresses 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 QUIET
|
|
|
-option.
|
|
|
+ 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>]
|
|
|
+ [SCHEDULE_RANDOM <ON|OFF>]
|
|
|
+ [STOP_TIME <time-of-day>]
|
|
|
+ [RETURN_VALUE <result-var>]
|
|
|
+ [QUIET]
|
|
|
+ )
|
|
|
+
|
|
|
+Run tests in the project build tree and store results in
|
|
|
+``Test.xml`` for submission with the :command:`ctest_submit` command.
|
|
|
+
|
|
|
+The options are:
|
|
|
+
|
|
|
+``BUILD <build-dir>``
|
|
|
+ Specify the top-level build directory. If not given, the
|
|
|
+ :variable:`CTEST_BINARY_DIRECTORY` variable is used.
|
|
|
+
|
|
|
+``APPEND``
|
|
|
+ Mark results for append to those previously submitted to a
|
|
|
+ dashboard server since the last :command:`ctest_start` call.
|
|
|
+ Append semantics are defined by the dashboard server in use.
|
|
|
+
|
|
|
+``START <start-number>``
|
|
|
+ Specify the beginning of a range of test numbers.
|
|
|
+
|
|
|
+``END <end-number>``
|
|
|
+ Specify the end of a range of test numbers.
|
|
|
+
|
|
|
+``STRIDE <stride-number>``
|
|
|
+ Specify the stride by which to step acorss a range of test numbers.
|
|
|
+
|
|
|
+``EXCLUDE <exclude-regex>``
|
|
|
+ Specify a regular expression matching test names to exclude.
|
|
|
+
|
|
|
+``INCLUDE <include-regex>``
|
|
|
+ Specify a regular expression matching test names to include.
|
|
|
+ Tests not matching this expression are excluded.
|
|
|
+
|
|
|
+``EXCLUDE_LABEL <label-exclude-regex>``
|
|
|
+ Specify a regular expression matching test labels to exclude.
|
|
|
+
|
|
|
+``INCLUDE_LABEL <label-include-regex>``
|
|
|
+ Specify a regular expression matching test labels to include.
|
|
|
+ Tests not matching this expression are excluded.
|
|
|
+
|
|
|
+``PARALLEL_LEVEL <level>``
|
|
|
+ Specify a positive number representing the number of tests to
|
|
|
+ be run in parallel.
|
|
|
+
|
|
|
+``SCHEDULE_RANDOM <ON|OFF>``
|
|
|
+ Launch tests in a random order. This may be useful for detecting
|
|
|
+ implicit test dependencies.
|
|
|
+
|
|
|
+``STOP_TIME <time-of-day>``
|
|
|
+ Specify a time of day at which the tests should all stop running.
|
|
|
+
|
|
|
+``RETURN_VALUE <result-var>``
|
|
|
+ Store in the ``<result-var>`` variable ``0`` if all tests passed.
|
|
|
+ Store non-zero if anything went wrong.
|
|
|
+
|
|
|
+``QUIET``
|
|
|
+ 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 ``QUIET`` option.
|