<html><body>
<h2>Name</h2>
<pre> ctest - Testing driver provided by CMake.</pre>
<h2>Usage</h2>
<pre> ctest [options]</pre>
<p>The "ctest" executable is the CMake test driver program. CMake-generated build trees created for projects that use the ENABLE_TESTING and ADD_TEST commands have testing support. This program will run the tests and report results.
<p>CMake is a cross-platform build system generator. Projects specify their build process with platform-independent CMake listfiles included in each directory of a source tree with the name CMakeLists.txt. Users build a project by using CMake to generate a build system for a native tool on their platform.
<h2>Command-Line Options</h2>
<ul>
<li>
<b><code>-C <config></code></b>: Choose configuration to test.<br>
<p>Some CMake-generated build trees can have multiple build configurations in the same tree. This option can be used to specify which one should be tested. Example configurations are "Debug" and "Release".
</li>
<li>
<b><code>-V,--verbose</code></b>: Enable verbose output from tests.<br>
<p>Test output is normally suppressed and only summary information is displayed. This option will show all test output.
</li>
<li>
<b><code>--debug</code></b>: Displaying more verbose internals of CTest.<br>
<p>This feature will result in large number of output that is mostly useful for debugging dashboard problems.
</li>
<li>
<b><code>-Q,--quiet</code></b>: Make ctest quiet.<br>
<p>This option will suppress all the output. The output log file will still be generated if the --output-log is specified. Options such as --verbose, --extra-verbose, and --debug are ignored if --quiet is specified.
</li>
<li>
<b><code>-O <file>, --output-log <file></code></b>: Output to log file<br>
<p>This option tells ctest to write all its output to a log file.
</li>
<li>
<b><code>-N,--show-only</code></b>: Disable actual execution of tests.<br>
<p>This option tells ctest to list the tests that would be run but not actually run them. Useful in conjunction with the -R and -E options.
</li>
<li>
<b><code>-R <regex></code></b>: Run tests matching regular expression.<br>
<p>This option tells ctest to run only the tests whose names match the given regular expression.
</li>
<li>
<b><code>-E <regex></code></b>: Exclude tests matching regular expression.<br>
<p>This option tells ctest to NOT run the tests whose names match the given regular expression.
</li>
<li>
<b><code>-D <DashboardTest></code></b>: Execute dashboard test<br>
<p>This option tells ctest to perform act as a Dart client and perform a dashboard test. All tests are ModeTest, where Mode can be Experimental, Nightly, and Continuous, and Test can be Start, Update, Configure, Build, Test, Coverage, and Submit.
</li>
<li>
<b><code>-M <TestModel></code></b>: Sets the model for a dashboard<br>
<p>This option tells ctest to act as a Dart client where the TestModel can be Experimental, Nightly, and Continuous. Combining -M and -T is similar to -D
</li>
<li>
<b><code>-T <action></code></b>: Sets the dashboard action to perform<br>
<p>This option tells ctest to act as a Dart client and perform some action such as start, build, test etc. Combining -M and -T is similar to -D
</li>
<li>
<b><code>-S <ConfigScript></code></b>: Execute a dashboard for a configuration<br>
<p>This option tells ctest to load in a configuration script which sets a number of parameters such as the binary and source directories. Then ctest will do what is required to create and run a dashboard. This option basically sets up a dashboard and then runs ctest -D with the appropriate options.
</li>
<li>
<b><code>-A <Notes file></code></b>: Add a notes file with submission<br>
<p>This option tells ctest to include a notes file when submitting dashboard.
</li>
<li>
<b><code>-I [Start,End,Stride,test#,test#|Test file]</code></b>: Run a specific number of tests by number.<br>
<p>This option causes ctest to run tests starting at number Start, ending at number End, and incrementing by Stride. Any additional numbers after Stride are considered individual test numbers. Start, End,or stride can be empty. Optionally a file can be given that contains the same syntax as the command line.
</li>
<li>
<b><code>-U</code></b>: Take the Union of -I and -R<br>
<p>When both -R and -I are specified by default the intersection of tests are run. By specifying -U the union of tests is run instead.
</li>
<li>
<b><code>--interactive-debug-mode [0|1]</code></b>: Set the interactive mode to 0 or 1.<br>
<p>This option causes ctest to run tests in either an interactive mode or a non-interactive mode. On Windows this means that in non-interactive mode, all system debug pop up windows are blocked. In dashboard mode (Experimental, Nightly, Continuous), the default is non-interactive. When just running tests not for a dashboard the default is to allow popups and interactive debugging.
</li>
<li>
<b><code>--build-and-test</code></b>: Configure, build and run a test.<br>
<p>This option tells ctest to configure (i.e. run cmake on), build, and or execute a test. The configure and test steps are optional. The arguments to this command line are the source and binary directories. By default this will run CMake on the Source/Bin directories specified unless --build-nocmake is specified. Both --build-makeprogram and --build-generator MUST be provided to use --built-and-test. If --test-command is specified then that will be run after the build is complete. Other options that affect this mode are --build-target --build-nocmake, --build-run-dir, --build-two-config, --build-exe-dir, --build-project,--build-noclean, --build-options
</li>
<li>
<b><code>--build-target</code></b>: Specify a specific target to build.<br>
<p>This option goes with the --build-and-test option, if left out the all target is built.
</li>
<li>
<b><code>--build-nocmake</code></b>: Run the build without running cmake first.<br>
<p>Skip the cmake step.
</li>
<li>
<b><code>--build-run-dir</code></b>: Specify directory to run programs from.<br>
<p>Directory where programs will be after it has been compiled.
</li>
<li>
<b><code>--build-two-config</code></b>: Run CMake twice<br>
</li>
<li>
<b><code>--build-exe-dir</code></b>: Specify the directory for the executable.<br>
</li>
<li>
<b><code>--build-generator</code></b>: Specify the generator to use.<br>
</li>
<li>
<b><code>--build-project</code></b>: Specify the name of the project to build.<br>
</li>
<li>
<b><code>--build-makeprogram</code></b>: Specify the make program to use.<br>
</li>
<li>
<b><code>--build-noclean</code></b>: Skip the make clean step.<br>
</li>
<li>
<b><code>--build-options</code></b>: Add extra options to the build step.<br>
<p>This option must be the last option with the exception of --test-command
</li>
<li>
<b><code>--test-command</code></b>: The test to run with the --build-and-test option.<br>
</li>
<li>
<b><code>--tomorrow-tag</code></b>: Nightly or experimental starts with next day tag.<br>
<p>This is useful if the build will not finish in one day.
</li>
<li>
<b><code>--ctest-config</code></b>: The configuration file used to initialize CTest state when submitting dashboards.<br>
<p>This option tells CTest to use different initialization file instead of DartConfiguration.tcl. This way multiple initialization files can be used for example to submit to multiple dashboards.
</li>
<li>
<b><code>--copyright [file]</code></b>: Print the CMake copyright and exit.<br>
<p>If a file is specified, the copyright is written into it.
</li>
<li>
<b><code>--help</code></b>: Print usage information and exit.<br>
<p>Usage describes the basic command line interface and its options.
</li>
<li>
<b><code>--help-full [file]</code></b>: Print full help and exit.<br>
<p>Full help displays most of the documentation provided by the UNIX man page. It is provided for use on non-UNIX platforms, but is also convenient if the man page is not installed. If a file is specified, the help is written into it.
</li>
<li>
<b><code>--help-html [file]</code></b>: Print full help in HTML format.<br>
<p>This option is used by CMake authors to help produce web pages. If a file is specified, the help is written into it.
</li>
<li>
<b><code>--help-man [file]</code></b>: Print a UNIX man page and exit.<br>
<p>This option is used by the cmake build to generate the UNIX man page. If a file is specified, the help is written into it.
</li>
<li>
<b><code>--version [file]</code></b>: Show program name/version banner and exit.<br>
<p>If a file is specified, the version is written into it.
</li>
</ul>
<h2>Copyright</h2>
<p>Copyright (c) 2002 Kitware, Inc., Insight Consortium. All rights reserved.
<p>Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
<ul>
<li>
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
</li>
<li>
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
</li>
<li>
The names of Kitware, Inc., the Insight Consortium, or the names of any consortium members, or of any contributors, may not be used to endorse or promote products derived from this software without specific prior written permission.
</li>
<li>
Modified source versions must be plainly marked as such, and must not be misrepresented as being the original software.
</li>
</ul>
<p>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<h2>Mailing List</h2>
<p>For help and discussion about using cmake, a mailing list is provided at cmake@www.cmake.org. Please first read the full documentation at http://www.cmake.org before posting questions to the list.
</body></html>
