Thread: [Cppunit-devel] Test hierarchies?
Brought to you by:
blep
From: Stanley S. <su...@t-...> - 2001-10-22 21:52:24
|
Is there a way to build test hierachies, other than creating seperate suites? I ddidn't see an obvous way in the documentation. For example, I'd like to report all the constructor/destructor tests together, accessor/mutators together, ... -- Stanley M. Sutton sms...@ie... su...@t-... TSurf Corporation - The gOcad Company - http://www.t-surf.com 11011 Richmond Ave. Suite 350 Houston TX 77042 Phone: (1) 713 787 0746 ext. 13 Fax: (1) 713 787 0852 --------------------------------------------------------------------- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin |
From: Baptiste L. <bl...@cl...> - 2001-11-04 12:36:31
|
----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "CppUnit Developers" <cpp...@li...> Sent: Monday, October 22, 2001 10:42 PM Subject: [Cppunit-devel] Test hierarchies? > Is there a way to build test hierachies, other than creating seperate > suites? I ddidn't see an obvous way in the documentation. For example, > I'd like to report all the constructor/destructor tests together, > accessor/mutators together, ... No. Why do you want to group constructor/destructor tests together ? Having per 'component' feedback seems more useful to me, specially when you only want to run the test for a specific component... 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). |
From: Stanley S. <su...@t-...> - 2001-11-05 16:31:10
|
Baptiste Lepilleur wrote: > > ----- Original Message ----- > From: "Stanley Sutton" <su...@t-...> > > > Is there a way to build test hierachies, other than creating seperate > > suites? I ddidn't see an obvous way in the documentation. For example, > > I'd like to report all the constructor/destructor tests together, > > accessor/mutators together, ... > > No. > > Why do you want to group constructor/destructor tests together ? Having > per 'component' feedback seems more useful to me, specially when you only > want to run the test for a specific component... > > 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). > Mostly because that is the typical way I develop classess. Constructors/Destructors first, then test, then accessor/mutators, then test, then operators, then test, ... I'm also looking at changing the code to allow verbose reporting of the tests for logging purposes, so that each test is listed by name, and success/failure is reported. -- Stanley M. Sutton sms...@ie... su...@t-... TSurf Corporation - The gOcad Company - http://www.t-surf.com 11011 Richmond Ave. Suite 350 Houston TX 77042 Phone: (1) 713 787 0746 ext. 13 Fax: (1) 713 787 0852 --------------------------------------------------------------------- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin |
From: Baptiste L. <gai...@fr...> - 2001-11-05 16:46:54
|
Quoting Stanley Sutton <su...@t-...>: > Baptiste Lepilleur wrote: > > > > ----- Original Message ----- > > From: "Stanley Sutton" <su...@t-...> > > > > > Is there a way to build test hierachies, other than creating > seperate > > > suites? I ddidn't see an obvous way in the documentation. For > example, > > > I'd like to report all the constructor/destructor tests together, > > > accessor/mutators together, ... > > > > No. > > > > Why do you want to group constructor/destructor tests together ? > Having > > per 'component' feedback seems more useful to me, specially when you > only > > want to run the test for a specific component... > > > > 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). > > > Mostly because that is the typical way I develop classess. > Constructors/Destructors first, then test, then accessor/mutators, > then > test, then operators, then test, ... OK. Still, why do you want to group those together ? To isolate dependency ? > I'm also looking at changing the code to allow verbose reporting of > the > tests for logging purposes, so that each test is listed by name, and > success/failure is reported. The XmlOutputter of the current CVS report both sucess and failure. Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html Language: English, French |