From: janis Date: Wed, 13 Nov 2002 20:55:02 +0000 (+0000) Subject: 2002-11-13 Janis Johnson X-Git-Tag: upstream/4.9.2~83443 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=5f38bed95b9f2c1645cbfdf62a70f9fa28252403;p=platform%2Fupstream%2Flinaro-gcc.git 2002-11-13 Janis Johnson * doc/install.texi (Testing): Document extra Java testing. * doc/sourcebuild.texi (Test Suites): Document libgcj testing. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@59085 138bc75d-0d04-0410-961f-82ee72b054a4 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 23e98e5..4316431 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2002-11-13 Janis Johnson + + * doc/install.texi (Testing): Document extra Java testing. + * doc/sourcebuild.texi (Test Suites): Document libgcj testing. + 2002-11-13 John David Anglin * pa64-hpux.h (LINK_SPEC): Move "+Accept TypeMismatch" switch to the diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index f2395b2..09b29f3 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -1264,6 +1264,19 @@ To get a list of the possible @file{*.exp} files, pipe the 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. This suite can be run +as part of libgcj testing by placing the Mauve tree within the libjava +testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by +specifying the location of that tree when invoking @samp{make}, as in +@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} diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi index 275a104..e337a50 100644 --- a/gcc/doc/sourcebuild.texi +++ b/gcc/doc/sourcebuild.texi @@ -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,32 @@ 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 tests for the Java Class Libraries. These tests are run as part +of libgcj testing by placing the Mauve tree within the libjava testsuite +sources at @file{libjava/testsuite/libjava.mauve/mauve}, or by specifying +the location of that tree when invoking @samp{make}, as in +@samp{make MAUVEDIR=~/mauve check}. + +To detect regressions, a mechanism in @file{mauve.exp} compares the +failures for a test run against the list of expected failures in +@file{libjava/testsuite/libjava.mauve/xfails} from the source hierarchy. +Update this file when adding new failing tests to Mauve, or when fixing +bugs in libgcj that had caused Mauve test failures. + +The @uref{http://oss.software.ibm.com/developerworks/opensource/jacks/,, +Jacks} project provides a test suite for Java compilers that can be used +to test changes that affect the GCJ front end. This test suite is run as +part of Java testing by placing the Jacks tree within the the libjava +testsuite sources at @file{libjava/testsuite/libjava.jacks/jacks}. + +We encourage developers to contribute test cases to Mauve and Jacks.