install.texi (Testing): Document extra Java testing.
2002-11-13 Janis Johnson <janis187@us.ibm.com> * doc/install.texi (Testing): Document extra Java testing. * doc/sourcebuild.texi (Test Suites): Document libgcj testing. From-SVN: r59087
This commit is contained in:
parent
e8855edac1
commit
4393a004b0
|
@ -1,3 +1,8 @@
|
|||
2002-11-13 Janis Johnson <janis187@us.ibm.com>
|
||||
|
||||
* doc/install.texi (Testing): Document extra Java testing.
|
||||
* doc/sourcebuild.texi (Test Suites): Document libgcj testing.
|
||||
|
||||
2002-11-12 Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
|
||||
|
||||
* doc/install.texi (powerpc-*-linux-gnu*): Update binutils requirement.
|
||||
|
|
|
@ -1228,6 +1228,17 @@ 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 specifying the location of the Mauve 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}
|
||||
|
|
|
@ -738,6 +738,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
|
||||
|
@ -870,3 +871,23 @@ 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 specifying the location of the Mauve tree when invoking
|
||||
@samp{make}, as in @samp{make MAUVEDIR=~/mauve check}.
|
||||
|
||||
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. There is no automated
|
||||
mechanism to run the Jacks suite as part of GCJ testing.
|
||||
|
||||
We encourage developers to contribute test cases to Mauve and Jacks.
|
||||
|
|
Loading…
Reference in New Issue