> From: Steve Loughran [mailto:[EMAIL PROTECTED]
>
> I think you cant see if a class is abstract without loading it (or
using
> BCEL). Load-time checking is best done in the runner, as the classpath
> is all set up there.
If you use BCEL (or better yet ASM since it's lighter weight and
faster),
y
Stefan Bodewig wrote:
On Tue, 12 Apr 2005, Steve Loughran <[EMAIL PROTECTED]> wrote:
I'm thinking of what would it take to modify JUnitTestRunner to
We have enhancement requests to do so in .
It may be easier to write a selector.
Stefan
I think you cant see if a class is abstract without loading
On Tue, 12 Apr 2005, Steve Loughran <[EMAIL PROTECTED]> wrote:
> I'm thinking of what would it take to modify JUnitTestRunner to
We have enhancement requests to do so in .
It may be easier to write a selector.
Stefan
-
To uns
Phil Weighill Smith wrote:
Steve,
I've not written any code to help here, but thought the following issue
could also be considered:
When executing a test class that has no test methods what-so-ever (e.g.
someone comments out all tests for some reason) the runner currently
barfs instead of ignoring
Steve,
I've not written any code to help here, but thought the following issue
could also be considered:
When executing a test class that has no test methods what-so-ever (e.g.
someone comments out all tests for some reason) the runner currently
barfs instead of ignoring the test class.
Phil :n.
I'm thinking of what would it take to modify JUnitTestRunner to
-skip anything that is abstract
-skip anything that is not a test case
I know there are bugs on this; has anyone done the code to do it, and if
not, where should I start.
I could tweak JUnitTestRunner.run() to probe classes and then
