1
0
mirror of synced 2024-12-22 20:50:00 +01:00
modern-cmake/chapters/testing.md

52 lines
1.5 KiB
Markdown
Raw Normal View History

2017-10-21 18:03:43 -04:00
# Testing
## General Testing Information
2018-03-29 19:30:00 +02:00
In your main CMakeLists.txt you need to add the following function call (not in a subfolder):
2017-10-21 18:03:43 -04:00
2018-12-05 18:21:01 +00:00
```cmake
include(CTest)
```
Which will enable testing and set a `BUILD_TESTING` option so users can turn testing on and off (Along with [a few other things](https://gitlab.kitware.com/cmake/cmake/blob/master/Modules/CTest.cmake)). Or you can do this yourself:
2017-10-21 18:03:43 -04:00
```cmake
2018-03-29 19:30:00 +02:00
enable_testing()
2017-10-21 18:03:43 -04:00
```
2018-03-30 15:15:37 +02:00
You can register targets with:
```cmake
add_test(NAME TestName COMMAND TargetName)
```
If you put something else besides a target name after COMMAND, it will register as a command line to run. It would also be valid to put the generator expression:
```cmake
add_test(NAME TestName COMMAND $<TARGET_FILE:${TESTNAME}>)
```
which would use the output location (thus, the executable) of the produced target.
2017-10-21 18:03:43 -04:00
2018-04-05 14:54:25 +02:00
## Building as part of a test
If you want to run CMake to build a project as part of a test, you can do that too (in fact, this is how CMake tests itself). For example, if your master project was called `MyProject` and you had an `examples/simple` project that could build by itself, this would look like:
```cmake
add_test(
NAME
ExampleCMakeBuild
COMMAND
"${CMAKE_CTEST_COMMAND}"
--build-and-test "${My_SOURCE_DIR}/examples/simple"
"${CMAKE_CURRENT_BINARY_DIR}/simple"
--build-generator "${CMAKE_GENERATOR}"
--test-command "${CMAKE_CTEST_COMMAND}"
)
```
## Testing Frameworks
2018-03-29 19:30:00 +02:00
Look at the subchapters for recipes for popular frameworks.