Testing Applications

eCATT enables you test all SAP applications, including those running outside of SAP GUI for Windows and SAP GUI for Java. To cover all the test possibilities, eCATT has different drivers (commands), each specialized for a particular task. As new SAP technologies, such as Web Dynpro, are introduced, new drivers are created to enable testing of applications based on the new technologies. You can use several drivers in the same test script. You choose the most appropriate drivers for the application under test. The following flow chart shows the decision process that you should use.

Non-User Interface

The non-user interface is for testing back-end modules, such as function modules and BAPIs. It should be the preferred driver for interface tests in the SAP environment. It is fast, efficient, and suitable for load testing. The relevant eCATT command is FUN.

TCD

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.

GUI Scripting

Use GUI scripting (SAPGUI command) 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.

The commands GETGUI and CHEGUI are useful for reading and checking screen elements. They allow the user to query the current state of controls on a screen or subscreen.

Web Dynpro

Web Dynpro applications, whether developed in ABAP or Java, can be tested using the WEBDYNPRO command. This is independent of the SAP NetWeaver Developer Studio, although a plug-in to the Developer Studio does allow scripts to be recorded that are usable by eCATT.

A simulator allows the easy parameterization of UI elements.

You can display the recorded Web Dynpro context in the eCATT structure editor. Here you can change the data and the actions performed on the screen. Changes are automatically reflected in a file that is sent to the XML client in the Web Dynpro runtime.

Web Services

Web services can be tested using the WEBSERVICE command.

ABAP Objects

eCATT provides a set of commands for testing global ABAP object classes.

Business Configuration Sets and Other Customizing

You can test Customizing changes, whether made by BC Sets or other means.

Interface to External Tools

When particular test scenarios are not covered by the built-in capabilities of eCATT (for example, testing in the SAP GUI for HTML, non-SAP applications, and so on), the provision of an external interface still allows eCATT to be used as the central test tool by integrating an external tool that can record and replay these scenarios.

You need to get the appropriate supported tools from third parties whose products have been certified against the BC-eCATT interface.

Inline ABAP

Inline ABAP is useful for working with database tables, SQL queries, ABAP language type pools and the like. It allows you to exploit almost the full strength of the ABAP language within an eCATT test script. Inline ABAP can manipulate the local variables of the eCATT test script.