UFT works directly with the SAP GUI Scripting API to record your operations. Therefore, UFT adds steps to your test or business component only when API events are sent to the server. This means that while recording a test or business component, you may perform several operations on your application before the corresponding steps are added. When you perform a step that sends information to the server, UFT inserts steps with the relevant Windows-based SAP objects.
Suppose you record the steps of filling in a Price Simulation for Material form. You select the three check boxes in the form (Incl. cash discount, Delivery costs, and Effective price) and click Continue. When you click the Continue button, information is sent to the SAP server, and the steps in which you select the check boxes and click the Continue button are added to your test at once:
Suppose you select a radio button to change the reporting period in the Reconcile Plan Versions transaction of your SAP GUI for Windows application. This radio button is labeled Current Year.
UFT uses the SAP GUI business component type (41) to identify the object as a SAPGuiRadioButton object. It creates a SAPGuiRadioButton test object with the name Current Year and records the following properties and values as the description for the radio button.
Note: The guicomponenttype and name property values are supplied by the SAP GUI Scripting API.
UFT also records that you performed a Set method to turn ON the radio button.
UFT adds a step as follows:
During the run session, UFT looks up the description for the SAPGuiRadioButton object with the name Current Yearby searching the object repository. UFT finds the following description:
guicomponenttype:=41 name:=PCHZTR_Y attachedtext:=Current Year
UFT then looks in the application for an SAPGuiRadioButton object that matches the above description. When it finds the object, it performs the Set method on it to change the value of the field to ON (selects the radio button).