Comments on: C++ Unit Testing Frameworks http://www.alittlemadness.com/2006/09/26/c-unit-testing-frameworks/ A man needs a little madness, or else he never dares cut the rope and be free. -Nikos Kazantzakis Fri, 03 Feb 2012 00:04:23 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Steven http://www.alittlemadness.com/2006/09/26/c-unit-testing-frameworks/comment-page-1/#comment-132116 Steven Mon, 10 Nov 2008 14:16:05 +0000 http://www.alittlemadness.com/?p=46#comment-132116 A rather new, yet interesting tool is cfix (http://cfix.sourceforge.net/) -- it is for Windows only, but allows tests to be written in a very clean manner... I tend to find it a lot more convenient to use than, for example, CppUnit. --Steven A rather new, yet interesting tool is cfix (http://cfix.sourceforge.net/) — it is for Windows only, but allows tests to be written in a very clean manner… I tend to find it a lot more convenient to use than, for example, CppUnit.

–Steven

]]> By: Gail Nagle http://www.alittlemadness.com/2006/09/26/c-unit-testing-frameworks/comment-page-1/#comment-117301 Gail Nagle Fri, 12 Sep 2008 22:11:55 +0000 http://www.alittlemadness.com/?p=46#comment-117301 Follow-on to my last post - the culprit is Qt not cxxtest. If Qt is linked in, no output ever goes to the build window when running from a post-build event. But there is a neat addition to cxxtest OutputDebugStringPrinter.h that can be downloaded from http://sourceforge.net/tracker/index.php?func=detail&aid=1161786&group_id=52834&atid=468189. This is not as nice as the post build event since it requires that the test be run by Debug->Start or triangular icon in the tool bar, but the test output will now go to the Build window. And you can double click an error and it will go right to the correct line in the test file. Follow-on to my last post – the culprit is Qt not cxxtest. If Qt is linked in, no output ever goes to the build window when running from a post-build event. But there is a neat addition to cxxtest OutputDebugStringPrinter.h that can be downloaded from http://sourceforge.net/tracker/index.php?func=detail&aid=1161786&group_id=52834&atid=468189. This is not as nice as the post build event since it requires that the test be run by Debug->Start or triangular icon in the tool bar, but the test output will now go to the Build window. And you can double click an error and it will go right to the correct line in the test file.

]]> By: Gail Nagle http://www.alittlemadness.com/2006/09/26/c-unit-testing-frameworks/comment-page-1/#comment-115790 Gail Nagle Fri, 05 Sep 2008 03:26:32 +0000 http://www.alittlemadness.com/?p=46#comment-115790 I would really like to know how you got any output from the post-build event to show up in the output window (i.e. the compile window in VS). I get no output there even though when run in a cmd shell the test executable runs fine. This is true whether or not a test passes or fails. I am using the ParenPrinter output formatter. Also, I am using VS.NET 2003. Thanks for any help you can provide. I would really like to know how you got any output from the post-build event to show up in the output window (i.e. the compile window in VS). I get no output there even though when run in a cmd shell the test executable runs fine. This is true whether or not a test passes or fails. I am using the ParenPrinter output formatter. Also, I am using VS.NET 2003. Thanks for any help you can provide.

]]> By: DJW http://www.alittlemadness.com/2006/09/26/c-unit-testing-frameworks/comment-page-1/#comment-49425 DJW Fri, 14 Dec 2007 09:43:25 +0000 http://www.alittlemadness.com/?p=46#comment-49425 Indeed, what did happen with most of the frameworks' development during 2004? Indeed, what did happen with most of the frameworks’ development during 2004?

]]> By: Jason http://www.alittlemadness.com/2006/09/26/c-unit-testing-frameworks/comment-page-1/#comment-2232 Jason Tue, 26 Sep 2006 07:57:02 +0000 http://www.alittlemadness.com/?p=46#comment-2232 Indeed, output formats are key for tool integration. Suprisingly, few frameworks seem to support an easily processed output format (e.g. XML reports) out of the box. These are great for reading results into other tools, or rendering as HTML. Indeed, output formats are key for tool integration. Suprisingly, few frameworks seem to support an easily processed output format (e.g. XML reports) out of the box. These are great for reading results into other tools, or rendering as HTML.

]]> By: martinus http://www.alittlemadness.com/2006/09/26/c-unit-testing-frameworks/comment-page-1/#comment-2213 martinus Mon, 25 Sep 2006 17:41:09 +0000 http://www.alittlemadness.com/?p=46#comment-2213 We have been using CxxTest for some time, and are quite happy with it. We integrated the unit tests in a post-build event in Visual Studio. This has the advantage that the test console output is directly written into the visual studio's compile window, and when using the right logger formatter you can doubleclick on the error message to jump directly to the problematic assert code. We have been using CxxTest for some time, and are quite happy with it. We integrated the unit tests in a post-build event in Visual Studio. This has the advantage that the test console output is directly written into the visual studio’s compile window, and when using the right logger formatter you can doubleclick on the error message to jump directly to the problematic assert code.

]]>