Don't know if it's worth bickering about, but why not specify
Class.method()?
The config file would consist of, say:
URLTest simpleURL
URLTest parsingURL
URLTest getContent
All methods are defined in one .class file per logical testsuite, without
having to bother with the interfaces or getTests(). The VM interface lets
you do this, no (call a method by class and methodname)? This would help
when you wanted to have some continuity for variables for subtests, as you
could define them as statics on the same class.
I'm fine either way. We're the one's who are going to be using it, so
let's make it easy.
Wes
At 09:49 PM 9/26/98 -400, you wrote:
>"Aaron M. Renn" <[EMAIL PROTECTED]> writes:
>
>> I would like to be able to have a given java class execute more than
>> one test.
>
>OK. How's this? (ie. ignore my previous post)
>
>The testing framework deals with classes that implement either
>gnu.test.Test or gnu.test.TestPackage.
>
>gnu.test.TestPackage is defined as:
>
>public interface TestPackage
>{
> /**
> * Return a set of instantiated tests.
> */
> public Test[] getTests();
>}
