Re: [Cppunit-devel] TestCaller interface change

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

As far as I know, all real initialization is done in setUp() and tearOf()
because you need that to be able to rerun the test.

Looking at the unit test I'm writing for Ttr, that's hold true. The
constructor and destructor of the testcase are usually left empty.

Though instead of removing the exisiting constructor, add a new one, so
people relying on that one won't have any problem.

It would also probably allow some nifty thing (having the same test run with
different setting or something like that).

I would also add a "void setFixture( Fixture *fixture)" method. So you could
write a decorator that iterates among a list of fixture and repeat the test
for each one.

----- Original Message -----
From: "Bastiaan Bakker" <bas...@li...>
To: <cpp...@li...>
Sent: Sunday, May 06, 2001 3:32 PM
Subject: [Cppunit-devel] TestCaller interface change


> Hi all,
>
> Baptiste's BoardGameTest problem, got me to look into TestCaller
> mechanism. As far as I can see, the main cause of the trouble is that
> every TestCaller constructs its own Fixture instance.
> I don't see any reason for that, so I'd like to change TestCaller to
> accept a reference to an existing TestCase.
> Please let me know if I'm wrong :-)
>
> Bastiaan
>
>
>
>
>
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> http://lists.sourceforge.net/lists/listinfo/cppunit-devel
>