Testing Web Dynpro Applications
eCATT can test Java-based and ABAP-based Web Dynpro applications.
Web Dynpro Java applications can be tested with eCATT as of SAP Web AS 6.40. When testing Web Dynpro ABAP applications, there are different requirements for the central system and the tested system: The central eCATT system supports Web Dynpro ABAP as of SAP NetWeaver Release 7.0 SP20. However, the tested system must be either Release SAP NetWeaver 7.0 EHP 2 (or a higher EHP) or SAP NetWeaver 7.2 or higher.
For an overview of the possible release combinations of eCATT systems and tested systems as well as further information about using eCATT together with Web Dynpro ABAP, see SAP Note 948076.
You can record and replay applications. The relevant eCATT command is WEBDYNPRO. You can parameterize the command interface to set input values of GUI elements, and to check or get values from GUI elements.
Simulation
Based on the data in the relevant command interface, simulation allows you to visualize the relevant page and select GUI elements for creating checks and getting and parameterizing values. You can also perform these actions in the command interface itself, but using the simulator simplifies the procedure.
You can also use the simulator to display screens when replaying in the foreground.
SAP NetWeaver Developer Studio
Java-based Web Dynpro applications are developed in SAP NetWeaver Developer Studio. However, you do not need the Developer Studio to test applications with eCATT.
To allow developers to record tests without using eCATT, there is a plug-in for the SAP NetWeaver Developer Studio that allows recording and replay of Web Dynpro applications in the Developer Studio. You can import scripts that were recorded within the Developer Studio into eCATT.
Replaying Web Dynpro Applications
In the start options, you can specify whether the application is replayed in the background or in the foreground. Foreground processing uses the simulator (not a browser) and allows you to see the screens as they are replayed. With foreground processing, you can specify how long to display each screen before the next screen is processed. When searching for errors, you can display the expected screen and the actual screen simultaneously. This enables you to see whether a new version of a screen has any different interface elements or extra pushbuttons, for example.
If the application requires user authentication, you need to have entered the relevant information in the destination using transaction SM59.