Nothing. That's the way I usually test my C code.
It has the drawback that one failing test aborts the whole program. The error messages are not the most informative, but it does the job.
It has the drawback that one failing test aborts the whole program. The error messages are not the most informative, but it does the job.
assert(test_foo() /* Checks the sanity of Foo */);
I prefer the regular assert() though because I want the build to fail by an aborting test program, and all I care is the line number of failure. Another benefit is that abort() will pause gdb in the exact place that it crashed, with the stack intact if you want to inspect it.
assert(("test_foo() should be true", test_foo()));
assert(condition && "message");