harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Ellison <t.p.elli...@gmail.com>
Subject old faithful (was: Re: newbie to project-where to start from)
Date Thu, 16 Feb 2006 10:17:42 GMT
Geir Magnusson Jr wrote:
> Tim Ellison wrote:
>> Pick a module [1] that interests you and from there the test code is in
>> <module_name>/src/test/java/org.apache.harmony.tests.<pkg>.<type>Test.java
>> where <pkg> and <type> are the package and type under test; see here
>> for an example.
> I'm not convinced that we should only use this package convention for
> tests.
> One should certainly be able to put a test in the same package as the
> class being tested...

ah that old favourite ;-)

I'm sure that I don't need to repeat myself, but, 'oh go on then'

- you cannot put code in java.* packages without running
  them on the bootclasspath.

- I am *strongly* opposed to running tests on the bootclasspath
  - the code is subject to different rules c.f. app classpath
  - our target apps don't run there so the API tests are bogus

- I agree with putting helpers into the bootclasspath to expose
  implementation classes that are tested (by tests on the app
  class path)
  - I would like to see a separation of java API tests and impl
    tests, so we know which ones we expect to pass on any
    compliant impl.



Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.

View raw message