I was looking for a straightforward C++ unit testing framework, and I found CUTE: C++ Unit Testing Easy. You know what? It’s pretty good. CUTE started in 2006, so unlike the incumbent CppUint, it takes advantage of all the C++ goodness in modern compilers and Boost. There is even a CUTE Eclipse plugin with many of the features of the famous JUnit.
Lately I used CUTE on an application I am enhancing for a client, and it has worked beautifully. Cute is lightweight and orthogonal to the application, so the interaction with CUTE is limited to assertions in the unit tests. The application code needed no modification whatsoever.
While researching CUTE, I found that the most relevant criticism was the lack of practical documentation. Well, I took a good whack at that problem. The CUTE documentation should be better now.
When developing applications on OpenAccess, I do unit testing with the OpenAccess unit testing framework. When the application doesn’t involve OpenAccess, my choice for C++ unit testing is CUTE.
{ 1 comment… read it below or add one }
Meanwhile, I have been encouraged to try the Google Test C++ unit testing framework. So far, I have only read the documentation, but wow! Google Test looks really good. I’ll try that next.