> pretty doctrinaire about And that is the problem. I have met teams that have gone into analysis paralysis about which unit test framework to use. I have me

> pretty doctrinaire about And that is the problem. I have met teams that have gone into analysis paralysis about which unit test framework to use. I have met teams where one of the impediments to unit testing was "we don't have time to learn something that complicated, we don't understand why all this stuff is necessary". Answer: It isn't necessary. Get off your ass and start unit testing with the simplist framework possible. It's more important, way way more important to just do it than fuss about the framework. Like TFA. Once you have actually done that for awhile, someone will say, "Wouldn't it be nice if..." And _that's_ the time to introduce a framework. Or grow what you have. On a C project I elected to grow, the nice thing about it is test setup and teardown? It's exactly the same thing as process set up and teardown. So valgrind will tell you _exactly_ if anything leaked or was uninitialized!