Thanks Tim, testing gurus, I was looking into testing conventions [1] and got the practical question:
--- citation starts --- Tests are not separated by functionality under test, for example, tests against clone() methods are NOT separated from tests against equals() methods. Classpath tests are separated from bootclasspath tests on a directory level: <modulename>/src/test/api/java - Classpath tests <modulename>/src/test/api/java.injected - Bootclasspath testsFind more details below. Some modules might have platform specific tests that are in the case separated on a directory level: <modulename>/src/test/api/common <modulename>/src/test/api/windows <modulename>/src/test/api/linux --- citation ends --- Imaging I have all kinds of tests, e.g. platform-specific, injected to the boot classpath, etc. Where should I put MyTest.java under src/test/api/common or under src/test/api/java? Or should I nest common under java? Or maybe we should just replace common with java, shouldn't we? I volunteer to prepare a patch to the web site when we agree on. [1] http://harmony.apache.org/subcomponents/classlibrary/testing.html On 11/23/07, Tim Ellison <[EMAIL PROTECTED]> wrote: > Alexei Fedotov wrote: > > Do I understand correctly that > > working_classlib/modules/awt/src/test/api/java/ should be actually at > > working_classlib/modules/awt/src/test/api/java.injected? Is it > > possible to use svn move instead of preparing a monstrous patch? > > Just send along a script with the SVN commands you want the committer to > perform, that is how people have done it in the past. > > > The reason why I'm asking is the following. I need to add a test at > > working_classlib/modules/awt/src/test/api/java/ and the tests which > > are injected to a boot classpath are in that place. I believe the > > right way to solve the problem is to move injected test cases to the > > proper place first. What do you think? > > Sounds good. > > Regards, > Tim > -- With best regards, Alexei, ESSD, Intel
