If you’ve been reading my blog over the past few months you’ll know that I’ve written a number of posts related to automated testing. We have our own internal test automation framework so I’ve never really taken a close look at DUnit although having browsed around the SourceForge page for DUnit I’m wondering if the project is still alive/active? This post mentions an update for D2006 back in August stating that a “release version will follow in a few weeks” although the SourceForge pages for DUnit seem very quiet and the bug tracker doesn’t have any recent issues logged against the core. Not to mention that it’s obviously been more than a few weeks since August 1st, which has me wondering what the state of DUnit really is?
Our internal testing framework has a class called TTestManager, written prior to Delphi 1.0, which manages test execution and handles the “accounting” details like how many tests have executed/passed/failed. One of the design goals was to use as small a footprint of the Delphi RTL as possible to give it the best chance to compile and run in the midst of a changing compiler and RTL. Over the years TTestManager has lived up to this goal and served its purpose well though, I think it’s a bit long in the tooth and it may well be time to use something like DUnit. There are a few developers here who have experience using it and I need to sit down with them and get their opinions. One of the biggest problems we have with our tools relates to reporting and the ability to publish test results to the entire team. Again, over the years there have been a multitude of solutions though none of which have been overly effective.
So, this leaves me with the following questions:
- Is the DUnit project still alive?
- What is your impression of DUnit?
- What, if any, changes they would make to it?
- Are you comfortable writing tests with DUnit?
- How do you publish the results of your testing efforts?
FWIW, in January I plan on spending a little time investigating DUnit to see it’s something we should look more closely at.