IBM
Contents Index Previous Next



Dynamic Behaviour Descriptions


There are three types of tables for specifying the behaviour descriptions:

We have already noted that the difference between the different behaviour tables is in the header, rather than in the body of the tables.

Figure 64 : Fragment of a test case behavior table, showing the header for the test case

Test case Identifiers and Test Group References

The test case identifier appears in the first field and, like most TTCN identifiers, it should be a name unique to the entire test suite. The second field contains the test case reference, which is a path name that specifies the test case's location in the test suite structure.

In the case of test steps this path specifies the test step's location in the test step library. In the case of defaults it specifies the location of the default in the default library. These references have the general format:

Note the terminating slash, which is the last group name in the path. The path may begin with the first GroupIdentifier, i.e. the SuiteIdentifier is optional. If the test suite has no hierarchy then the reference is empty.

Test Purpose and Objective

In the test case table the third field is used to specify the test purpose. The corresponding field in test steps and defaults is called the objective.

Configuration

The configuration entry is introduced by the concurrent TTCN to state the configuration in which this test case behaviour description is used. This field does not appear in test steps and defaults.

Default Behaviour

The default entry is used to state the default behaviour which should be used, if any.

Case study 20: Test step dynamic behaviour.

Figure 65 : Test step dynamic behaviour (LT_DATA_TRANSFER)


http://www.ibm.com/rational
Contents Index Previous Next