diff options
Diffstat (limited to 'doc/user.sgml')
| -rw-r--r-- | doc/user.sgml | 41 |
1 files changed, 21 insertions, 20 deletions
diff --git a/doc/user.sgml b/doc/user.sgml index c711a10..1de4c89 100644 --- a/doc/user.sgml +++ b/doc/user.sgml @@ -1,17 +1,17 @@ <chapter id=runningtests> <title>Running Tests</title> - <para>There are two ways to execute a testsuite. The most common - way is to rely upon support in a <filename>Makefile</filename> for - a <emphasis>check</emphasis> target. The other way is to execute - the <command>runtest</command> program directly. To run - <command>runtest</command> directcly from the command line - requires either all the correct options, or the <xref - linkend=local> must be setup correctly. Automake can generate a - <filename>Makefile</filename> that does all of the right things - when the user invokes <command>make check</command> and is the - preferred approach. Both ways of executing a testsuite will be - covered in more detail below.</para> + <para>There are two ways to run a testsuite. The most common way + is to rely on <filename>Makefile</filename> support for a + <emphasis>check</emphasis> target. The other way is to invoke the + <command>runtest</command> program directly. To invoke + <command>runtest</command> from the command line requires either + much care to be taken to ensure that all of the correct options + are given or that the <xref linkend=local> is set up correctly. + Automake can help to produce a <filename>Makefile</filename> that + does the right things when the user invokes <command>make + check</command> and this is the preferred approach. Both ways of + executing a testsuite will be covered in more detail below.</para> <sect1 id=makecheck xreflabel="Make Check"> <title>make check</title> @@ -746,15 +746,16 @@ <chapter id=tutorial> <title>Tutorial</title> -<para>This chapter was originally written by Niklaus Giger (ngiger@mus.ch) because he lost a week to figure out how DejaGnu works and how to write a first test.</para> - -<para>Follow these instructions as closely a possible in order get a -good insight into how DejaGnu works, otherwise you might run into a -lot of subtle problems. The examples given in this chapter were run -on an AMD K6 machine with a AMD K6 and a Mac Powerbook G3 acting as a -remote target. The tests for Windows were run under Windows NT using -Cygwin. Its target system was a PowerPC embedded system running -vxWorks.</para> + +<para>This chapter was originally written by Niklaus Giger +(ngiger@mus.ch) because he lost a week to figure out how DejaGnu works +and how to write a first test.</para> + +<para>This tutorial will give a brief, but sound overview into how +DejaGnu works. The examples given in this chapter were run on an AMD +K6 machine with a Mac Powerbook G3 acting as a remote target. The +tests for Windows were run under Cygwin. Its target system was a +PowerPC embedded system running vxWorks.</para> <sect1> <title>Test your installation</title> |