Don't have a ton of code or test cases yet - just three months into a startup with four developers.<p>Looking for something relatively lightweight, with a small learning curve, that can keep us honest for the next year or two. I've used CppUnit in the past. Didn't hate it. Wondering if there's something better.<p>Do you have opinions on this? Looking for your war stories, whether good, bad, or plain ugly.
I don't know what special needs a startup has. I've used Catch and been happy with it. I haven't used CppUnit, so I can't compare.<p><a href="https://github.com/philsquared/Catch" rel="nofollow">https://github.com/philsquared/Catch</a><p>Previous HN discussion (with some other suggestions):<p><a href="https://news.ycombinator.com/item?id=8220352" rel="nofollow">https://news.ycombinator.com/item?id=8220352</a><p>and a relevant StackOverflow thread:<p><a href="https://stackoverflow.com/questions/87794/c-unit-testing-framework" rel="nofollow">https://stackoverflow.com/questions/87794/c-unit-testing-fra...</a>
I really enjoy CppUTest. It was written by James Grenning who is one brilliant engineer if you ask me. He also wrote the fantastic book "Test Driven Development for Embedded C" which I would highly recommend to anyone, even non-embedded developers.<p>I used CppUTest on a c++ project to test algorithms for image and video manipulation. It worked fantastically, very easy to learn, and it helped test drive and optimize the algorithms. Highly recommended.<p>Edit: fixed typos, typing on phones is hard.
I am a heavy user of gtest. I like to integrate it with CMake and CTest, then use ctest --verbose in the build and release process, with lib_gtest.a linked against test commands specified for CTest.