Test Script Versions

You can create versions of test scripts. This allows you to use the same script to test a particular business function, even if the implementation of this function in the system changes from release to release (for example, from a transaction in SAP GUI for Windows to a web application).

eCATT automatically finds the appropriate version of a test script for the system under test (through the test configuration).There is only one eCATT object for a test script, irrespective of how many versions exist – in other words, there is only one object in the object directory.

Creating different versions of a script is suitable for scripts with similar functionality but differing implementations for different validity areas. You should not use versions for scripts with different implementations in the same validity area.

Certain attributes and parameters should be identical for all versions of a test script – otherwise, there would problems with calling the interface when using the REF command. However, new versions of a test script can extend the interface. Even parameters such as complex structures or tables can be extended.

The following table summarizes what must be, or need not be, retained across versions.

Property

Retained?

Title

NO

Input & Output Parameters

YES

Local Variables

NO

Code

NO

There are two ways to create a new version of an existing test script. If you use Create, the new version will be empty with the exception of the input and output parameters. If you use Copy, the second version will be identical to the first.