diff options
| author | Rob Savoye <rob@welcomehome.org> | 2001-05-06 16:22:20 +0000 |
|---|---|---|
| committer | Rob Savoye <rob@welcomehome.org> | 2001-05-06 16:22:20 +0000 |
| commit | ee37e3e22012ecee8b3d1d243378ce19a03689e3 (patch) | |
| tree | 008acffabe6121789ecdc575da9aa8beee9565c6 /doc/user.sgml | |
| parent | ca94f15320ca1c1bd31020459f4751ab512b217c (diff) | |
* debian/rules: Install all the doc formats.release-1-4-1dejagnu-1.4.1-release
* redhat/dejagnu.spec: Install all the doc formats.
* Clean.tcl: Also nuke all Emacs backup files.
* Makefile.am: Fix dependencies on tarball target. Add new target
to build Debian packages. Add $(includedir) to install-data-local
target so dejagnu.h gets installed in the right place.
* doc/Makefile.am: Make all paths absolute, cause some versions of
the db2* tools are braindead.
* doc/overview.sgml: Update version numbers and log.
* doc/user.sgml: Add mention of dejagnu.h header file.
* doc/ref.sgml: Add chapter on dejagnu.h header file for unit
testing.
* config/default.exp: New file for default config settings for
simple native testsuites that don't need anything else.
* lib/dejagnu.exp: Add $text\r\n to all strings, to make sure we
only get one line at a time.
* testsuite/libdejagnu: New directory for dejagnu library test
cases.
* testsuite/libdejagnu/unit.cc: Test case for dejagnu.h.
* testsuite/libdejagnu/tunit.exp: Test driver for dejagnu.h.
* testsuite/libdejagnu/Makefile.am: New makefile to build the test
case.
* testsuite/libdejagnu/Makefile.in: Generated.
* testsuite/Makefile.am: Add libdejagnu to SUBDIRS. Replace the
site.exp rule, cause we don't want the $tool setting, so we run
all the test suites. Don't pass the tool name for "make check".
* configure.in: Add testsuite/libdejagnu/Makefile to AC_OUTPUT.
Diffstat (limited to 'doc/user.sgml')
| -rw-r--r-- | doc/user.sgml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/user.sgml b/doc/user.sgml index 16f2160..3ba26ad 100644 --- a/doc/user.sgml +++ b/doc/user.sgml @@ -2374,10 +2374,10 @@ libraries. In this case, each file is linked with a test case in C or C++, and each function or class and method is tested in series, with the test case having to check private data or - global variable to see if the function or method worked.</para> + global variables to see if the function or method worked.</para> - <para>This works particularly well for testing API and a level - where it is easier to debug them, than by need to trace through + <para>This works particularly well for testing APIs and at level + where it is easier to debug them, than by needing to trace through the entire appication. Also if there is a specification for the API to be tested, the testcase can also function as a compliance test.</para> |