tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse Kuhnert <jkuhn...@gmail.com>
Subject Re: testing....testng?
Date Sun, 12 Feb 2006 21:24:57 GMT
I poked around the mailing lists and found the discussion regarding
annotation inheritance. I don't believe I'm familiar enough with the
semantics to know what to say.

Is it really breaking the java annotation spec if you do a search on super
classes as well?

Either way I understand the frustration but don't think I can help if the
two core devs already voted -1 on this feature. Hmmm...

On 2/12/06, Kevin Menard <kmenard@servprise.com> wrote:
> On Sun, 12 Feb 2006 02:16:07 -0500, Jesse Kuhnert <jkuhnert@gmail.com>
> wrote:
> > Just being curious, what caused the need for creating an xml file? Only
> > because of my recent interactions.
> Two issues that have been rather annoying for me is the failure for the
> plug-in to properly detect @Factory.  Rather than use the factory to
> invoke instances of a particular class, the plugin attempts to create a
> copy of the class with arbitrary parameters, which will almost certainly
> cause the test to fail.
> The other issue is that it won't detect any classes that don't have @Test
> somewhere in the class.  Thus, if you like to build a test hierarchy using
> template methods, your subclasses won't run.
> Both issues seem to have gone away when I provided my own testng.xml file,
> but that was more work than I really wanted to do.  It also makes it
> difficult to right-click on a class to run just that class.
> --
> Kevin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message