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.

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 there are no variants.

You can migrate a test case, 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.