> -----Original Message-----
> From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 3:47 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: AXIS Test Restructuring
>
>
> > Me, I think that as well as cleaning up the build process,
> we need to work
> > on the test suite so it runs more like a big fat junit
> test; you run all the
> > tests and get back an XML file of what worked, what
> didnt...to date the way
> > we go right now the first failure seems to stops the run.
>
> I know you guys are further along on this now, but I just
> wanted to note that I believe we need to go in the other
> direction. Right now we pretty much have to run the whole
> suite in a lump and what would be really useful is to be able
> to run individual tests, or a selection of tests.
I agree.
> I also like the 'first failure stops the run' mode, and would
> not like that to change as the default. It is perfectly
> reasonable for automation to report all the tests that failed
> in a run however.
I must not be reading this correctly because it seems contradictory. There will only be one test failure to report if you stop after the first failure. I'd rather allow all the tests to run and get a report containing information on all the failures. The Ant tasks junitreport is an excellent way to summarize the results.
***********************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************
