I am pleased to notify everyone that a ZIP file of the DUnit changes to
support FASTMM, add some extra functionality and fix some bugs is now
1) FASTMM support, including optional memory leak checking on a per test
basis, resulting in improved execution speed of many tests.
2) Optional checking that each test case calls at least one CheckXXX method.
3) Optional detection of each test case that overrides the global GUI test
4) Optional halting of a repeated test on the first failure.
5) Fully backwards compatibility with older versions of Delphi, DUnit and
FASTMM, i.e. it shouldn't break anything when you install it over your
existing set up!
The file can simply be unzipped over any of the 9.2.x folders as it has all
the recent changes merged, and for those of you who are interested, Delphi
2006 is shipping with 9.2.1, i.e. the most up to date release, although they
named the folder dUnit (somebody was obviously very attached to dBase!)
Please refer to NewTo9.2.x.txt in the main folder for details of what is new
or has been changed, and readme-fastmm.txt for specific instructions for
setting it up with FastMM.
We've tested it with all version of Delphi from 5 through 2006 inclusive, so
those remain the supported versions, and if someone can confirm that Kylix
is still ok that would be greatly appreciated.
Please let us know how it goes, whether well, ok, or badly, and of any
improvements we can make before we check the changes into CVS and give them
a version number.
I also have some simple questions about the default values for certain
1) When you have a significant number of small tests the run speed is
significantly increased if you enable the following:
Hide test nodes on open
Show tested node
For our own benefit we would love to make them the default settings, since
we often delete the DUNIT.INI file to clean up, but what does anyone else
2) Currently the width of the Test Name field is set to a maximum width of
400, and the width of the Message fields is set to a maximum of 800 - are
there any objections to removing those maximums?
3) The new setting 'Fail test case if no checks executed' defaults to False
for backwards compatibility, and should stay so for a while, but should
eventually be defaulted to True - any thoughts?
I've also added a News item on the home page for the DUnit Guidelines for
Change Requests and Contributions that Kristofer added a while back, and we
will try and keep the news more up to date!
That's all for now, other than another big thanks to Peter McNab for
contributing the majority of this!
All the best,
Makers of CodeHealer and SOCKShell