Just being curious, what caused the need for creating an xml file? Only because of my recent interactions.
I can say at the very least that in maven2, unless you have some weird runtime DataProvider stuff to setup there is actually 0 configuration that needs to be done. Unless you wanted only a certain set of classes to be run? But then, why not use groups to specify the classes instead of inviduals themselves? No idea what you environment is like, but would love to know of any issues beforehand. On 2/11/06, Kevin Menard <[EMAIL PROTECTED]> wrote: > > On Sat, 11 Feb 2006 15:28:01 -0500, Jesse Kuhnert <[EMAIL PROTECTED]> > wrote: > > > Does anyone have any strong feelings about possibly incorporating testng > > into some of the 4.1 unit tests? > > > > The good part about this is that testng can happily run any junit test > > (as > > well as the eclipse plugin), along with a number of additional useful > > features: > > IMHO, the Eclipse plug-in has some ways to go before it's really useful, > unless you're willing to handcraft a TestNG XML file. I've filed some > bugs in their JIRA and Alexandru has even addressed some of the issues, so > that's cool. Just something to be aware of. With that being said, I'm > not a Tapestry dev, so it's ultimately up to you guys. > > -- > Kevin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
