To begin automation, the first step every tester learns is ‘Record-and-Play‘. Why? It’s the easiest 🙂 Also, during automation there will be cases when we need to record object using its properties, or continuous mouse movements, or object’s co-ordinates, or to record images of the object. The purpose defines the type of UFT Recording mode you select.
Record and Playback
Recording a test corresponds to recording the user actions of the application under test so that UFT automatically generates the scripts that can be played back. It is used as the preliminary investigation method to verify if UFT can support the technology/application and to create a test script to check the basic functionality of an application that does not require long-term maintenance. It is one of the start point for any Automation, post which the scripts are enhanced with Object repositories, Checkpoints, Parameterization, etc.
Records the objects (using its properties) in the application and the operations performed on them. This mode is the default and takes full advantage of UFT’s Test object model.
‘Record’ (menu bar option) >> ‘Record’ | Select “Record” option from Toolbar | Use short cut key “F6”
Record the exact mouse and keyboard operations you perform in relation to either the screen or the application window – UFT records and tracks every mouse movement as you drag it around a screen or window. This mode is useful for recording operations that cannot be recorded at the level of an object, for example, recording a signature produced by dragging the mouse. Note: You cannot edit analog recording steps from within UFT. The main funda behind this recording mode is it records continues mouse movements in the form of a track and save this track file on your computer.
Records at the object level and records all run-time objects as Window or WinObject test objects. Use low-level recording for an environment or on an object not recognized by UFT. The recording is done on the bases of co-ordinates not its properties and i.e. QTP/UFT records the co-ordinate location of the object on which action has been performed.
One of the main competitive advantages of HP Unified Functional Testing (UFT) is its wide support for different technologies. But even after supporting multiple technologies, there are always technologies that that are too rare or complex for UFT to identify objects based on its properties.
In order to bridge the gap, UFT 11.50 introduced Insight, an image-based form of automation. Insight uses an image in order to identify a test object and is fully integrated into UFT so it can leverage the full range of UFT capabilities such as Record, Learn and Visual Relations Identifiers to name but a few. Insight can be used on unsupported technologies such as Flash, or even on a remote desktop connection. An Insight Object’s description is based on an image, instead of its properties. UFT inserts the actual image of the test object into the script, which has the added benefit of making the test understandable and maintainable.
Double clicking the Insight image will open the test object in the object repository. Insight does not use simple image matching. Instead, Insight looks for controls that are similar to the image in the description. The best match is always used.
- The first preference should always be Normal recording mode. Use Analog or Low-level recording only when normal recording mode does not accurately record your operation.
- Analog recording and Low-level recording require more disk space than Normal recording mode