Remote execution
Test cases can either run locally in the system which contains the test scripts, or remotely in another system. A remote system is accessed via the SAP Remote Function Call (RFC) interface. A remote system is identified by the RFC destination which contains the system name, the client and the user name which you use in this system. You can edit RFC destinations in the SAP system with the transaction SM59. The remote system must not necessarily be a different system, it could also be another client in the same system.
The SPA/GPA parameter RFC ID
determines whether CATT is executed locally or in a remote system. If this parameter is empty, CATT is executed locally; if it contains a valid RFC destination, it is executed remotely. You can set the parameter globally, so that its value is always assigned at logon.Choose System
® User profile ® Own data. Choose the Parameter tab. Enter the parameter RCF ID in the Parameter column and the remote system in the Value column.You can also set the parameter individually at run time. The value specified remains valid until you logoff.
Enter a test case in the CATT main screen (transaction SCAT). Choose Execute. You go to the automatic test case execution screen. Enter a valid destination in the R/3 RFC destination field and choose Execute.
When running automatic test cases directly with the CAT_START
function module, the RFC destination for the current run can be passed in the RFCD parameter.Data and parameters in remote execution
CATT functions are defined in test cases in the management system (system 1). Function modules are called remotely in the execution system (system 2) and they perform the CATT functions locally. The values in the remote system are used for the system variables used in CATT functions, e.g.
SY-MANDT = &MND
SY-LANGU = &SPR
SY-UNAME = &NAM
SPA/GPA parameters are also processed with CATT functions in the remote system, i.e. each parameter value is read live from the remote system. When they are set, each value is stored in the remote system memory.
Authorization
At run time the destination client in the remote system is first checked for CATT authorization. Set this flag when the client is created.
You need the usual authorizations for executing test procedures in the remote system target client, for the authorization object S_DEVELOP. This authorization cannot be restricted to certain test cases. You must be authorized to execute all test procedures, as the value ‘*’ is checked. The authorizations required in transactions and function calls are also checked in the remote system, as required.