The docs for Google Test 1.7 suggest: If you have a broken test that you cannot fix right away, you can add the DISABLED_ prefix to its name. This will exclude it from execution. This is better than commenting out the code or using #if 0, as disabled tests are still compiled (and thus won’t … Read more
Per your comments, you have a C++ console application (MyApp) for which you have developed some application-specific classes that you want to unit-test with googletest in Visual Studio. How? As you say, if you wanted to unit-test a library the way to do it would be obvious. You would: 1) Create a project to create … Read more
I would really suggest looking at Google C++ Mocking Framework. Even if you don’t want to mock anything, it allows you to write rather complicated assertions with ease. For example //checks that vector v is {5, 10, 15} ASSERT_THAT(v, ElementsAre(5, 10, 15)); //checks that map m only have elements 1 => 10, 2 => 20 … Read more
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
You could use advanced options to run Google tests. To run only some unit tests you could use –gtest_filter=Test_Cases1* command line option with value that accepts the * and ? wildcards for matching with multiple tests. I think it will solve your problem. UPD: Well, the question was how to run specific test cases. Integration … Read more
The error message is clear – you should also specify build directory for googletest. # This will build googletest under build/ subdirectory in the project’s build tree add_subdirectory( ${GOOGLETEST_PROJECT_LOCATION} build) When you give relative path (as a source directory) to add_subdirectory call, CMake automatically uses the same relative path for the build directory. But in … Read more
You need to specify -pthread after -lgtest. The linker takes libraries in order, and only takes as much as it needs to resolve references which are undefined at that point.
I found myself in the same situation lately. I had to write unit tests for libraries written in C, which in turn had dependencies to other libraries also written in C. So I wanted to mock all function calls of dependencies using gmock. Let me explain my approach by an example. Assume the code to … Read more
So there is the macro option @Tsyvarev mentioned that was originally suggested here: # overwrite install() command with a dummy macro that is a nop macro (install) endmacro () # configure build system for external libraries add_subdirectory(external) # replace install macro by one which simply invokes the CMake install() function with the given arguments macro … Read more
Before you start make sure your have read and understood this note from Google! This tutorial makes using gtest easy, but may introduce nasty bugs. 1. Get the googletest framework wget https://github.com/google/googletest/archive/release-1.8.0.tar.gz Or get it by hand. I won’t maintain this little How-to, so if you stumbled upon it and the links are outdated, feel … Read more