System Testing driver script (.pts)
This section describes each System Testing driver script instruction, including:
-
Syntax
-
Functionality and rules governing its usage
-
Examples of use
Notation Conventions
Throughout this guide, command notation and argument parameters use the following standard convention:
Notation | Example | Meaning |
BOLD | ADD_ID | Language keyword |
<italic> | <filename> | Symbolic variables |
[ ] | [<option>] | Optional items |
{ } | {<filenames>} | Series of values |
[{ }] | [{<filenames>}] | Optional series of variables |
| | on|off | OR operator |
System test script keywords are case sensitive. All keywords must be entered in upper case.
For conventional purposes however, this document uses upper-case notation for the supervisor script keywords in order to differentiate from native source code.
Split statements
Statements may be split over several lines in a .spv supervisor script. Continued lines must start with the ampersand ('&') symbol to be recognized as a continuation of the previous line. No tabs or spaces should precede the ampersand.
Statements must be shorter than 2048 characters, although this limit may be lower on some platforms.
Identifiers
A supervisor script identifier is a text string used as a label, such as the name of a message type.
Identifiers are made of an unlimited sequence of the following characters:
-
a-z
-
A-Z
-
0-9
-
_ (underscore)
Spaces are not valid identifier characters.
System Testing keywords and identifiers are case sensitive. This means that LABEL, label, and Label are three different identifiers.
Related Topics
System Testing driver script structure | System Testing driver script keywords | System Testing for C overview