Changes from 1.4.3 include:
1. New XML output option, so test results can be loaded into a database.
2. Support for the KFAIL/KPASS (known failures).
6. BlueGnu has been removed from the contrib directory.
7. The contrib/test* scipts were bitrotten and have been removed. If
you still want copies of these, they can be found in the previous
DejaGnu release.
8. i960glue.c has been removed.
gcc.gnu.org:
2003-06-13 Jason Thorpe <thorpej@wasabisystems.com>
* lib/target.exp (prune_warnings): Add two more linker
warning patterns for warnings generated by modern verions
of NetBSD.
Changes since 1.4.1 include:
- New XML output option, so test results can be loaded into a database.
- Support for the KFAIL/KPASS (known failures). This is mostly oriented
towards GDB testing.
- New tutorial chapter.
- Test case builds with either libstdc++-v3 (as used by gcc-3.0.x) or the
older v2.(as used by gcc-2.95.x)
provide a single front end for all tests. Beyond this, DejaGnu offers
several advantages for testing:
- The flexibility and consistency of the DejaGnu framework
make it easy to write tests for any program.
- DejaGnu provides a layer of abstraction which makes all
tests (if correctly written) portable to any host or target
where a program must be tested. For instance, a test for
GDB can run (from any Unix based host) on any target
architecture supported by DejaGnu. Currently DejaGnu runs
tests on several single board computers, whose operating
software ranges from just a boot monitor to a full-fledged,
Unix-like realtime OS.
- DejaGnu is written in expect, which in turn uses Tcl
(Tool command language). The framework comprises two parts:
the testing framework and the testsuites themselves. Tests
are usually written in expect using Tcl.
