Skip to main content

Setting up google test and google mock

Google test is a great library that one can use for unit testing. Google mock is an extension of Google test as a mocking framework which can be used to mock the behavior of interfaces. First things first, build the library gmock. I use netbeans.

1. Create a new project  as C/C++ static library
2. Include the files as "Add Existing Item"   ${GTEST_DIR}/src/gtest-all.cc and ${GMOCK_DIR}/src/gmock-all.cc
3. Include the  Directories and Headers for the compiler in project properties. ${GTEST_DIR}/include and ${GMOCK_DIR}/include and  ${GTEST_DIR} and ${GMOCK_DIR}
4. Build.....

Note: It's mentioned that you need -pthread but since we are building a static library, the links are not resolved so you need to only enter them in the application linker properties.

Now you'll end up with the ".a file" in the dist folder.

Now create a new application as a C/C++ project. This project contains your application that should be tested or mocked using Google test framewrok.

You should include the above mentioned 4 folders in the C++ compiler path and includer the gtest library for the linker.

In a test application you create a new test folder under test files (see image) and create a new test file under that folder.
This test file will contain the Google test code grouped as different unit tests.
Now if you right click on "Test Files" and say "Test" the Google tests will be run and their status will be displayed as OK / PASSED or FAILED.

The Google test  framework documentation is vast and I leave the discussion out on how to use the framework for testing and mocking.

Comments

Post a Comment

Popular posts from this blog

Detaching a process from terminal - exec(), system(), setsid() and nohup

Linux processes are created by fork() and exec(). The very first process of POSIX systems is init and subsequent processes are derived from the init as parent. These subsequent processes are child processes. During forking the parent process copies itself - with all I/O, address space, stack, everything. The only thing that is different is the process ID. The parent and child will have 2 different process IDs. The system() library function uses fork(2) to create a child process that executes the shell command specified in command using execl(3) as follows: execl("/bin/sh", "sh", "-c", command, (char *) 0); system() returns after the command has been completed. system() executes a command specified in command by calling /bin/sh -c command , and returns after the command has been completed. During execution of the command, SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored.  system() calls are often made within programs to execut...
Post a Comment
Read more

C++ Callbacks using function pointers vs boost bind +boost function

In C, the most common uses of callbacks are as parameters to library functions like qsort , and as callbacks for Windows functions, etc. For example you might have a library that provides some sorting functions but you want to allow the library user to provide his own sorting function. Since the arguments and the return values do not change depending on the sorting algorithm, this can be facilitated in a convenient manner using function callbacks. Callbacks are also used as event listeners. onMouseClick(), onTerminalInput(), onData(), onConnectionStatus(), onRead() are probably some examples you've already seen in different libraries. The libraries have these callback functions and the users of the library are supposed to implement them. The library has a function pointer to these functions and calls them on their event loop which will invoke the code of the inherited classes of the library user. The implementation of function pointers is simple: they are just "code p...
Post a Comment
Read more

sprintf, snprintf, strcpy, strncpy and sizeof operator

"C library functions such as strcpy (), strcat (), sprintf () and vsprintf () operate on null terminated strings and perform no bounds checking." "snprintf is safer than sprintf" What do these statements really mean? int sprintf ( char * str , const char * format , ... )  int snprintf ( char * s, size_t n, const char * format, ... );  char * strcpy ( char * destination, const char * source ); char * strncpy ( char * destination, const char * source, size_t num );   The usage is something like; char* msg1 = new char[10]; strcpy(msg1, "test"); // 1 char buffer[128]; sprintf(buffer, "%s", msg); //2 strcpy : Copies bytes until it finds a 0-byte in the source code. The string literal "test" has 4 characters and a terminating null character at end, therefore needs 5 characters at least on msg1.  Is this dangerous? Yes, because if the source message is not null terminated it will read until a null character ...
Post a Comment
Read more