Is Google Test OK for testing C code?

So I've come to like and enjoy using Google Test for a C++ project I'm involved in. I'm just bringing up a new project that will be straight C (a library) and so far can't see any reason why not to continuing using Google Test, even though its a C++ framework. Having a C++ compiler available will not be an issue.

Are there are specific reasons why I shouldn't use Google Test for testing straight C code?

Thanks.

It is pretty common to test C code using a C++ testing frameworks, even the leading book on the subject follows this approach. I have used googletest extensively in the past to unit test C code and can recommend it.

I have written a blog post about it that might be useful: http://meekrosoft.wordpress.com/2009/11/09/unit-testing-c-code-with-the-googletest-framework/

As all Google's C++ code, Google Test does not use exceptions, so exception safety flow won't be an issue. As long as your headers are C++-compatible (not using C++ keywords, export symbols with correct linkage), it should be fine.

Jason, be aware of that!!! :D

As Meekrosoft said, yes, it is possible. I also used his website when I tried to do that. It works, but there is one big problem:

GTest is objected oriented tool and C language isn't!

In example, in GTest you have a lot of functions (80% of whole API) that request object as parameter, for example:

EXPECT_CALL(turtle, PenDown())              // turtle is object(class) and PenDown() is method of that object
      .Times(AtLeast(1));

from GTest website https://code.google.com/p/googlemock/wiki/ForDummies so you will use only macros like expect_equal, expect_bigger_than and so on...

I would like to suggest you tool CMocka (or some other C unit testing tools). It is also from google (modified by group of non-google developers) and it is created directly for C language. I use this one when I want to test C-type source code.

I hope this helps.. :-) Have a nice day.. :-)

I just thought I'd add another point: since gtest is C++, you'll be parsing your C headers under test as C++. This means the tests don't guarantee that the headers are consumable from C. I recently ran into this with a C library I'm building.