Start with a clean directory: /home/user/Desktop/projects/cpp/ # your project lives here Add your cmake file(CMakeLists.txt), your source files, and test file. The directory now looks like this: └─cpp/ ├─ CMakeLists.txt ├─ myfunctions.h └─ mytests.cpp Clone and add googletest to this directory: └─cpp/ ├─ googletest/ ├─ CMakeLists.txt ├─ myfunctions.h └─ mytests.cpp Open your CMakeLists.txt and enter … Read more
INSTANTIATE_TEST_CASE_P accepts an optional 4th argument which can be used for this purpose. See https://github.com/google/googletest/blob/fbef0711cfce7b8f149aac773d30ae48ce3e166c/googletest/include/gtest/gtest-param-test.h#L444.
The assertion is there to confirm that a function would bring about program termination if it were executed in the current process (the details explains that the death test is invoked from a subprocess which allows the tests to continue despite the death). This is useful because some code may guarantee program termination / abortion … Read more
For Linux environments: It’s simple you just have to set the GTEST_OUTPUT environment variable like this: export GTEST_OUTPUT=”xml:/home/user/src”. or use the -gtest_output flag set the same way.
Yes, you can call EXPECT_CALL on the same mock object multiple times. As long as you assure that all EXPECT_CALL were called before the mocked methods were actually used. Otherwise your test will rely on undefined behavior. From ForDummies: Important note: gMock requires expectations to be set before the mock functions are called, otherwise the … Read more
If you want the latest version without using Homebrew: git clone https://github.com/google/googletest cd googletest mkdir build cd build cmake .. make make install
Create one file that contains just the main to run the tests. // AllTests.cpp #include “gtest/gtest.h” int main(int argc, char **argv) { testing::InitGoogleTest(&argc, argv); return RUN_ALL_TESTS(); } Then put the tests into other files. You can put as many tests as you like in a file. Creating one file per class or per source file … Read more
Try moving -lpthread to after gtest_main.a in your g++ command.
Using Riga’s excellent answer, here is a summary of how I got it to work: Created a new C++ project in Eclipse (I chose Executable > Empty Project) Downloaded googletest 1.5.0, untarred, and ran ./scripts/fuse_gtest_files.py . <project-dir>/contrib Back in Eclipse, excluded the contrib directory from the Release build configuration, and added <project-dir>/contrib to the include … Read more
This is a result of holding p as a shared_ptr, using InSequence and the order in which you have declared your expectations. When you call EXPECT_CALL(*c, myMethod(Eq(p))); you increase the use_count of p. In order for the leak detection to pass, p must be destroyed at (or before) the end of TEST. The problem here … Read more