You can migrate CATT test cases to eCATT test scripts of the same name. The eCATT test scripts are new objects and the original CATT test cases remain as they were. The distinction made in CATT between test procedure and test module does not exist in eCATT – both procedures and modules are represented in eCATT by test scripts. The migrated eCATT test script is always stored in the eCATT system regardless of where the original CATT script was stored.
During migration, eCATT does the following:
· Writes a comment in the test script, with information about the source of the test case.
· Copies all the attributes of the test case to the test script.
· Copies the documentation in the test case to the test script.
· Replaces the ampersand ( & ) at the beginning of CATT parameters and local variables with the underscore ( _ ) at the beginning of eCATT parameters. The ampersand ( & ) at the beginning of standard parameters is not affected.
· Replaces CATT functions with the appropriate eCATT commands.
· Writes comment lines into the test script where changes to the script need to be done manually.
Variants are an integral part of many CATT test cases, whereas in eCATT the variants are separate from the test scripts.
eCATT can migrate a test case into a test script and create a test configuration of the same name. The test configuration contains the variants. Alternatively, you can choose to only create the test script. In this case, no variants are migrated.
You can migrate a test case that exists in several forms, from different releases of the SAP System, into one test script of multiple versions.
CATT test cases can use the REF function to call test modules, which can call other test modules.
If you use recursive REF migration, all the test modules are migrated into individual eCATT test scripts, which are referenced using the REF command.
If you do not use recursive REF migration, only the test case is migrated. The test modules are referenced by the REFCATT or REMOTECATT commands as appropriate.
The parameters of the CATT test cases begin with an ampersand ( & ). When migrating to eCATT, the first character of the parameter name is replaced with underscore ( _ ).
For example, the parameter &BUKRS turns into the parameter _BUKRS.
In some applications, the visibilities of the parameters are indicated by I, E, or V at the beginning of the parameter names. For example:
· I_BUKRS is an import parameter
· E_BUKRS is an export parameter
· V_BUKRS is a local variable
During the migration, you can choose to place the relevant type (I, E, or V) at the beginning of the eCATT parameter name to be created. This also affects the REF calls, which are executed simultaneously when the option Recursive REF Migration is selected. If you migrate CATT modules in a first step and the CATT test cases in a second step, use the same setting for the parameter names. Otherwise, inconsistencies may occur – for example, it might not be possible for the migration tool to enter correct parameter assignments in the command interfaces.
Not everything that was possible in a CATT test case can be automatically converted when migrating to eCATT. When the migration function determines that manual modification of the eCATT test script is required or recommended, it writes additional comments in the test script.
The CATT variables &T01 to &T99 containing translatable text are local variables _T01 to _T99 in eCATT. However, the eCATT variables only contain the text in the original language as default values.
Dynamic changes of destination during execution are not possible in eCATT. The CATT parameter &LDS, which was used for setting a RFC destination dynamically, can no longer be used in eCATT.
In CATT, all messages from a transaction were accessible using the system variable &MSG. This is not so in eCATT.