[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Kissme and Classpath

From: Alex Lau
Subject: Re: Kissme and Classpath
Date: Sun, 23 Jun 2002 20:44:17 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.6) Gecko/20011120

Thanks again. I'm going to start making some Test case at mauve.. cross my figure :)

Download the lastest cvs from classpath... it is miss javax.transaction directory... is it normal?
I'm going to use my old source for now.

Another question.
1) if the javadoc say since 1.2 (example) , should I build that under the test name "" or should I build it under the name of the class instead e.g.( ) I think I don' t really understand the usage of naming a test under jdk12 ( or jdk11) . Wont that be huge for some

Stephen Crawley wrote:

I did go through all the testlet class. but just don't know how am I go
about creating test. ( Is there anyone working on something related to
mauve and able to shine me some light )

1) When I making a test ( e.g. just like
gnu/testlet/java/io/File/ ) how do
I find out the class info? Should I look at Java Spec? or Just the
ClassPath code?

I think you should start by reading the J2SDK 1.4 javadoc carefully, in
conjunction with older JDK javadocs and other Sun sources. Then build
your tests according to the spec.  If you look at the ClassPath
implementation, only use it to look for ideas on what to test.  Don't
use it to find out how the method ought to behave.

If it is unclear from the JDK javadoc how a particular method ought to
behave, run your test case code against some Sun implementations.
Ultimately, the aim is for 100% (bug for bug) compatibility with the
relevant Sun implementations.  The behaviour of the Sun implementations
are definitive.

2) if the function is depreciated, should I build test for it?

Given that people's code often relies on deprecated methods, yes.

-- Steve

reply via email to

[Prev in Thread] Current Thread [Next in Thread]