Re: [Cppunit-devel] CppUnit

[Baptiste L. <bl...@cl...>]

----- Original Message -----
From: "Pratt, Nick" <np...@mi...>
To: <cpp...@li...>
Sent: Tuesday, October 30, 2001 10:34 PM
Subject: [Cppunit-devel] CppUnit


> Hi
>
> We use CppUnit 1.5 in house for NT unit testing. We made some alterations
to
> it, and I was wondering if you want the diffs in case you wish to add them
> into CppUnit 1.6.x (some of the alterations, you may have already
> added/fixed)
>
> The main ones:
>
> + Renamed assert() to TestAssert() so as not to conflict with <assert.h> -
> nothing major, but it was a pain in the ass.

    CppUnit now use CPPUNIT_ASSERT

> + Production code DLLs are now loaded dynamically, so you dont have to
> relink the HostApp everytime you touch a production code DLL. This
> alteration was not a nice one, but it worked. (You can see for yourself).
Im
> not sure of a nice, cross platform way to do this.

    What do you call 'Product code DLL' ? Is the feature you are refering to
similar to the TestPlugIn feature (still experimental) ?

> + When you shut the HostApp down via the Close button, the MFC "Untitled"
> window no longer pops up.

    This has been solved using a Dialog application instead of an MDI
application and never showing up the dialog. A specific application has been
created to run test plug in (TestPlugInRunner).

> + Added a command line parameter which, if specified, causes only that
> production code DLL to be loaded. Not really an issue with only a few DLLs
> in a directory, but when you have a product with several hundred, loading
up
> HostApp could take a long time.

    I still don't get what you are calling 'Production code DLL'.

> + Fixed some issues that Numega Boundschecker was complaining about in a
> release build.

    Those fixs are welcome.

> Removal of the need to use standard C++ RTTI would be a great benefit
since
> not all platforms/compilers support it, and does add runtime overhead. I
> noticed something in the Changelog about RTTI and some macros, but I need
to
> look into the new docs further to see if you have already done this.

    RTTI is not required, but you won't be able to use the TestRunner if you
don't have it. The TestBrowser rely on RTTI to distinguish TestSuite and
TestCase.

    Baptiste.