尝试lcut !- http://code.google.com/p/lcut

如果你熟悉JUnit，那么我推荐CppUnit。 http://cppunit.sourceforge.net/cppunit-wiki

这是假设你有c++编译器来做单元测试。如果没有，那么我必须同意亚当·罗森菲尔德的观点，支票就是你想要的。

C语言中的一个单元测试框架是Check;C语言单元测试框架的列表可以在这里找到，并在下面复制。根据运行时具有多少标准库函数，您可以使用其中的一个，也可以不使用。

AceUnit AceUnit (Advanced C and Embedded Unit) bills itself as a comfortable C code unit test framework. It tries to mimick JUnit 4.x and includes reflection-like capabilities. AceUnit can be used in resource constraint environments, e.g. embedded software development, and importantly it runs fine in environments where you cannot include a single standard header file and cannot invoke a single standard C function from the ANSI / ISO C libraries. It also has a Windows port. It does not use forks to trap signals, although the authors have expressed interest in adding such a feature. See the AceUnit homepage. GNU Autounit Much along the same lines as Check, including forking to run unit tests in a separate address space (in fact, the original author of Check borrowed the idea from GNU Autounit). GNU Autounit uses GLib extensively, which means that linking and such need special options, but this may not be a big problem to you, especially if you are already using GTK or GLib. See the GNU Autounit homepage. cUnit Also uses GLib, but does not fork to protect the address space of unit tests. CUnit Standard C, with plans for a Win32 GUI implementation. Does not currently fork or otherwise protect the address space of unit tests. In early development. See the CUnit homepage. CuTest A simple framework with just one .c and one .h file that you drop into your source tree. See the CuTest homepage. CppUnit The premier unit testing framework for C++; you can also use it to test C code. It is stable, actively developed, and has a GUI interface. The primary reasons not to use CppUnit for C are first that it is quite big, and second you have to write your tests in C++, which means you need a C++ compiler. If these don’t sound like concerns, it is definitely worth considering, along with other C++ unit testing frameworks. See the CppUnit homepage. embUnit embUnit (Embedded Unit) is another unit test framework for embedded systems. This one appears to be superseded by AceUnit. Embedded Unit homepage. MinUnit A minimal set of macros and that’s it! The point is to show how easy it is to unit test your code. See the MinUnit homepage. CUnit for Mr. Ando A CUnit implementation that is fairly new, and apparently still in early development. See the CUnit for Mr. Ando homepage. This list was last updated in March 2008.

更多的框架:

CMocka

CMocka是一个支持模拟对象的C语言测试框架。它易于使用和设置。

请参阅CMocka主页。

标准

Criterion是一个跨平台的C单元测试框架，支持自动测试注册、参数化测试和理论，可以输出多种格式，包括TAP和JUnit XML。每个测试都在自己的进程中运行，因此如果需要，可以报告或测试信号和崩溃。

更多信息请参阅Criterion主页。

HWUT

HWUT是一个通用的单元测试工具，支持c语言。它可以帮助创建makefile，生成大量的测试用例，在最小的“迭代表”中编码，运行状态机，生成c语言存根等等。一般的方法是非常独特的:裁决是基于“好标准输出/坏标准输出”。不过，比较函数是灵活的。因此，任何类型的脚本都可以用于检查。它可以应用于任何可以产生标准输出的语言。

请参阅武汉理工大学主页。

CGreen

一个现代的、可移植的、跨语言的C和c++单元测试和模拟框架。它提供了可选的BDD表示法、模拟库和在单个进程中运行它的能力(使调试更容易)。一个自动发现测试函数的测试运行器是可用的。但是您可以通过编程方式创建自己的。

所有这些特性(以及更多)在CGreen手册中都有解释。

维基百科在单元测试框架列表下给出了C单元测试框架的详细列表:C

我说几乎和ratkok一样，但如果你有一个嵌入的扭曲单元测试，那么……

Unity——强烈推荐用于单元测试C代码的框架。

#include <unity.h>

void test_true_should_be_true(void)
{
    TEST_ASSERT_TRUE(true);
}

int main(void)
{
    UNITY_BEGIN();
    RUN_TEST(test_true_should_be_true);
    return UNITY_END();
}

书中提到的嵌入式C线程TDD中的例子是使用Unity(和CppUTest)编写的。

Michael Feather的书《有效地使用遗留代码》介绍了很多专门用于C开发期间单元测试的技术。

有一些与依赖注入相关的技术是特定于C语言的，我在其他任何地方都没有见过。

谷歌拥有优秀的测试框架。https://github.com/google/googletest/blob/master/googletest/docs/primer.md

是的，据我所知，它将与普通C一起工作，即不需要c++功能(可能需要c++编译器，不确定)。