Sweet! Guess I need to brush up on my documentation reading skills:(
I will use this pattern a lot so I will overload ServletTestSuite to
allow a string to be passed in and hide the details.
Public class DeluxeTestSuite extends ServletTestSuite
{
public DeluxeTestSuite(Class suite) {...}
public void addTest(String test) { ... }
}
Thanks
-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 20, 2005 10:28 AM
To: 'Cactus Users List'
Subject: RE: Execution Order
> -----Original Message-----
> From: Rod Macpherson [mailto:[EMAIL PROTECTED]
> Sent: mardi 20 septembre 2005 19:13
> To: Cactus Users List
> Subject: RE: Execution Order
>
> I'll take another look but I was looking for individual test method
> ordering. I looked at the suite, in fact that's what I use exclusively
> is suites, but it was the ordering of the testXXX methods withing that
> suite that seemed not to be supported. addTestSuite takes a class not
> a method name, 'less I have missed something.
>
> How do you order the individual testXXX methods without creating a
> class for every method? I didn't see anything for that.
>
> Public class PhoneTest extends TestCase {
> public static Test suite()
> {
> ServletTestSuite suite = new ServletTestSuite();
> suite.add(...);
> suite.add(...);
> ...
> return suite;
> }
> ...
> }
suite.addTest(new MyTestCase("testXXX1")); suite.addTest(new
MyTestCase("testXXX2")); ...
-Vincent
> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 20, 2005 10:04 AM
> To: 'Cactus Users List'
> Subject: RE: Execution Order
>
> Actually JUnit does not lack ordering :-) The way to do it through a
> Test Suite. Just create one and add each test individually to the
> suite in the order you want. Check the JUnit FAQ for more details on
this.
>
> Thanks
> -Vincent
>
> > -----Original Message-----
> > From: Rod Macpherson [mailto:[EMAIL PROTECTED]
> > Sent: mardi 20 septembre 2005 18:55
> > To: Cactus Users List
> > Subject: Execution Order
> >
> > JUnit lacks execution ordering and, by extension, so does Cactus.
> > Test
>
> > independence is clearly desirable but, ironically, execution order
> > does not imply test dependency. That is to say execution order is an
> > independent notion.
> >
> > Let's say I have a dozen tests. They all run independently, however,
> > all the tests are dependent on the code excersied by the first test.
> > Again, they aren't dependent on the first test but rather the code
> > that test exercises. So, it makes a heckuvalotta sense to run the
> > first test first and bail out early. Any way of ordering execution?
> > Perhaps that too dangerous in that dependencies might bleed through?
> >
> > TIA
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
