1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
5
>Special variables used by test cases.</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
12
HREF="book1.html"><LINK
14
TITLE="Extending DejaGnu"
15
HREF="c1099.html"><LINK
17
TITLE="Hints On Writing A Test Case"
18
HREF="x1522.html"><LINK
21
HREF="c1584.html"></HEAD
32
SUMMARY="Header navigation table"
41
>DejaGnu: The GNU Testing Framework</TH
51
><<< Previous</A
57
>Extending DejaGnu</TD
65
>Next >>></A
79
>Special variables used by test cases.</H1
81
>There are special variables used by test cases. These contain
82
other information from DejaGnu. Your test cases can use these variables,
83
with conventional meanings (as well as the variables saved in
87
>. You can use the value of these variables,
88
but they should never be changed.</P
98
>The tracking system (e.g. GNATS) number identifying
99
a corresponding bugreport. (<I
103
specify it in the test script.)</P
109
>An optional bug id; may reflect a bug
110
identification from another organization. (<I
114
if you do not specify it.)</P
120
>The subdirectory for the current test
124
>$expect_out(buffer)</DT
127
>The output from the last command. This is an
128
internal variable set by Expect. More information can be found in
129
the Expect manual.</P
135
>This is the output from a
139
> command. This only applies to
140
tools like GCC and GAS which produce an object file that must in
141
turn be executed to complete a test.</P
147
>This is the output from a
151
> command. This is conventionally
152
used for batch oriented programs, like GCC and GAS, that may
153
produce interesting output (warnings, errors) without further
164
SUMMARY="Footer navigation table"
177
><<< Previous</A
195
>Next >>></A
203
>Hints On Writing A Test Case</TD
b'\\ No newline at end of file'