7 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.44"><LINK
10 HREF=
"book1.html"><LINK
13 HREF=
"preface.html"><LINK
15 TITLE=
"What's New In This Release"
16 HREF=
"new.html"></HEAD
29 >DejaGnu: The GNU Testing Framework
</TH
63 >Chapter
1. Overview
</A
74 HREF=
"overview.html#WHATIS"
80 >What's New In This Release
</A
84 HREF=
"designgoals.html"
90 >A POSIX conforming test framework
</A
100 >What is DejaGnu ?
</A
107 testing other programs. Its purpose is to provide a single
108 front end for all tests. Think of it as a custom library of
109 Tcl procedures crafted to support writing a test harness. A
114 infrastructure that is created to support a specific program
115 or tool. Each program can have multiple test suites, all
116 supported by a single test harness. DejaGnu is written in
120 >, which in turn uses
125 language. There is more information on Tcl at the
<A
126 HREF=
"http://www.scriptics.com"
130 Expect web site is at
<A
131 HREF=
"http://expect.nist.gov"
136 >DejaGnu offers several advantages for testing:
</P
142 STYLE=
"list-style-type: disc"
144 >The flexibility and consistency of the DejaGnu
145 framework make it easy to write tests for any program, with
146 either batch oriented, or interactive programs.
</P
149 STYLE=
"list-style-type: disc"
151 >DejaGnu provides a layer of abstraction which
152 allows you to write tests that are portable to any host or
153 target where a program must be tested. For instance, a test
157 > can run (from any Unix
158 based host) on any target architecture that DejaGnu
159 supports. Currently DejaGnu runs tests on many single board
160 computers, whose operating software ranges from just a boot
161 monitor to a full-fledged, Unix-like realtime OS.
</P
164 STYLE=
"list-style-type: disc"
166 >All tests have the same output format. This
167 makes it easy to integrate testing into other software
168 development processes. DejaGnu's output is designed to be
169 parsed by other filtering script, and it is also human
173 STYLE=
"list-style-type: disc"
175 >Using Tcl and expect, it's easy to create wrappers
176 for existing test suites. By incorporating existing tests under
177 DejaGnu, it's easier to have a single set of report analyse
182 >Running tests requires two things: the testing framework, and
183 the test suites themselves. Tests are usually written in
187 > using Tcl, but you can also use a
188 Tcl script to run a test suite that is not based on
196 > script filenames conventionally
200 > as a suffix; for example, the main
201 implementation of the DejaGnu test driver is in the file
207 >Julia Menapace first coined the term ``Deja Gnu'' to describe an
208 earlier testing framework at Cygnus Support she had written for
212 >. When we replaced it with the Expect-based
213 framework, it was like DejaGnu all over again... But more importantly, it
214 was also named after my daughter,
<A
215 HREF=
"mailto:deja@welcomehome.org"
219 years old in Dec of
1998), who was a toddler during DejaGnu's
273 >What's New In This Release
</TD