Tests often include utility classes in the same directory so just assuming
everything
is a test case is not valid. The unit test class naming conventions allow
for:
Test*.class
*Test.class
Main.class
AllJUnitTests.class
----- Original Message -----
From: "Chris Kimpton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 05, 2001 7:08 AM
Subject: Re: [JBoss-dev] Automated JBoss Testsuite Results
> Hi,
>
> >From: David Jencks <[EMAIL PROTECTED]>
> >
> >Having these tests back is wonderful but...
> >
> >WHATS GOING ON?
> >
> >the test script appears to be assuming every class whose name begins with
> >Test is a test-- does this mean I have to rewrite my tests to rename the
> >ejbs and mbeans that I happened to name e.g. TestSomethingMBean?
Couldn't
> >we only assume classes are tests if they are in a .../test/xxx/test/
> >directory?
> >
> >Also, there is some kind of security exception from rmi making even less
> >information come back from the server than previously. Anyone know what
> >this is about? (cf eg jmx/test/TestConnectionFactoryLoader)
> >
>
> I think the testsuite/test run ant scripts need some work to
include/exclude
> the right stuff - and/or to follow some naming convention - I think Jason
> mentioned this a few weeks back...
>
>
> Chris
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
