CATT test case names are being lengthened as part of the Basis namespace extension. At the same time CATT will switch from internal number assignment to external name assignment.

CATT test cases navigate through transactions in a fixed screen sequence. If the screen sequence is changed, test cases must be modified accordingly. The Change Managements function has been implemented to make this easier.

From 4.5A parameters can be maintained in screens in screen simulation mode. It allows the maintenance of nested subscreens, Table Controls and TabStrips.

Function modules can be tested from 4.5A using type F test cases which can be managed in the Test Workbench.

You can control whether the transactions in a transaction chain run directly after one another (within a work process), or are separated by a specified waiting time (work process is released during waiting), in a parameter.

CATT has previously considered a transaction to be finished when COMMIT WORK was called. Transactions which contained several COMMIT WORKs could not be tested with CATT. The new CATT mode allows transactions which contain several COMMIT WORKs to be tested.

The previous mode is still supported.

Test cases usually use the screen definition for the transactions tested in the R/3 System which called them. This can cause problems when testing transactions in various test systems from a central System, if transactions are tested which have different screen defintions in the central System. The release-independent call function has been implemented for this case.

To ease the creation of complex test cases, individual test cases can be retested from the log.

When a test case is retested, its import interface has the same values as in the logged test. The retest is in a new session.