This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Testsuites and Test Results
Gerald Pfeifer wrote:
>>Index: ChangeLog
>>from Ranjit Mathew <rmathew@hotmail.com>
>>
>> * install.texi (Testing): Added information on how to run
>> Java runtime tests separately.
>
>
> This looks mostly fine, apart from markup (@file instead of @samp), but...
>
>
>>+Java runtime tests can be executed via @samp{make check} from
>>+the @samp{testsuite} directory of the libjava hierarchy
>>+in the build tree.
>
>
> ...wouldn't it be better to specify something like
>
> "in the @filename(@var{target}/libjava/testsuite} directory in
> the build tree" ?
Ok, I'm attaching a modified patch below that makes this
change to both install.texi and sourcebuild.texi.
In addition, I took the liberty of slightly rephrasing the
paragraph on Jacks based testing simply to force makeinfo
into actually creating a new paragraph for it in the HTML
as the original author intended - for some reason, if
a new paragraph merely starts with a @uref{}, makeinfo
was not putting it into a separate paragraph.
BTW, the current documents use both "test suite" and
"testsuite". Are both forms considered correct? If not,
should we not uniformly use the correct form?
Ranjit.
Index: ChangeLog
from Ranjit Mathew <rmathew@hotmail.com>
* install.texi (Testing): Added information on how to run
Java runtime tests separately.
Added @var{target} to the paths specified for placing the
Mauve and Jacks test suites.
Rephrased the Jacks test suite paragraph to force
makeinfo to really show it as a separate paragraph in HTML.
Index: install.texi
===================================================================
--- install.texi Tue Jun 17 10:10:55 2003
+++ install.texi Tue Jun 17 10:31:11 2003
@@ -1495,4 +1495,7 @@
@samp{Running @dots{} .exp} lines.
+The Java runtime tests can be executed via @samp{make check}
+in the @file{@var{target}/libjava/testsuite} directory in
+the build tree.
@section Additional testing for Java Class Libraries
@@ -1501,12 +1504,13 @@
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}.
+testsuite at @file{@var{target}/libjava/testsuite/libjava.mauve/mauve},
+or by specifying the location of that tree when invoking @samp{make},
+as in @samp{make MAUVEDIR=~/mauve check}.
-@uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks}
-is a free test suite that tests Java compiler front ends. This suite
-can be run as part of libgcj testing by placing the Jacks tree within
-the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
+The @uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks}
+test suite is a free test suite that tests Java compiler front ends. This
+suite can be run as part of libgcj testing by placing the Jacks tree within
+the libjava testsuite at
+@file{@var{target}/libjava/testsuite/libjava.jacks/jacks}.
@section How to interpret test results
Index: sourcebuild.texi
===================================================================
--- sourcebuild.texi Tue Jun 17 10:10:48 2003
+++ sourcebuild.texi Tue Jun 17 10:12:34 2003
@@ -945,7 +945,7 @@
@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.
+Runtime tests are executed via @samp{make check} in the
+@file{@var{target}/libjava/testsuite} directory 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