blender/tests/gtests/CMakeLists.txt


if(WITH_GTESTS)
  # Otherwise we get warnings here that we can't fix in external projects
  remove_strict_flags()

  # Build common test executable used by most tests
  add_subdirectory(runner)

  # Build utility library used by test executables
  add_subdirectory(testing)
endif()
GTest unit testing framework Currently covers only small set of functionality. 2014-06-18 12:49:17 +00:00
Some WITH_TESTS weer not renamed to WITH_GTEST 2014-06-18 16:28:27 +00:00			`if(WITH_GTESTS)`
Cleanup: Spelling Mistakes This patch fixes many minor spelling mistakes, all in comments or console output. Mostly contractions like can't, won't, don't, its/it's, etc. Differential Revision: https://developer.blender.org/D11663 Reviewed by Harley Acheson 2021-06-22 17:42:32 +00:00			`# Otherwise we get warnings here that we can't fix in external projects`
GTest unit testing framework Currently covers only small set of functionality. 2014-06-18 12:49:17 +00:00			`remove_strict_flags()`

Tests: move remaining gtests into their own module folders And make them part of the blender_test runner. The one exception is blenlib performance tests, which we don't want to run by default. They remain in their own executable. Differential Revision: https://developer.blender.org/D8498 2020-08-07 14:43:42 +00:00			`# Build common test executable used by most tests`
T73268: Link C/C++ unit tests into single executable This commit introduces a new way to build unit tests. It is now possible for each module to generate its own test library. The tests in these libraries are then bundled into a single executable. The test executable can be run with `ctest`. Even though the tests reside in a single executable, they are still exposed as individual tests to `ctest`, and thus can be selected via its `-R` argument. Not yet ported tests still build & run as before. The following rules apply: - Test code should reside in the same directory as the code under test. - Tests that target functionality in `somefile.{c,cc}` should reside in `somefile_test.cc`. - The namespace for tests is the `tests` sub-namespace of the code under test. For example, tests for `blender::bke` should be in `blender::bke:tests`. - The test files should be listed in the module's `CMakeLists.txt` in a `blender_add_test_lib()` call. See the `blenkernel` module for an example. Reviewed By: brecht Differential Revision: https://developer.blender.org/D7649 2020-07-16 10:58:49 +00:00			`add_subdirectory(runner)`

Tests: move remaining gtests into their own module folders And make them part of the blender_test runner. The one exception is blenlib performance tests, which we don't want to run by default. They remain in their own executable. Differential Revision: https://developer.blender.org/D8498 2020-08-07 14:43:42 +00:00			`# Build utility library used by test executables`
GTest unit testing framework Currently covers only small set of functionality. 2014-06-18 12:49:17 +00:00			`add_subdirectory(testing)`
			`endif()`