commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason van Zyl <>
Subject Re: [jelly] JellyUnit is available (was Re: [jelly] http and validation tag libraries)
Date Mon, 22 Jul 2002 18:54:32 GMT
On Mon, 2002-07-22 at 14:31, bob mcwhirter wrote:
> > And would it be possible to tweak the collection of tests to exclude
> > abstract test cases or possible have a process inspect a specified
> > directory and simply run non-abstract tests?
> Yah, I think this is mostly a usage issue, really.
> If you name abstract tests slightly differently (ie, FooAbstractTest)
> then using <include>/<exclude>, I think you can pick up the right
> ones.
> By default, *Test* seems to be the pattern for <include>, which
> seems to be a tad bit broad.

Yeah, I just made a project.xml file for beanutils and all the tests end
with 'TestCase' which seems to work well when test cases are in the same
directory as test classes.
> Though, having junit be smart enough not to run abstract tests
> would also be a plus.
> 	-bob
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>

Jason van Zyl

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  -- Jacques Ellul, The Technological Society

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message