Web site: contributing test cases.

[Alexandre Petit-Bianco]

Tom once sent me instructions on how to contribute new test cases. I
thought we should keep it on the contrib pages.

OK to commit?

./A

Thu Jun  1 10:13:26 2000  Alexandre Petit-Bianco  <apbianco@cygnus.com>

	* contrib.html: Added info on how to contribute test cases.

Index: contrib.html
===================================================================
RCS file: /cvs/java/htdocs/contrib.html,v
retrieving revision 1.3
diff -u -p -r1.3 contrib.html
--- contrib.html        2000/04/23 05:00:31     1.3
+++ contrib.html        2000/06/01 17:19:09
@@ -162,7 +162,36 @@ projects</a>.
 
     <p>Once the originator reports back, or after some suitable amount
       of time (less time if you are absolutely sure, beyond any shadow
-      of a doube, that the bug has been fixed) close the PR.
+      of a doubt, that the bug has been fixed) close the PR.
+
+    <p>
+<pr>
+<table border="0" cellpadding="4" width="95%">
+<tr bgcolor="#b0d0ff">
+ <th align="left">
+  Contributing test cases
+ </th>
+</tr>
+</table>
+<br>
+
+  We're accepting test case patches.<br>
+
+<ul>
+  <li>Put the <tt>.java</tt> file in
+      <tt>libjava/testsuite/libjava.compile</tt>
+      (if it is an expected compiler failure or other compile-time test --
+      run-time tests usually go in <tt>libjava.lang</tt>)
+
+  <li>If the file is "<tt>foo.java</tt>" make a "<tt>foo.xfail</tt>" file.
+      For an expected failure the only thing in there should be
+      "<tt>shouldfail</tt>"
+
+  <li>If the test case matches a Java PR, it is customary to name it after
+      the PR number.
+
+  <li>Send the patch to java-patches and then commit of you're allowed to.
+</ul>
 
 </td></tr>
 </table>