Tuesday
Feb222011
Comparing Unit Test Frameworks
Our goal is to help you find the right fit for your needs. If that's not our particular tools, it does neither of us any good for us to try to oversell our goods. Here's a comparison to other frameworks that seem popular. If there are any errors or omissions that are noteworthy, just let us know:
| Feature | Unity | CppUTest | Google Test | CuTest | Check | MinUnit | CMockery |
|---|---|---|---|---|---|---|---|
| Language | C | C++(4) | C++ | C | C | C | C |
| Can Mock | C(1) | C | C++ | no | no | no | C |
| Auto Runners(2) | YES | no | YES | no | no | no | YES |
| Embeddable? | YES | YES | YES | YES | no(3) | YES | YES |
| Type-Specific Asserts? | YES | no | YES | no | no | no | no |
| Memory Leak Detect? | no | YES | YES | no | no | no | YES |
Notes
- (1) via CMock.
- (2) frameworks without this feature require you to manually add each test to some sort of central list or function. Each time you forget, a test gets missed.
- (3) relies on posix forking, making it unsuitable for many embedded targets.
- (4) uses C++, but still intended to test C.
Tuesday, February 22, 2011 at 7:01AM |
Mark VanderVoord (Dr. Twig) 



