On Monday 27 June 2011, Stefano Lattarini wrote:
> On Monday 27 June 2011, Stefano Lattarini wrote:
> >
> > Attached is the squash-in with the fixes you suggested. I hope to
> > be soon able to finish up this part of the documentation; I'll post
> > and additional squash-in when I'm done.
> >
> OK the documentation is basically complete now (it still lacks a
> working example I'd like to add in the `doc/' subdir, similar to
> what is done with the "amhello" package). I've pushed it to the
> temp branch; attached is the diff w.r.t. the previous status, for
> reference.
>
> Regards,
> Stefano
>
And please consider also this further squash-in as done.
Sorry for the noise,
Stefano
-*-*-*-
diff --git a/doc/automake.texi b/doc/automake.texi
index 39192ba..6b7b761 100644
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -332,7 +332,7 @@ API for Custom Test Drivers
* Command-line arguments for test drivers::
* Log files generation and test results recording::
-* Console output during testsuite runs::
+* Testsuite progress output::
* HTML generation from testsuite logs::
Changing Automake's Behavior
@@ -9126,7 +9126,7 @@ explicitly stated otherwise.
@menu
* Command-line arguments for test drivers::
* Log files generation and test results recording::
-* Console output during testsuite runs::
+* Testsuite progress output::
* HTML generation from testsuite logs::
@end menu
@@ -9148,7 +9148,7 @@ Here is the list of options:
The name of the test, with VPATH prefix (if any) removed. This can have a
suffix and a directory component (as in e.g., @file{sub/foo.test}), and is
mostly meant to be used in console reports about testsuite advancements and
-results (@pxref{Console output during testsuite runs}).
+results (@pxref{Testsuite progress output}).
@item --log-file=@var{PATH}
The log file the test driver must create. If it has a directory component
(as in e.g., @file{sub/foo.log}), the Automake harness will ensure that
@@ -9258,8 +9258,8 @@ if a test script reports 8 successful test cases and 2
skipped test
cases, some drivers might report that globally as a SKIP, while others
as a PASS.
-@node Console output during testsuite runs
-@subsubsection Console output during testsuite runs
+@node Testsuite progress output
+@subsubsection Testsuite progress output
A custom test driver has also the task of displaying, on the standard
output, the test results as soon as they become available. Depending on
