Index: README
===================================================================
RCS file: /cvs/apisupport/harness/release/README,v
retrieving revision 1.47
diff -u -r1.47 README
--- README	17 Aug 2006 15:28:15 -0000	1.47
+++ README	21 Aug 2006 16:05:19 -0000
@@ -305,7 +305,9 @@
 use spec.version.base (see below).
 
 Specify your test dependencies on other modules [since 5.0u2, requires /3
-schema]:
+schema]. Runtime module dependencies are added on compile and runtime classpath of 
+tests for compatibility with /2 schema. The tags in project.xml are 
+described bellow:
 
     <test-dependencies>
         <test-type>
@@ -318,15 +320,75 @@
             <test-dependency>
                 <!-- Identification of module our tests depend upon. -->
                 <code-name-base>org.netbeans.modules.java.project</code-name-base>
-                <!-- Include also transitive dependencies of that module. -->
+                <!-- Include also transitive module dependencies of that module. -->
                 <recursive/>
-                <!-- Always available when running, but to include at compile time also: --> 
+                <!-- Always available when running, but to include at compile time also. --> 
                 <compile-dependency/>
-                <!-- To request the tests of that module, rather than the module itself: -->
+                <!-- To request the tests of that module, rather than the module itself. -->
                 <test/>
             </test-dependency>
         </test-type>
     </test-dependencies>
+
+For example we have three modules with code name bases A,B,C. A depends on B, B depends on C.
+
+Use case 1:
+
+<test-type>
+ <name>unit</name>
+ <test-dependency>
+    <code-name-base>A</code-name-base>
+ </test-dependency> 
+</testtype>
+
+Runtime classpath is A.
+Compile classpath is not defined.
+
+Use case 2:
+
+<test-type>
+ <name>unit</name>
+ <test-dependency>
+    <code-name-base>A</code-name-base>
+    <recursive/>
+ </test-dependency> 
+</testtype>
+
+Runtime classpath is A,B,C.
+
+Use case 3:
+
+<test-type>
+ <name>unit</name>
+ <test-dependency>
+    <code-name-base>A</code-name-base>
+    <compile-dependency/>
+    <recursive/>
+ </test-dependency> 
+</testtype>
+
+Runtime classpath is A,B,C.
+Compile classpath is A,B,C.
+
+Use case 4:
+
+<test-type>
+ <name>unit</name>
+ <test-dependency>
+    <code-name-base>A</code-name-base>
+    <compile-dependency/>
+    <recursive/>
+    <test/>
+ </test-dependency> 
+</testtype>
+
+Runtime classpath is A,B,C, unittests of A.
+Compile classpath is A,B,C, unittests of A.
+
+Source roots  for tests are placed at:
+
+${project.dir}/test/unit/src/   - source folder for unit testtype
+${project.dir}/test/qa-functional/src - source folder for qa-functional testtype  
 
 As an example, to ensure that FileUtil.toFileObject(File) will work when your
 unit tests are run: