Relevant for: GUI tests and components
You can create the main body of a test or component by recording the typical processes that users perform on your application.
UFT records the operations you perform, adding them as steps to the selected test action or component.
Then, during a run session, UFT uses the recorded steps to replicate the operations you performed while recording.
While you record the steps, UFT creates test objects representing the objects in your application on which you perform operations, and stores them in the test or component's local object repository. This enables UFT to identify the objects in your application both while creating the test or component and during a run session.
UFT also enters the correct methods, and argument values for the objects in your application. During a recording session, you can also add checkpoint and output value steps, to check or retrieve values from your application.
UFT provides the following recording modes:
Note: UFT supports an additional recording mode, Standard Windows recording, which is relevant when recording tests or components on SAP GUI for Windows applications.
For details, see the SAP GUI for Windows section of the Unified Functional Testing Add-ins Guide.
Records the objects in your application and the operations performed on them.
This mode is the default and takes full advantage of the UFT test object model, recognizing the objects in your application regardless of their location on the screen.
Records the exact mouse and keyboard operations that you perform, in relation to either the screen or the application window.
This mode is useful for recording operations that cannot be recorded at the level of an object, such as a digital signature produced by dragging the mouse.
The steps recorded are saved in a separate data file stored with the action.
A single RunAnalog statement is added to your action or component, which calls the recorded analog file.
You cannot edit analog recording steps from within UFT.
Analog recording requires more disk space than normal recording mode.
For details on the available settings for analog recording, see Analog Recording
Records on any object in your application, whether or not UFT recognizes the specific object or the specific operation.
Use low-level recording:
- For recording on environments or objects not supported by UFT, if the appearance of the objects might change, but their location will not. If the object’s appearance will not change, you can use Insight recording for unsupported environments or objects.
- If the location of the object is important to your test or scripted component. This way, the step will pass only if the object is in the correct position.
This mode records all parent level objects as Window test objects and all other objects as WinObject test objects. They are displayed in the Active Screen as standard Windows objects.
The following methods are supported:
Window test objects
WinObject test objects
Low-level recording mode is not fully supported for multibyte character input.
Steps recorded using low-level recording mode may not run correctly on all objects.
Low-level recording requires more disk space than normal recording mode.
Records on any object displayed on your screen, whether or not UFT recognizes the object's technology and is able to retrieve its properties or activate its methods.
UFT recognizes objects based on their appearance, and not their native properties. This can be useful to test controls from an environment that UFT does not support or even from a remote computer running a non-Windows operating system.
For more details, see Identifying objects using Insight.
Note: Insight recording requires more disk space than normal recording mode.
To control the amount of space used, adjust the number of snapshots saved and their size in the Insight pane of the Options Dialog Box.