Setting up googlemock with Visual C++ 2010 Express Edition

Posted on March 15, 2012 by Niall Cooling

Following on from my last post about setting up googletest to use with Visual Studio 2010 express edition, this post builds on that by showing how to build, setup and test the googlemock libraries.

If you have read the previous post, then the basic steps are very similar.

First, download the googlemock zip file and unzip it to known location. As before, I suggest something easy, either C:\gmock-1.6.0, or as in my case C:\src\gmock-1.6.0. One useful fact is that all the gtest code is included as part of the gmock distribution. It can be found at \gmock-1.6.0\gtest.

Building the gtest libraries

It is the same process as build the gtest libraries. One importany note is that

The gmock libraries contain all the gtest code as well.

Navigate to the directory \gmock-1.6.0\msvc\2010 and open the Visual C++ project gmock (gmock.sln). You will end up with three projects.

image

Go ahead and build these (F7) and ignore any warnings. Once successfully built, look in the directory \gmock-1.6.0\msvc\2010\gtest\Debug and you will find two library files

  • gmock.lib
  • gmock_main.lib

Test the GMock Library

As part of the standard build two executable are created that allow a quick self-test of googlemock (gtest does have the same but I neglected to mention those in my previous post).

I recommend opening a command window and navigating to directory  \gmock-1.6.0\msvc\2010\Debug. There you will fine the file gmock_test.exe; go ahead and execute that [NOTE: I had two (of the 830) tests fail, which I’m not sure why (yet) – to be investigated]

image
This indicates that (most of) gmock functions correctly.

Building a Base GMock Project

A gmock project is the same as  a gtest project but with different project properties. Create a newWin32 Console Application  project.  Add a test fixture file to the project:

testFixture.cpp
  1. #include “gtest/gtest.h”
  3. TEST(setup_test_case, testWillPass)
  4. {
  5.     EXPECT_EQ(42, 42);
  6. }
  8. TEST(setup_test_case, testWillFail)
  9. {
  10.     EXPECT_EQ(42, 0);
  11. }

and exclude file containing default main from build.

Modify the project properties (Alt+F7) as follows:

  • Set gmock and gtest header include directories
    • C/C++ -> General -> Additional Include Directories
      • \gmock-1.6.0\include
      • \gmock-1.6.0\gtest\include
  • Add gmock libraries (instead of gtest libs)
    • Linker -> General -> Addition Library Directories
      • \gmock-1.6.0\msvc\2010\Debug
    • Linker -> Input -> Additional Dependencies
      • gmock.lib
      • gmock_main.lib
  • Modify Runtime Library:
    • C/C++ -> Code Generation -> Runtime Library
      • Multi-threaded Debug (/MTd).

Note here that we don’t have to include the gtest libraries as these are embedded in the gmock libraries. Build and run and we will see the familiar gtest output:
image

To test the gmock setup we need to create two classes:

  • The class to become the Unit-Under-Test (UUT)
  • An interface class that the UUT calls upon, which doesn’t have any implementation (or the implementation is target/hardware specific).

Interface Class

IWidget.h
  1. class IWidget
  2. {
  3. public:
  4.     virtual void On() = 0;
  5.     virtual void Off() = 0;
  6. };

Unit Under Test

WidgetController.h
  1. class IWidget;
  3. class WidgetController
  4. {
  5. public:
  6.     WidgetController(IWidget& w);
  7.     ~WidgetController(void);
  8.     void exec();
  9. private:
  10.     IWidget& myWidget;
  11. };
WidgetController.cpp
  1. #include “WidgetController.h”
  2. #include “IWidget.h”
  4. WidgetController::WidgetController(IWidget& w):myWidget(w)
  5. {
  6.     myWidget.Off();
  7. }
  9. WidgetController::~WidgetController()
  10. {
  11.     myWidget.Off();
  12. }
  14. void WidgetController::exec()
  15. {
  16.     myWidget.On();
  17. }

Testing using the Mock framework

To test using the Mock we need to:

  1. Include the gmock header [line 3]
  2. Create a mock class derived from the Interface class [lines 7-12]
  3. Create a test where the UUT calls on the interface on the mock object [lines 16-23]
  4. Set the mock objects expectation [line 20]. The mock expectation is that the Off member function will be called twice, once during WidgetController construction and once during destruction.
Using the mock
  1. // testFixture.cpp
  2. #include “gtest/gtest.h”
  3. #include “gmock/gmock.h”
  5. #include “IWidget.h”
  7. class MockWidget : public IWidget
  8. {
  9. public:
  10.     MOCK_METHOD0(On, void());
  11.     MOCK_METHOD0(Off, void());
  12. };
  14. #include “WidgetController.h”
  16. TEST(TestWidgetController, testConstructor)
  17. {
  18.     MockWidget mw;
  20.     EXPECT_CALL(mw, Off()).Times(2);
  22.     WidgetController wc(mw);
  23. }

Build and run

image

You can see gmock in action by simply changing the expectation, e.g. [line 6]

Failing Test
  1. TEST(TestWidgetController, testConstructor)
  2. {
  3.     MockWidget mw;
  5. //    EXPECT_CALL(mw, Off()).Times(2);
  6.     EXPECT_CALL(mw, Off());
  8.     WidgetController wc(mw);
  9. }

will result in the following failed test output:

image

Where next?

Once you have a working project, the documentation on the Googlemock site is excellent. Start with Googlemock for Dummies.

Niall Cooling
Latest posts by Niall Cooling (see all)
Dislike (0)
Niall Cooling
Website | + posts

Co-Founder and Director of Feabhas since 1995.
Niall has been designing and programming embedded systems for over 30 years. He has worked in different sectors, including aerospace, telecomms, government and banking.
His current interest lie in IoT Security and Agile for Embedded Systems.

About Niall Cooling

Co-Founder and Director of Feabhas since 1995. Niall has been designing and programming embedded systems for over 30 years. He has worked in different sectors, including aerospace, telecomms, government and banking. His current interest lie in IoT Security and Agile for Embedded Systems.
This entry was posted in C/C++ Programming, Testing and tagged , . Bookmark the permalink.

2 Responses to Setting up googlemock with Visual C++ 2010 Express Edition

  1. Chris says:
    March 15, 2012 at 4:11 pm

    Oof. I've been thinking about moving (part of) our group to a dual-target, test-as-you-go kinda system rather than our current ad-hoc style.

    I'm a little worried about the first couple times we try it because I know setting up the dual-target environment is going to be time consuming, but I'm sick of finding missed corner cases 3 months into hardware integration where they start pushing the schedule out.

    Thanks for the link to the Grenning book, the excerpts look like they have some good advice to get me started.

    Like (0)
    Dislike (0)
  2. matt says:
    November 11, 2015 at 4:09 pm

    if anyone has a problem building the gmock solution itself, that is can't generate the .lib files, this did it for me:

    https://groups.google.com/forum/#!topic/googlemock/FaEAHedxpAQ

    there was an outdated GTestDir definition in gmock_config.props, a change from "../../gtest" to "../../../googletest" did it. At least the libs were compiled, i still got the gmock_test error though.

    Like (0)
    Dislike (1)

Leave a Reply