Google Test
Google Test and Google Mock are a pair of unit testing tools developed by Google.
Adding Google Test to your project
-
Download Google Test from the official repository and extract the contents of googletest-main into an empty folder in your project (for example, Google_tests/lib ).
Alternatively, clone Google Test as a git submodule or use CMake to download it (instructions below will not be applicable in the latter case).
-
Create a CMakeLists.txt file inside the Google_tests folder: right-click it in the project tree and select .
Customize the following lines and add them into your script:
# 'Google_test' is the subproject name project(Google_tests) # 'lib' is the folder with Google Test sources add_subdirectory(lib) include_directories(${gtest_SOURCE_DIR}/include ${gtest_SOURCE_DIR}) # 'Google_Tests_run' is the target name # 'test1.cpp test2.cpp' are source files with tests add_executable(Google_Tests_run test1.cpp test2.cpp) target_link_libraries(Google_Tests_run gtest gtest_main) -
In your root CMakeLists.txt script, add the
add_subdirectory(Google_tests)command to the end, then reload the project. -
When writing tests, make sure to add
#include "gtest/gtest.h"at the beginning of every .cpp file with your tests code.
Generate menu for Google Test
In the files with
gtest
included, you can generate code for tests and test fixtures using the
Generate
menu
Alt+Insert
.
When called from a fixture, this menu additionally includes SetUp Method and TearDown Method :
Google Test run/debug configuration
Although Google Test provides the
main()
entry, and you can run tests as regular applications, we recommend using the dedicated Google Test run/debug configuration. It includes test-related settings and let you benefit from the built-in
test runner
, which is unavailable if you run tests as regular programs.
-
To create a Google Test configuration, go to Run | Edit Configurations , click
and select
Google Test
from the list of templates.
-
Specify the test or suite to be included in the configuration, or provide a pattern for filtering test names. Auto-completion is available in the fields to help you quickly fill them up:
Set wildcards to specify test patterns, for example:
-
In other fields of the configuration settings, you can set environment variables and command line options. For example, use Program arguments field to pass the
--gtest_repeatflag and run a Google test multiple times:
The output will look as follows:
Repeating all tests (iteration 1) ... Repeating all tests (iteration 2) ...