Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Fetching latest commit…

Cannot retrieve the latest commit at this time

..
Failed to load latest commit information.
Architecture
ArgumentExpansion
Assembler
BuildDepends
BundleGeneratorTest
BundleTest
BundleUtilities
CFBundleTest
CMakeCommands/target_link_libraries
CMakeLib
CMakeOnly
CMakeTestAllGenerators
CMakeTestBadCommandLines
CMakeTestMultipleConfigures
CMakeTests
COnly
CPackComponents
CPackComponentsForAll
CPackTestAllGenerators
CTestConfig
CTestScriptMode
CTestTest
CTestTest2
CTestTestBadExe
CTestTestChecksum
CTestTestConfigFileInBuildDir
CTestTestCostSerial
CTestTestCrash
CTestTestCycle
CTestTestDepends
CTestTestFailedSubmits
CTestTestFailure
CTestTestParallel
CTestTestResourceLock
CTestTestRunScript
CTestTestScheduler
CTestTestStopTime
CTestTestSubdir
CTestTestTimeout
CTestTestUpload
CTestTestZeroTimeout
CheckCompilerRelatedVariables
CommandLineTest
CompileCommandOutput
CompileDefinitions
Complex
ComplexOneConfig
Contracts
CrossCompile
CustComDepend
CustomCommand
CustomCommandWorkingDirectory
CxxOnly
Dependency
DocTest
DoubleProject
EmptyLibrary
Environment
ExportImport
ExternalOBJ
ExternalProject
FindModulesExecuteAll
FindPackageModeMakefileTest
FindPackageTest
ForceInclude
Fortran
FortranC
FortranOnly
Framework
FunctionTest
GeneratorExpression
IPO
IncludeDirectories
JCTest
Java
Jump
LibName
LinkDirectory
LinkFlags
LinkLanguage
LinkLine
LinkLineOrder
LinkStatic
LoadCommand
LoadCommandOneConfig
MFC
MacroTest
MakeClean
MathTest
MissingSourceFile
Module
ModuleDefinition
MumpsCoverage
NewlineArgs
ObjC++
ObjectLibrary
OutDir
OutOfBinary
OutOfSource
PerConfig
Plugin
Policy0002
PolicyScope
PositionIndependentTargets
PreOrder
PrecompiledHeader
Preprocess
Properties
Qt4Deploy
QtAutomoc
ReturnTest
RunCMake
RuntimePath
SBCS
SameName
SetLang
Simple
SimpleCOnly
SimpleExclude
SimpleInstall
SimpleInstallS2
SourceGroups
StringFileTest
SubDir
SubDirSpaces
SubProject
SwigTest
SystemInformation
TarTest
TargetName
TestDriver
Testing
TestsWorkingDirectory
TryCompile
Tutorial
Unset
VSExternalInclude
VSGNUFortran
VSMidl
VSResource
VariableUnusedViaSet
VariableUnusedViaUnset
VariableUsage
Wrapping
X11
iOSNavApp
.NoDartCoverage
CMakeBuildTest.cmake.in
CMakeInstall.cmake
CMakeLists.txt
CMakeWizardTest.cmake
CTestUpdateBZR.cmake.in
CTestUpdateCVS.cmake.in
CTestUpdateCommon.cmake
CTestUpdateGIT.cmake.in
CTestUpdateGIT.sh.in
CTestUpdateHG.cmake.in
CTestUpdateSVN.cmake.in
CheckFortran.cmake
EnforceConfig.cmake.in
README
TestInstall.sh.in
bootstrap.bat.in
test_clean.cmake.in

README

If you think about adding a new testcase then here is a small checklist you
can run through to find a proper place for it. Go through the list from the
beginning and stop once you find something that matches your tests needs,
i.e. if you will test a module and only need the configure mode use the
instructions from section 2, not 3.

1. Your testcase can run in CMake script mode, i.e. "cmake -P something"

Put your test in Tests/CMakeTests/ directory as a .cmake.in file. It will be
put into the test binary directory by configure_file(... @ONLY) and run from
there. Use the AddCMakeTest() macro in Tests/CMakeTests/CMakeLists.txt to add
your test to the test runs.

2. Your test needs CMake to run in configure mode, but will not build anything

This includes tests that will build something using try_compile() and friends,
but nothing that expects add_executable(), add_library(), or add_test() to run.

If the test configures the project only once and it must succeed then put it
into the Tests/CMakeOnly/ directory.  Create a subdirectory named like your
test and write the CMakeLists.txt you need into that subdirectory. Use the
add_CMakeOnly_test() macro from Tests/CMakeOnly/CMakeLists.txt to add your
test to the test runs.

If the test configures the project with multiple variations and verifies
success or failure each time then put it into the Tests/RunCMake/ directory.
Read the instructions in Tests/RunCMake/CMakeLists.txt to add a test.

3. If you are testing something from the Modules directory

Put your test in the Tests/Modules/ directory. Create a subdirectory there
named after your test. Use the ADD_TEST_MACRO macro from Tests/CMakeLists.txt
to add your test to the test run. If you have put your stuff in
Tests/Modules/Foo then you call it using ADD_TEST_MACRO(Module.Foo Foo).

4. You are doing other stuff.

Find a good place ;) In doubt mail to cmake-developers@cmake.org and ask for
advise.
Something went wrong with that request. Please try again.