-xn name exclude tests whose name contains the substring name (v3.8).

-xg group exclude tests whose group contains the substring group (v3.8).

-v verbose, print each test name as it runs.

-sn name only run test whose name exactly matches the string name.

-sg group only run test whose group exactly matches the string group.A second run that has no leaks indicates that someone is allocating statics and not releasing them. This is handy if you are experiencing memory leaks. -r# repeat the tests some number (#) of times, or twice if # is not specified.-oteamcity output to xml files (as the name suggests, for TeamCity).-ojunit output to JUnit ant plugin style xml files (for CI systems).-n name only run test whose name contains the substring name.-ln print a list of test names in the form of group.name, separated by spaces.-lg print a list of group names, separated by spaces.-k package name, Add a package name in JUnit output (for classification in CI systems).-g group only run test whose group contains the substring group.-c colorize output, print green if OK, or red if failed.The test execution of this will likely (no guarantee of order in CppUTest) be: To write your first test, all you need is a new cpp file with a TEST_GROUP and a TEST, like: #include 'CppUTest/TestHarness.h' Build with Test-driven Development in mind.

It is written in C++ but is used in C and C++ projects and frequently used in embedded systems. CppUTest is a C /C++ based unit xUnit test framework for unit testing and for test-driving your code.

Years used runonly to avoid detection