* doc/user.sgml: Add new tutorial by Niklaus Giger as a new

	chapter.
	* doc/Makefile.am: Tweak rules for building output files.
	* doc/Makefile.in: Regenerated.

1 files changed, 13 insertions, 19 deletions

diff --git a/doc/dejagnu.texi b/doc/dejagnu.texi
index fb624a0..d290343 100644
--- a/doc/dejagnu.texi
+++ b/doc/dejagnu.texi
@@ -527,6 +527,10 @@ procedures (see below), and you must be careful to return
 @code{UNRESOLVED} where appropriate, as described in the
 @code{UNRESOLVED} section above.
   
+Besides the @sc{posix} messages, DejaGnu provides for variations of the
+PASS and FAIL messages that can be helpful for the tool maintainers.
+It must be noted, however, that this feature is not @sc{posix} 1003.3
+compliant, so its use should be avoided if compliance is necessary.
 
 The additional messages are:
 
@@ -586,6 +590,12 @@ This means that @code{PASS} is in some sense more ambiguous than if
 
 @end ftable
 
+See also @ref{Invoking runtest,,Using @code{runtest}}.
+For information on how to mark tests as expected/known to fail by using
+@code{setup_xfail} and @code{setup_kfail}, see
+@ref{framework.exp,,Core Internal Procedures}.
+
+
 @node Future Directions
 @section Future directions
 @cindex future directions
@@ -672,14 +682,6 @@ A pleasant kind of failure: a test was known to fail, but succeeded.
 This may indicate progress; inspect the test case to determine whether
 you should amend it to stop expecting failure.
 
-@item KPASS
-@kindex KPASS
-@cindex successful test, unexpected
-@cindex unexpected success
-A pleasant kind of failure: a test was known to fail, but succeeded.
-This may indicate progress; inspect the test case to determine whether
-you should amend it to stop expecting failure.
-
 @item FAIL
 @kindex FAIL
 @cindex failing test, unexpected
@@ -2063,16 +2065,7 @@ list of configuration target names.  It is only necessary to call
 @code{clear_kfail} if a test case ends without calling either
 @code{pass} or @code{fail}, after calling @code{setup_kfail}.
 
-@item clear_kfail @var{config}
-@cindex cancelling known failure
-@cindex known failure, cancelling
-Cancel a known failure (previously declared with @code{setup_kfail})
-for a particular set of configurations.  The @var{config} argument is a
-list of configuration target names.  It is only necessary to call
-@code{clear_kfail} if a test case ends without calling either
-@code{pass} or @code{fail}, after calling @code{setup_kfail}.
-
-@item verbose @r{[}-log@r{]} @r{[}-n@r{]} @r{[}--@r{]} "@var{string}" @var{number}
+@item verbose @r{[}-log@r{]} @r{[}-n@r{]} @r{[}--@r{]} @r{[}--@r{]} "@var{string}" @var{number}
 @cindex @code{verbose} builtin function
 Test cases can use this function to issue helpful messages depending on
 the number of @samp{--verbose} options on the @code{runtest} command
@@ -2082,7 +2075,8 @@ default value for @var{number} is 1.  Use the optional @samp{-log} argument
 to cause @var{string} to always be added to the log file, even if it won't
 be printed.  Use the optional @samp{-n} argument to print @var{string}
 without a trailing newline.  Use the optional @samp{--} argument if
-@var{string} begins with "-".
+@var{string} begins with "-".  To log test results to a XML file use the
+@samp{-x} argument.
 
 @end ftable