Re: [Cppunit-devel] include directory clean-up

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

Well, now for the last part ;-)

----- Original Message -----
From: "Steve M. Robbins" <ste...@vi...>
To: <cpp...@li...>
Sent: Thursday, June 14, 2001 5:16 PM
Subject: Re: [Cppunit-devel] include directory clean-up


> On Thu, Jun 14, 2001 at 04:39:41PM +0200, Baptiste Lepilleur wrote:
> >   textui/: text based TestRunner
> >     TestRunner.h  (within the CppUnit::TextUi namespace, was
TextTestRunner.h)
> >   mfcui/: MFC based TestRunner
> >     TestRunner.h  (within the CppUnit::MfcUi namsepace, was
> > msvc6/TestRunner/TestRunner.h )
>
> Here, the directory structure is intended to mirror the namespace
> structure, right?  I wonder what is intended to be in the
> CppUnit::<UI> namespace.  Currently, there is only TestRunner; are
> more classes envisioned?  If not, we'd be creating multiple <UI>
> namespaces with a single member each.  That doesn't sound right.  Why
> not create a TestRunner base class, with specializations for each UI?
   Well, for the TextUi I can't see anymore classes coming. We are limited
by portability which means no RTTI and therefore no test hierarchy browsing
(we could still add a "dump" test hierarchy option).
   For the MfcUi, I have restricted the "published" part to the strict
minimum because the other parts are evolving a lot. But ultimately, we
should reach a well factored and solid TestRunner that allow subclassing.
The dialog, and the models would be published and the user could subclass
them.
   For example, I have planned a "detail" feature, that show the detail
about the selected failure in the list. For a basic "Exception" failure, you
would just have larger text fields to read them properly. For the
"NotEqualException", you would have two text fields to compare the
"expected" and "actual" value (with a nice diff option of course ;-) ).
  When the user extends the framework by subclassing Exception, the user
should be able to provide a new "detail" view for that exception. This is a
very far goal, but one none the less.
  Closer goal, would be to be able to subclass the TestRunnerModel (being
worked on, it is a model that contains the list of test failure reported in
the list), so the user could add functionnalities, such as the time is took
for each test to run, write a duplicate of the failure to a file...
  It's going on slowly (I'm not a MFC expert), but certainly.

  As a alternative for the directories, we could have:
  include/
     cppunit/
     cppunitui/
        mfc/
        text/

  I think I like that one better,
  Baptiste.

---
Baptiste Lepilleur <gai...@fr...>   http://gaiacrtn.free.fr/index.html
Author of The Text Reformatter, a tool for fanfiction readers and writers.
Language: English, French (Well, I'm French).