Cmockery tests are compiled into a stand-alone executable and linked with the cmockery library, the standard C library and module being tested. Any symbols external to the module being tested should be mocked - replaced with functions that return values determined by the test - within the test application. Even though significant differences may exist between the target execution environment of a code module and the environment used to test the code the unit testing is still valid since its goal is to test the logic of a code modules at a functional level and not necessarily all of its interactions with the target execution environment.

Other features:

• Lightweight C Unit test with mocking support
• JUnit XML report output which can be used with Jenkins
• Provides design-by-contract support

This project is a successor of http://code.google.com/p/cmockery-staging/ which is a successor of Google's http://code.google.com/p/cmockery/.

• Usage Guide
• Coverage Support with Jenkins

• Devconf 2015