cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Martin" <>
Subject Re: [C2] Unit testing.
Date Sat, 10 Feb 2001 02:35:05 GMT
In the past I've taken the approach of giving test cases obviously different
names which cannot be confused with normal classes e.g.
This also makes it easy to seperate out code and test using Ant. Also makes
it easy to use the <batchtest> task to execute test cases.

Not everyone would want to take this approach though.

On a similar note has anyone thought about an XMLUnit which could be used to
test the XML output of producers? It's something I've considered putting
together in the past rather than trying to examine HTML output to verify

----- Original Message -----
From: Berin Loritsch <>
To: <>
Sent: Friday, February 09, 2001 7:21 PM
Subject: Re: [C2] Unit testing.

> Paul Russell wrote:
> >
> > * Stuart Roebuck ( wrote :
> > > I kept my tests in separate directory hierarchies at first but found
> > > it more of a hassle to maintain, especially working from the command
> > > line - though I don't do that very often!  Putting them in the same
> > > directory gives me a visual check on whether everything is unit
> > > tested, and/or whether I have moved and renamed everything when I'm
> > > refactoring - I just visually look for side-by side pairs in the
> > > listing.
> >
> > Mm-hmm. Okay, I'm happy to put them in the same directories, but I'd
> > like input from the other developers before I start splattering the
> > place with unit tests :) Guys...?
> I really don't like confusing the implementation class and the test
> class.  I would much prefer using Ant to merge the test and the Cocoon
> directories for compilation--Just don't mix the test classes and the
> Cocoon classes.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

View raw message