eCATT enables you test all mySAP applications, including those running outside of SAP GUI for Windows and SAP GUI for Java. To cover all the test possibilities, eCATT has four different drivers, each specialized for a particular task. You can use several drivers in the same test script. You choose the most appropriate drivers for the application under test.

The non-user interface is for testing back-end R/3-specific modules, such as function modules and BAPIs. It should be the preferred driver for interface tests in the mySAP environment. It is fast, efficient, and suitable for load testing.

Use TCD for testing transactions, especially those that do not use controls.

TCD has the following advantages:

• It has a built in screen simulation for standard screen elements.
• No GUI is required for playback.
• It is suitable for load testing.

The TCD command has the same limitations as the CATT function of the same name. The flow of data to and from controls, as well as screen input values, are recorded. When the test script runs, the controls are deactivated and the user's actions are simulated by reading the recorded data flows.

Use GUI scripting for testing applications that use controls in SAP GUI for Windows and SAP GUI for Java.

It requires GUIs for playback and is not suitable for load testing.

If you have the appropriate supported tools from third parties, you can test applications that run under GUIs other than SAP GUI for Windows and SAP GUI for Java.