test/tests/gtests/CMakeLists.txt

# SPDX-FileCopyrightText: 2014-2022 Blender Authors
#
# SPDX-License-Identifier: GPL-2.0-or-later

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
  if(WITH_TESTS_SINGLE_BINARY)
    add_subdirectory(runner)
  endif()

  # Build utility library used by test executables
  add_subdirectory(testing)
endif()
License Headers: Set copyright to "Blender Authors", add AUTHORS Listing the "Blender Foundation" as copyright holder implied the Blender Foundation holds copyright to files which may include work from many developers. While keeping copyright on headers makes sense for isolated libraries, Blender's own code may be refactored or moved between files in a way that makes the per file copyright holders less meaningful. Copyright references to the "Blender Foundation" have been replaced with "Blender Authors", with the exception of `./extern/` since these this contains libraries which are more isolated, any changed to license headers there can be handled on a case-by-case basis. Some directories in `./intern/` have also been excluded: - `./intern/cycles/` it's own `AUTHORS` file is planned. - `./intern/opensubdiv/`. An "AUTHORS" file has been added, using the chromium projects authors file as a template. Design task: #110784 Ref !110783. 2023-08-16 00:20:26 +10:00			`# SPDX-FileCopyrightText: 2014-2022 Blender Authors`
License headers: use SPDX-FileCopyrightText for CMake files 2023-06-14 22:49:59 +10:00			`#`
File headers: use SPDX license for CMake files 2022-02-11 14:23:56 +11:00			`# SPDX-License-Identifier: GPL-2.0-or-later`
GTest unit testing framework Currently covers only small set of functionality. 2014-06-18 22:49:17 +10:00
Some WITH_TESTS weer not renamed to WITH_GTEST 2014-06-18 22:28:27 +06: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 10:42:32 -07: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 22:49:17 +10: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 16:43:42 +02:00			`# Build common test executable used by most tests`
Tests: add option to build one binary per GTest file Bundling many tests in a single binary reduces build time and disk space usage, but is less convenient for running individual tests command line as filter flags need to be used. This adds WITH_TESTS_SINGLE_BINARY to generate one executable file per source file. Note that enabling this option requires a significant amount of disk space. Due to refactoring, the resulting ctest names are a bit different than before. The number of tests is also a bit different depending if this option is used, as one uses gtests discovery and the other is organized purely by filename, which isn't always 1:1. Co-authored-by: Sergey Sharybin <sergey@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/114604 2024-01-03 18:35:50 +01:00			`if(WITH_TESTS_SINGLE_BINARY)`
			`add_subdirectory(runner)`
			`endif()`
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 12:58:49 +02:00
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 16:43:42 +02:00			`# Build utility library used by test executables`
GTest unit testing framework Currently covers only small set of functionality. 2014-06-18 22:49:17 +10:00			`add_subdirectory(testing)`
			`endif()`