7 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.44"><LINK
10 HREF=
"book1.html"><LINK
12 TITLE=
"A POSIX conforming test framework"
13 HREF=
"posix.html"><LINK
16 HREF=
"runtest.html"></HEAD
29 >DejaGnu: The GNU Testing Framework
</TH
63 >Chapter
2. Running Tests
</A
74 HREF=
"runningtests.html#MAKECHECK"
84 HREF=
"outputfiles.html"
85 >The files DejaGnu produces.
</A
90 >There are two ways to execute a test suite. The most
91 common way is when there is existing support in the
95 >. This support consists of a
99 > target. The other way is to execute the
103 > program directly. To run
107 > directcly from the command line requires
108 either all the correct options, or the
<A
109 HREF=
"customizing.html#LOCAL"
111 >Local Config File
</I
124 >To run tests from an existing collection, first use
128 > as usual to set up the
129 build directory. Then try typing:
</P
148 usually saves you some trouble. For instance, it can set up any
149 auxiliary programs or other files needed by the tests. The most
150 common file the check builds is the
154 >. The site.exp file contains
155 various variables that DejaGnu used to dertermine the
156 configuration of the program being tested. This is mostly for
157 supporting remote testing.
</P
162 > target is supported by GNU
166 >. To have DejaGnu support added to your
170 >, just add the keyword
171 dejagnu to the AUTOMAKE_OPTIONS variable in your
177 >Once you have run
<I
181 any auxiliary files, you can invoke the test driver
185 > directly to repeat the tests.
186 You will also have to execute
<B
190 directly for test collections with no
241 >A POSIX conforming test framework
</TD