A test script consists of three principal parts – its attributes, the script commands, and the parameters.
As with other eCATT objects, the test script has mandatory attributes (title, package, person responsible, and application component) as well as attributes containing administrative information. Two important attributes are the maintenance system and the versioning information. You need to assign a system data container in the maintenance attributes to enable the test script to address the system landscape during development. Optionally, you can specify a target system from the system data container as the default target system that is used at design time. A test script can exist in several versions and the validity of a test script for testing a given system, is determined by the versioning information.
The import and export parameters define the interface of the test script so that values can be passed to and from the script. You can also create local variables that are only used within the test script.
The commands describe the test. Typically, a script contains one or more recorded transactions with the associated checks and calculations but it need not do so. For example, it could contain just some usefully functionality that can be referenced from another script, or it could contain a series of references to other scripts to build a more complex test out of reusable units.