[PATCH] merge java/test.html into install.texi and sourcebuild.texi

[Janis Johnson <janis187 at us dot ibm dot com>]

This patch merges information from java/test.html into the main GCC
documents.  General information about running libgcj tests is now in
the Testing section of the installation instructions, and information
about the tests themselves is in the Test Suites section of the GCC
internals manual.

Tested with "make dvi" and "make info".  OK for the mainline?  Should
it also go into the 3.2 branch at this point?

2002-11-12  Janis Johnson  <janis187@us.ibm.com>

	* doc/install.texi (Testing): Document extra Java testing.
	* doc/sourcebuild.texi (Test Suites): Document libgcj testing.

Index: doc/install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.148
diff -u -p -r1.148 install.texi
--- doc/install.texi	10 Nov 2002 01:14:48 -0000	1.148
+++ doc/install.texi	12 Nov 2002 17:30:06 -0000
@@ -1264,6 +1264,18 @@ To get a list of the possible @file{*.ex
 output of @samp{make check} into a file and look at the
 @samp{Running @dots{}  .exp} lines.
 
+To run only the tests for a library, run @samp{make check} from the
+the library's testsuite in a subdirectory of the object directory:
+@file{libstdc++-v3/testsuite} or @file{libcgj/testsuite}.
+
+@section Additional testing for Java Class Libraries
+
+The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
+a suite of tests for the Java Class Libraries.
+libgcj supports Mauve testing.  If you have Mauve checked out in,
+e.g., @file{~/mauve/}, then you can tell the libgcj to run the Mauve
+tests like so: @samp{make MAUVEDIR=~/mauve check}.
+
 @section How to interpret test results
 
 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
Index: doc/sourcebuild.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/sourcebuild.texi,v
retrieving revision 1.11
diff -u -p -r1.11 sourcebuild.texi
--- doc/sourcebuild.texi	23 Oct 2002 08:47:54 -0000	1.11
+++ doc/sourcebuild.texi	12 Nov 2002 17:31:02 -0000
@@ -753,6 +753,7 @@ here; FIXME: document the others.
 @menu
 * Test Idioms::  Idioms used in test suite code.
 * C Tests::      The C language test suites.
+* libgcj Tests:: The Java library test suites.
 @end menu
 
 @node Test Idioms
@@ -903,3 +904,31 @@ shouldn't.
 
 FIXME: merge in @file{testsuite/README.gcc} and discuss the format of
 test cases and magic comments more.
+
+@node libgcj Tests
+@subsection The Java library test suites.
+
+Runtime tests are executed via @samp{make check} from the @samp{testsuite}
+directory of the libjava hierarchy in the build tree.  Additional runtime
+tests can be checked into this testsuite.
+
+Regression testing of the core packages in libgcj is also covered by the
+Mauve test suite.  The @uref{http://sources.redhat.com/mauve/,,Mauve Project}
+develops a suite of tests for the Java Class Libraries.  These tests are
+run as part of libgcj testing if the suite is available when the tests are
+run.  If you have Mauve checked out in, e.g., @file{~/mauve/}, then you can
+tell the libgcj to run the Mauve tests with @samp{make MAUVEDIR=~/mauve check}.
+
+To highlight regressions, a mechanism in @file{mauve.exp} tracks expected
+failures by comparing against the contents of
+@file{libjava/testsuite/libjava.mauve/xfails} from the source hierarchy.
+Update this file when adding new failing tests to Mauve or when making
+fixes to libgcj that correct for failing Mauve tests.
+
+The @uref{http://oss.software.ibm.com/developerworks/opensource/jacks/,,
+Jacks} project exists to create a test suite for Java compilers.
+Changes affecting the gcj front end can usefully be tested against Jacks.
+We don't as yet have an automated mechanism to run Jacks tests in our test
+framework.
+
+We encourage developers to contribute test cases to Mauve and Jacks.