System Test Script keywords (PTS)

System Testing for C helps you solve complex testing issues related to system interaction, concurrency, and time and fault tolerance by addressing the functional, robustness, load, performance and regression testing phases from small, single threads or tasks up to very large, distributed systems. Test script file names must contain only plain alphanumerical characters. System Testing for C

Basic structure

A typical System Testing .pts test driver script is presented as follows:

HEADER "Registering", "1.0", "1.0"

SCENARIO basic_registration

FAMILY nominal

-- The body of my basic_registration test

END SCENARIO

SCENARIO extented_registration

FAMILY robustness

SCENARIO reg_priv_area

-- The body of my reg_priv_area test

END SCENARIO -- reg_priv_area

SCENARIO reg_pub_area LOOP 10

-- The body of my reg_pub_area test

END SCENARIO -- reg_priv_area

END SCENARIO

The overall structure of a C system test script must follow these rules:

  • A test script always starts with the HEADER keyword.

  • A test script is composed of one or several scenarios.

  • All statements begin with a keyword.

  • Statements are not case sensitive (except when C expressions are used).

  • Statements start at the beginning of a line and end at the end of a line. You can, however, write an instruction over several lines using the ampersand (&) continuation character at the beginning of additional lines. In this case, the ampersand must be the very first character on that line; no spaces or tabs should precede it.

  • Statements must be shorter than 2048 characters, although this limit may be lower on some platforms.

Structuring statements

The basic structuring statements are:

  • HEADER: Specifies the name of the test script, the version of the tested system, and the version of the test script. This information will be included in the test report.

  • SCENARIO: Indicates the beginning of a SCENARIO block. A SCENARIO block ends with an END SCENARIO statement. A SCENARIO block can be iterated multiple times using to the LOOP keyword.

  • FAMILY: Qualifies the scenario and all its sub-scenarios. The FAMILY attribute is optional. A list of qualifiers can be given such as: FAMILY nominal, structural.

Each scenario can be split into sub-scenarios.