UFT One provides the following recording modes .
- Normal Recording Mode
- Analog Recording Mode
- Low-Level Recording Mode
- Insight Recording Mode
- UI Automation Recording Mode.
Normal Recording Mode :
This mode is the default and takes full advantage of the UFT One test object model, recognizing the objects in our application regardless of their location on the screen.
Analog Recording Mode -
Records the exact mouse and keyword operations that we perform in relation to either the screen or the application window.
This mode is useful for recording operations that cannot be recorded at the at 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 Run Analog statement is added to out action or component, which calls the recorded analog file.
Note - we cannot edit analog recording steps from within UFT One.
Analog recording requires more disk space than normal recording mode.
Low-Level Recording Mode -
This mode enables we to record on any object in our application, irrespective of UFT recognizes the specific object or the specific operation.
This mode records at the object level and records all run-time objects as either window or WinObject test objects.
It is Used when the exact coordinates of the object are important for our tests, A good example would be hashmaps where clicking different sections of a picture take you to different links.
Used when recording tests in an environment or an object not recognized by UFT. Low level mode records the x, y coordinates on any clicks.
Low-Level recording mode following methods are supported.
Window test objects:
Activate
Click
DblClick
Drag
Drop
Maximize
Minimize
Restore
Type
WinObject test Objects
Click
DblClick
Drag
Drop
Type
Note-
- Low-Level recording mode is not fully supported for multibype 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.
InSight Recording -
Records on any object displayed on our screen, whether or not UFT recognizes the objects technology an 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 control from an environment that UFT does not support or even from a remote computer running a non-window operating system.
When UFT runs the test or component, It recognizes the controls in the application by matching them to the images saved with each of the sight test objects.
Insight test objects are always created as children of the UFT test object that contains them, we can move the insight object under a different parent object in the object repository.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.