4Test syntax features
528
User's Guide
A QA O
RGANIZER
K
EYWORDS
Statements
You use QA Organizer keywords to construct statements, using this syntax:
keyword : value
keyword
One of the QA Organizer keywords.
value
A comment, script, testcase, include file, attribute name, or data
value.
For example, this statement associates the script myscript.t with the plan:
script : myscript.t
Spaces before and after the colon are optional.
Symbol definition
statements
Use symbols to define data that is shared by a group of tests in the plan.
Symbol definitions follow these syntax conventions:
·
The symbol name can be any valid 4Test identifier name, but must begin
with the $ character.
·
The symbol value can be any text. When QA Organizer encounters the
symbol, it expands it (in the same sense that another language expands
macros).
For example, the following QA Organizer statement defines a symbol
named Color and assigns it the
STRING
value "Red":
$Color = "Red"
·
To use a $ in a symbol value, precede it with another $. Otherwise, the
compiler will interpret everything after the $ as another symbol. For
example, this statement defines a symbol with the value Some$String:
$MySymbol = "Some$$String"
·
To assign a null value to a symbol, do not specify a value after the equals
sign. For example:
$MyNullSymbol =
·
To indicate that a test is incomplete when generating a testplan
completion report, assign the symbol the ? character. For example:
$MySymbol = ?
Note If a symbol is listed in a testcase's argument list, but is not
assigned a value before the testcase is actually called, QA Organizer
will generate a runtime error that indicates that the symbol is
undefined. To avoid this error, assign the symbol a value or a ? if the
data is not yet finalized.
For more information on 4Test syntax features (identifier names, data types,
or the list constructor operator) see online Help.
