Go to the first, previous, next, last section, table of contents.


Special variables used by test cases

Your test cases can use these variables, with conventional meanings (as well as the variables saved in `site.exp' see section Setting runtest defaults):

These variables are available to all test cases.

prms_id
The tracking system (e.g. GNATS) number identifying a corresponding bugreport. (`0' if you do not specify it in the test script.)
bug_id
An optional bug id; may reflect a bug identification from another organization. (`0' if you do not specify it.)
subdir
The subdirectory for the current test case.

These variables should never be changed. They appear in most tests.

expect_out(buffer)
The output from the last command. This is an internal variable set by expect.
exec_output
This is the output from a tool_load command. This only applies to tools like GCC and GAS which produce an object file that must in turn be executed to complete a test.
comp_output
This is the output from a tool_start command. This is conventionally used for batch oriented programs, like GCC and GAS, that may produce interesting output (warnings, errors) without further interaction.


Go to the first, previous, next, last section, table of contents.