5/13/2019

eCATT: Extended Computer Aided Test

Tool (BC-TWB-TST-ECA)
Generated on: 2019-05-13

SAP S/4HANA | 1709 002

PUBLIC

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the SAP Help Portal.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 5/13/2019

Preparing Systems and Computers for

eCATT
Use
For up-to-date information, see SAP Note 519858.

Here is a checklist for preparing to use eCATT:

Maintain table T000 to allow eCATT to be used in the relevant clients.

Patch the systems. For information about which support packages to use, see SAP Note 519858.

Check that the users have the appropriate authorizations.

Install the latest 6.40 SAP GUI for Windows with the SAP GUI Scripting component.

Enable scripting if required. This needs to be done at both the back end and front end.

Prepare systems for Web Dynpro testing if required.

Install certi ed external tools on the local machine of the user. Use the SET_EXTERNAL_TOOL function module to make
the required entries in the customizing table ECCUST_ET.

Create RFC destinations (transaction SM59) for target systems.

Maintaining Table T000

Procedure

1. Start transaction SM31.

2. In the Table/View eld, enter T000.

3. Choose Maintain.

4. On the "Change Clients" View: Overview screen, select the relevant client and choose .

5. In the Restrictions when Starting CATT and eCATT eld, select an entry that allows eCATT.

6. For more information about the possible entries, use the F1 help on the eld.

7. Choose .

Enabling Scripting at the Front End

Prerequisites
The SAP GUI Scripting component is installed. There is an option for installing this component when installing the SAP GUI.

Procedure
This is custom documentation. For more information, please visit the SAP Help Portal 2
 5/13/2019

1. On any screen, choose Customizing of local layout.

2. Choose Options....

3. Choose the Scripting tab.

4. Select Enable Scripting.

5. Choose OK.

Example
The following screenshot shows the recommended settings.

If you are using GUI scripting only within eCATT, there is no need to have a message displayed each time a script starts. On the
other hand, a script never tries to open a new GUI connection in the eCATT environment.

Enabling Scripting on the Application Server

Procedure

You can enable scripting by setting the pro le parameter sapgui/user_scripting to TRUE. The value set using this
procedure will be lost when the system is restarted.

If the administrator edits the application server pro le of the SAP System to include sapgui/user_scripting = TRUE,
scripting will be enabled by default when the server is restarted.

Procedure

1. Call transaction RZ11.

2. On the Maintain Pro le Parameters screen, enter sapgui/user_scripting.

3. Choose Display.

4. In the Display Pro le Parameter Attributes screen, choose Change value.

5. Enter TRUE in the New value eld.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 5/13/2019
6. Choose Save.

Patching the Systems

Use

To be testable by eCATT, the target systems must be based on component SAP_BASIS Release 4.6 or later. A patch containing
essential eCATT functions must have been applied to each of the target systems. For more information about relevant support
packages, see SAP Note 519858.

Preparing to Use an External Tool with eCATT

Use
For up-to-date information, see SAP Note 519858.

An external tool must be:

Certi ed against the BC-eCATT interface. Certi cation should cover the target release as well as the user interface to be
tested.

Installed on the front-end machine that you run the tests on.

Registered on the backend system that eCATT runs on. This is usually done by the system administrator. For registering,
maintain the customizing table ECCUST_ET. You can maintain the table manually or add entries using the function
module SET_EXTERNAL_TOOL from transaction SE37. You should provide the following information:

A working name for the tool

The PROG_ID of the test tool's certi ed interface (this is case-sensitive)

A description of the tool

The local database of the tool, if it has one

The external tool requires a service user in order to communicate with eCATT. To do this, run the program
ECATT_GENERATE_ET_USER from transaction SE38.

If you have not started the external tool from within eCATT, you need the role SAP_ECET in your user pro le to be able to save
and load test scripts to and from eCATT.

Preparing Systems for Testing Web Dynpro

De nition
Create User ECATT_HTTP in the eCATT System

The administrator in the eCATT system must create a user called ECATT_HTTP (with a password). The user requires no special
authorization but must be a system user (in transaction SU01, display the user and choose the Logon data tab. Under User
Type, select System).

Activate the Service ecatt_recorder in the eCATT System

This is custom documentation. For more information, please visit the SAP Help Portal 4
 5/13/2019
1. In the eCATT system, start transaction SICF and navigate to the service default_host/sap/bc/ecatt/ecatt_recorder.

2. Double-click the service and choose the Logon Data tab.

3. Enter the user ECATT_HTTP and the corresponding password.

4. In the Procedure eld at the top of this tab, choose the entry Standard from the drop-down list. In addition, the checkbox
Enable all Logon Procedures has to be selected. For the other elds, you can keep the default settings.

5. Choose Save.

6. Select ecatt_recorder and choose Service/Virtual Host Activate .

Activate the Service ecattping in the Target Systems

Java System

1. In the SAP NetWeaver Administrator, choose Server Services Deploy .

2. On the Runtime tab, select Application.

3. Select ecattping.

4. Choose Start Application.

ABAP System

1. In the target system, start transaction SICF and navigate to the service ecattping.

2. Select ecattping and choose Service/Virtual Host Activate .

Activate eCATT Rendering in the Target System

To activate eCATT Rendering in the target system, open the Web Dynpro application WD_GLOBAL_SETTING in editing mode.
Under section General Parameters, choose Permit eCATT Rendering (WDENABLEXBCMLCLIENT) and save your entries.

Use

Authorizations
Use
Authorizations and security are covered more fully in the eCATT Security Guide, which can be found in SAPNet.

Access to the eCATT Test System

Access to the eCATT test system should be strictly controlled.

Caution
If trusted RFC is not used, there may be RFC destinations in the eCATT test system in which the user and password are fully
speci ed.

Authorizations Required at Design Time

You can assign the role SAP_ECAT (eCATT Editor) to your test developers to authorize them for design time.

This is custom documentation. For more information, please visit the SAP Help Portal 5
 5/13/2019
In more detail, you need:

Developer rights (S_DEVELOP with relevant activities for object types ECAT, ECSC, ECSD, ECTC and ECTD) in the eCATT
test system.

RFC rights (S_RFC) in the eCATT test system.

The relevant authorizations in the target systems.

If applicable, rights for maintaining documentation with SE61 (S_DOKU_AUT) in the eCATT test system.

Rights for GUI activities for uploading and downloading (S_GUI) in the eCATT test system.

Authorizations Required at Runtime

You can assign the role SAP_ECST (eCATT Starter) to your testers to authorize them for runtime.

In more detail, you need:

A pro le containing S_DEVELOP authorization with activity 16 (Execute) and 03 (Display) in the eCATT test system.

RFC rights (S_RFC) in the eCATT test system.

A pro le containing S_DEVELOP authorization with activity 16 (Execute) in the target systems.

The relevant authorizations in the target systems.

If applicable, rights for archiving eCATT Logs in an archive (S_ARCHIVE) in the eCATT test system.

Security and the SAPGUI Command

The following are some of the security features:

The administrator can switch GUI Scripting on or off for a particular application server.

In addition to the server settings, GUI Scripting requires certain components to be installed on the front end. If GUI
Scripting is enabled, the user can enable or disable scripting at the front end. Here, you have the option to be noti ed
whenever a script attaches to the SAP GUI or a script opens a connection. eCATT itself never opens a new connection.

eCATT GUI Scripting does not use Windows Scripting Host.

The SAPGUI command never records logon screens.

Target Systems

When you record GUI actions in a target system, the security settings of the target system apply. When you replay a SAPGUI
command, the security settings of the eCATT system apply.

This is custom documentation. For more information, please visit the SAP Help Portal 6