harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nadi...@apache.org
Subject svn commit: r600515 - in /harmony/standard/site: docs/subcomponents/classlibrary/testing.html xdocs/subcomponents/classlibrary/testing.xml
Date Mon, 03 Dec 2007 13:05:40 GMT
Author: nadinem
Date: Mon Dec  3 05:05:34 2007
New Revision: 600515

URL: http://svn.apache.org/viewvc?rev=600515&view=rev
Log:
HARMONY-5233

Modified:
    harmony/standard/site/docs/subcomponents/classlibrary/testing.html
    harmony/standard/site/xdocs/subcomponents/classlibrary/testing.xml

Modified: harmony/standard/site/docs/subcomponents/classlibrary/testing.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/testing.html?rev=600515&r1=600514&r2=600515&view=diff
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/testing.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/testing.html Mon Dec  3 05:05:34
2007
@@ -233,21 +233,17 @@
                                 <p>
                     Tests are not separated by functionality under test, for example, tests
against <code>clone()</code>
                     methods are NOT separated from tests against <code>equals()</code>
methods.
-                    Classpath tests are separated from bootclasspath tests on a directory
level:
+                    Find more details <a href="#Package and Class Names for Different
Types of the Tests"> below</a>.
                 </p>
-                                <pre>&lt;modulename&gt;/src/test/api/<b>java</b>
- Classpath tests
-&lt;modulename&gt;/src/test/api/<b>java.injected</b> - Bootclasspath
tests</pre>
                                 <p>
-                    Find more details <a href="#Package and Class Names for Different
Types of the Tests">
-                        below</a>.
-               </p>
-                                <p>
-                    Some modules might have platform specific tests that are in the case
separated on a directory
-                    level:
+                    Some modules might have implementation specific tests that are in this
case separated on a directory level:
                 </p>
-                                <pre>&lt;modulename&gt;/src/test/api/<b>common</b>
-&lt;modulename&gt;/src/test/api/<b>windows</b>
-&lt;modulename&gt;/src/test/api/<b>linux</b></pre>
+                                <pre>&lt;modulename&gt;/src/test/impl/<b>boot</b>
- Package private tests
+&lt;modulename&gt;/src/test/impl/<b>linux</b> - Linux specific tests
+&lt;modulename&gt;/src/test/impl/<b>windows</b> - Windows specific tests</pre>
+                                <p>
+                    If one pretends to test implementation independent platform-specific
functionality, the test should be placed at <code>&lt;modulename&gt;/src/test/api</code>
directory and check platforms from test internals.
+                 </p>
                    
                                     
     <h2>
@@ -291,16 +287,10 @@
                                 <p class="exampletext">
                     To separate the <code>impl</code> test results from
                     the <code>api</code> ones, the <code>impl</code>
test names end with
-                    <code>_ImplTest</code>:<br />
-                    <code>
-                        javax.crypto.<b>CipherTest</b>
-                    </code> - Implementation independent bootclasspath
-                    test for <code>javax.crypto.Cipher</code><br />
-                    <code>
-                        javax.crypto.<b>Cipher_ImplTest</b>
-                    </code> - Implementation specific bootclasspath
-                    test for <code>javax.crypto.Cipher</code>
+                    <code>_ImplTest</code>:
                 </p>
+                                <pre>org.apache.harmony.javax.crypto.tests.javax.crypto.<b>CipherTest</b>
- Implementation independent test for <code>javax.crypto.Cipher</code>
+org.apache.harmony.javax.crypto.tests.javax.crypto.<b>Cipher_ImplTest</b> - Implementation
specific test for <code>javax.crypto.Cipher</code></pre>
                    
                 <p class="backtotop"><a href="#top">Back to top</a></p>
                 

Modified: harmony/standard/site/xdocs/subcomponents/classlibrary/testing.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/classlibrary/testing.xml?rev=600515&r1=600514&r2=600515&view=diff
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/classlibrary/testing.xml (original)
+++ harmony/standard/site/xdocs/subcomponents/classlibrary/testing.xml Mon Dec  3 05:05:34
2007
@@ -60,21 +60,17 @@
        <p>
                     Tests are not separated by functionality under test, for example, tests
against <code>clone()</code>
                     methods are NOT separated from tests against <code>equals()</code>
methods.
-                    Classpath tests are separated from bootclasspath tests on a directory
level:
+                    Find more details <a href="#Package and Class Names for Different
Types of the Tests"> below</a>.
                 </p>
-<pre>&lt;modulename&gt;/src/test/api/<b>java</b> - Classpath tests
-&lt;modulename&gt;/src/test/api/<b>java.injected</b> - Bootclasspath
tests</pre>
-               <p>
-                    Find more details <a href="#Package and Class Names for Different
Types of the Tests">
-                        below</a>.
-               </p>
                 <p>
-                    Some modules might have platform specific tests that are in the case
separated on a directory
-                    level:
+                    Some modules might have implementation specific tests that are in this
case separated on a directory level:
                 </p>
-<pre>&lt;modulename&gt;/src/test/api/<b>common</b>
-&lt;modulename&gt;/src/test/api/<b>windows</b>
-&lt;modulename&gt;/src/test/api/<b>linux</b></pre>
+<pre>&lt;modulename&gt;/src/test/impl/<b>boot</b> - Package private
tests
+&lt;modulename&gt;/src/test/impl/<b>linux</b> - Linux specific tests
+&lt;modulename&gt;/src/test/impl/<b>windows</b> - Windows specific tests</pre>
+                 <p>
+                    If one pretends to test implementation independent platform-specific
functionality, the test should be placed at <code>&lt;modulename&gt;/src/test/api</code>
directory and check platforms from test internals.
+                 </p>
             </subsection>
             <subsection name="Package and Class Names for Different Types of the Tests">
                 <p>
@@ -114,16 +110,10 @@
                 <p class="exampletext">
                     To separate the <code>impl</code> test results from
                     the <code>api</code> ones, the <code>impl</code>
test names end with
-                    <code>_ImplTest</code>:<br/>
-                    <code>
-                        javax.crypto.<b>CipherTest</b>
-                    </code> - Implementation independent bootclasspath
-                    test for <code>javax.crypto.Cipher</code><br/>
-                    <code>
-                        javax.crypto.<b>Cipher_ImplTest</b>
-                    </code> - Implementation specific bootclasspath
-                    test for <code>javax.crypto.Cipher</code>
+                    <code>_ImplTest</code>:
                 </p>
+<pre>org.apache.harmony.javax.crypto.tests.javax.crypto.<b>CipherTest</b>
- Implementation independent test for <code>javax.crypto.Cipher</code>
+org.apache.harmony.javax.crypto.tests.javax.crypto.<b>Cipher_ImplTest</b> - Implementation
specific test for <code>javax.crypto.Cipher</code></pre>
             </subsection>
         </section>
     </body>



Mime
View raw message