N.B. cfix studio was the code name of what has become Visual Assert
There is little doubt that native code, and C and C++ in particular, is here to stay. And still, it is pretty obvious that when it comes to tools and IDEs, it is the managed world that has gotten most attention from tool vendors over the past years.
While there are lots and lots of useful tools for native development, many of them probably even better than their managed counterparts, there are some areas where the managed language fraction is far ahead: One of these areas certainly is IDE support for unit testing.
JUnit for Eclipse, TestDriven.Net for Visual Studio and MS Test make test-driven development so much more convenient and efficient that it is almost ridiculous that using command line tools is still state of the art for C/C++ development.
That said, there is great news: With cfix studio, there finally is a solution filling in this gap! cfix studio, based on the cfix unit testing framework, is a Visual Studio-AddIn that allows you to easily write, manage, run, and debug your unit tests from within Visual Studio. No fiddling with command line tools, complex configuration, or boilerplate code required!
Among lots of other features, cfix studio also has first-class support for multi-architecture development – you can easily switch back and forth between 32-bit and 64-bit and can even mix tests of different architectures in a single test run. Needless to say, cfix studio, like cfix, is also fully compatible to WinUnit.
If that has caught your interest, you are invited to check out the first beta version of cfix studio:
It is free, quick to install and comes with a set of example projects. Give it a try – and please let me know about all your crticism, suggestions and other feedback!
Here are some screenshots of cfix studio in action:
The Test Explorer allows you to start a single or set of tests, the Run Window shows the results
Run Window: Viewing test progress
Run Window: Viewing test results and details of a failed assertion
When running in the debugger, a failed assertion will hit a breakpoint and the Run Window will show additional details« Back to home