Gtestdiscovertests (BINARY SRC COMMENT) This allows for it to scan for tests in the source file SRC to run against the binary BINARY with a comment COMMENT at build system generation time. This is great, and we’ve been using it to generate our “make test” command for quite some times. The testdirectory contains a single executable allowing to test the libfooservice using a mockversion of libbar. From Wikipedia: In object-oriented programming, mock objects are simulated objects that mimic the behavior of real objects in controlled ways. For those interested, the.

This module defines functions to help use the Google Test infrastructure. Twomechanisms for adding tests are provided. gtest_add_tests() has beenaround for some time, originally via find_package(GTest).gtest_discover_tests() was introduced in CMake 3.10.

The (older) gtest_add_tests() scans source files to identify tests.This is usually effective, with some caveats, including in cross-compilingenvironments, and makes setting additional properties on tests more convenient.However, its handling of parameterized tests is less comprehensive, and itrequires re-running CMake to detect changes to the list of tests.

The (newer) gtest_discover_tests() discovers tests by asking thecompiled test executable to enumerate its tests. This is more robust andprovides better handling of parameterized tests, and does not require CMaketo be re-run when tests change. However, it may not work in a cross-compilingenvironment, and setting test properties is less convenient.

The gtestdiscovertests command gained a new DISCOVERYMODE keyword in CMake 3.18. This can be used to control whether test discovery is performed at built time or test time (the latter can be important if cross-compiling). Same if I try gtestdiscovertests. I use CMake 3.2-MSVC2 on Windows 10 in VS2019. Should the above be expected to work? Are there downsides to using GTest with vcpkg? Various blog posts recommend including the GTest source directly in a project. I'm unsure if vcpkg accomplishes the same thing.

More details can be found in the documentation of the respective functions.

Both commands are intended to replace use of add_test() to registertests, and will create a separate CTest test for each Google Test test case.Note that this is in some cases less efficient, as common set-up and tear-downlogic cannot be shared by multiple test cases executing in the same instance.However, it provides more fine-grained pass/fail information to CTest, which isusually considered as more beneficial. By default, the CTest test name is thesame as the Google Test name (i.e. suite.testcase); see alsoTEST_PREFIX and TEST_SUFFIX.

Automatically add tests with CTest by scanning source code for Google Testmacros:

gtest_add_tests attempts to identify tests by scanning source files.Although this is generally effective, it uses only a basic regular expressionmatch, which can be defeated by atypical test declarations, and is unable tofully 'split' parameterized tests. Additionally, it requires that CMake bere-run to discover any newly added, removed or renamed tests (by default,this means that CMake is re-run when any test source file is changed, but seeSKIP_DEPENDENCY). However, it has the advantage of declaring tests atCMake time, which somewhat simplifies setting additional properties on tests,and always works in a cross-compiling environment.

The options are:

Specifies the Google Test executable, which must be a known CMakeexecutable target. CMake will substitute the location of the builtexecutable when running the test.

When provided, only the listed files will be scanned for test cases. Ifthis option is not given, the SOURCES property of thespecified target will be used to obtain the list of sources.

Any extra arguments to pass on the command line to each test case.

Specifies the directory in which to run the discovered test cases. If thisoption is not provided, the current binary directory is used.

Specifies a prefix to be prepended to the name of each discovered testcase. This can be useful when the same source files are being used inmultiple calls to gtest_add_test() but with different EXTRA_ARGS.

Similar to TEST_PREFIX except the suffix is appended to the name ofevery discovered test case. Both TEST_PREFIX and TEST_SUFFIX maybe specified.

Normally, the function creates a dependency which will cause CMake to bere-run if any of the sources being scanned are changed. This is to ensurethat the list of discovered tests is updated. If this behavior is notdesired (as may be the case while actually writing the test cases), thisoption can be used to prevent the dependency from being added.

The variable named by outVar will be populated in the calling scopewith the list of discovered test cases. This allows the caller to dothings like manipulate test properties of the discovered tests.

Usage example:

For backward compatibility, the following form is also supported:

The path to the test executable or the name of a CMake target.

A ;-list of extra arguments to be passed to executable. The entirelist must be passed as a single argument. Enclose it in quotes,or pass ' for no arguments.

A list of source files to search for tests and test fixtures.Alternatively, use AUTO to specify that exe is the nameof a CMake executable target whose sources should be scanned.

Automatically add tests with CTest by querying the compiled test executablefor available tests:

New in version 3.10.

gtest_discover_tests() sets up a post-build command on the test executablethat generates the list of tests by parsing the output from running the testwith the --gtest_list_tests argument. Compared to the source parsingapproach of gtest_add_tests(), this ensures that the full list oftests, including instantiations of parameterized tests, is obtained. Sincetest discovery occurs at build time, it is not necessary to re-run CMake whenthe list of tests changes.However, it requires that CROSSCOMPILING_EMULATOR is properly setin order to function in a cross-compiling environment.

Additionally, setting properties on tests is somewhat less convenient, sincethe tests are not available at CMake time. Additional test properties may beassigned to the set of tests as a whole using the PROPERTIES option. Ifmore fine-grained test control is needed, custom content may be providedthrough an external CTest script using the TEST_INCLUDE_FILESdirectory property. The set of discovered tests is made accessible to such ascript via the <target>_TESTS variable.

The options are:

Specifies the Google Test executable, which must be a known CMakeexecutable target. CMake will substitute the location of the builtexecutable when running the test.

Any extra arguments to pass on the command line to each test case.

Specifies the directory in which to run the discovered test cases. If thisoption is not provided, the current binary directory is used.

Specifies a prefix to be prepended to the name of each discovered testcase. This can be useful when the same test executable is being used inmultiple calls to gtest_discover_tests() but with differentEXTRA_ARGS.

Similar to TEST_PREFIX except the suffix is appended to the name ofevery discovered test case. Both TEST_PREFIX and TEST_SUFFIX maybe specified.

By default, the type index of type-parameterized tests is replaced by theactual type name in the CTest test name. If this behavior is undesirable(e.g. because the type names are unwieldy), this option will suppress thisbehavior.

By default, the value index of value-parameterized tests is replaced by theactual value in the CTest test name. If this behavior is undesirable(e.g. because the value strings are unwieldy), this option will suppressthis behavior.

Gtest Cmake

Specifies additional properties to be set on all tests discovered by thisinvocation of gtest_discover_tests().

Make the list of tests available in the variable var, rather than thedefault <target>_TESTS. This can be useful when the same testexecutable is being used in multiple calls to gtest_discover_tests().Note that this variable is only available in CTest.

Specifies how long (in seconds) CMake will wait for the test to enumerateavailable tests. If the test takes longer than this, discovery (and yourbuild) will fail. Most test executables will enumerate their tests veryquickly, but under some exceptional circumstances, a test may require alonger timeout. The default is 5. See also the TIMEOUT option ofexecute_process().

Note

In CMake versions 3.10.1 and 3.10.2, this option was called TIMEOUT.This clashed with the TIMEOUT test property, which is one of thecommon properties that would be set with the PROPERTIES keyword,usually leading to legal but unintended behavior. The keyword waschanged to DISCOVERY_TIMEOUT in CMake 3.10.3 to address thisproblem. The ambiguous behavior of the TIMEOUT keyword in 3.10.1and 3.10.2 has not been preserved.

If specified, the parameter is passed along with --gtest_output=xml:to test executable. The actual file name is the same as the test target,including prefix and suffix. This should be used instead ofEXTRA_ARGS--gtest_output=xml to avoid race conditions writing theXML result output when using parallel test execution.

Gtest Discover Tests

New in version 3.18.

Provides greater control over when gtest_discover_tests() performs testdiscovery. By default, POST_BUILD sets up a post-build commandto perform test discovery at build time. In certain scenarios, likecross-compiling, this POST_BUILD behavior is not desirable.By contrast, PRE_TEST delays test discovery until just prior to testexecution. This way test discovery occurs in the target environmentwhere the test has a better chance at finding appropriate runtimedependencies.

Google Test Cmake

DISCOVERY_MODE defaults to the value of theCMAKE_GTEST_DISCOVER_TESTS_DISCOVERY_MODE variable if it is notpassed when calling gtest_discover_tests(). This provides a mechanismfor globally selecting a preferred test discovery behavior without havingto modify each call site.