Parameters

Parameters are a test script’s import and export interfaces, and also the local variables. Within a test script, the parameters behave in a similar manner.

Visibility

The visibility determines whether a parameter is an import parameter, an export parameter, or a local variable. You set the visibility in the parameter list.

Local variables can be used inside inline ABAP blocks. Import and export parameters cannot be used inside inline ABAP blocks.

Import parameters

Import parameter values are passed when a test script is called, and are available locally in the test script. They can have default values which are used if no other value is passed in the call.

Import parameters are version-independent – that is, if you create a parameter in one version, it exists in all versions. This is important because it ensures a consistent interface for the test script.

Export parameters

You can assign the test script result to an export parameter, which can be passed to a variable in the calling test procedure when you return from a test module.

Export parameters are version-independent – that is, if you create a parameter in one version, it exists in all versions. This is important because it ensures a consistent interface for the test script.

Local variables

Local variables are used in test cases for calculations, or to receive export parameters from referred test cases or called function modules. They are also used for passing values to and from inline ABAP blocks.

Local variables are version-dependent – that is, a local variable defined in one version is not automatically defined in another version. For example, a parameter with a given name might be defined as type C in one version, type I in a second version , and not exist at all in a third version.

Naming convention

Names are alphanumeric strings up to 30 characters long. The first character must be a letter or an underscore.

Copying parameters from other eCATT objects

See Importing Parameters into Test Data Containers or Test Scripts.