UFT IDE Overview
Keyword and expert view
Record and Play
3. UFT IDE Overview
UFT IDE consists of
Solution Explorer shows all the components associated with a test in a hierarchical manner. To see this pane, go to
View > Solution Explorer.
It contains all the menu links.
It shows the test details like author , created by, Test add ins, Description and facilitates addition and modifications
of new settings. To view this pane, choose View > Properties.
The tool box conatains the list if library and local functions and object repository and allows user to drag and drop
the same. To view this pane, choose View > ToolBox.
Output tab allows user to view the run time output. To view this pane, choose View > Output.
The data tab shows data related to test in a spreadsheet. To view this pane, choose View > Data.
The error pane shows all detected errors. To view this pane, choose View > Errors.
5. Keyword and Expert View
Keyword view facilitates user to enter and view code in a tabular format, User can generate steps, add parameters
and perform operations.
User can easily add steps and understand the flow.
Does not require any coding skill.
User can choose keyword view from View >Keyword View.
Expert view facilitates user write code in a VB Script, User can generate code, debug and run it.
User has to write a code in VB script
User can choose keyword view from View >Editor.
7. Record and Play Back
Record and playback is a functionality which allows user to record user
actions and play them back.
After recording UFT generates the code , which can be played back to
simulate recorded actions.
For the web based testing, recording is supported on Internet Explorer
both 32 and 64 bit version and even on Apple safari (on Remote Mac
Recording is not supported on firefox or chrome browsers, although it can
execute the scripts on these browser with some modifications.
8. Modes of Recording
Normal Recording : This is the default Recording mode that records the
objects and the operations performed on the application under test.
Analog Recording : This records not only the keyboard actions but also the
mouse movements relative to the screen or the application window.
Low-Level Recording : This records the exact co-ordinates of the objects
independent of the fact whether UFT recognizes the object or NOT. It just
records the co-ordinates, hence does NOT record mouse movements.
Insight Recording : UFT records operation based on its appearance and
NOT based on its native properties.
9. Object Repository
Object repository is a container which contains all the objects and stores
its unique properties by which it will identify the objects.
UFT has a utility– Object Spy which helps UFT in identifying the unique
properties of the object and stores them in OR.
There are 2 Types of Object Repository (OR)
10. Test Results
This window shows the test summary after each execution of test.
It consist of the following
Test passed and Test Failed
The test results can be exported following file formats
We can configure the test to take screen shots in case of errors and warnings
We can also configure defect tracking tool to report defects upon error.
12. Check Point
Checkpoint refers to the validation point that compares the actual properties of object
with expected value.
There are several checkpoints available in UFT
Standard Checkpoint Compares object value property
Page Checkpoint Compares no. of links, created time, page properties
Bitmap Checkpoint Compares 2 bitmaps
Image Checkpoint Compares image properties
Text Checkpoint Compares text value of objects
Accessibility Checkpoints Checks w3 standards of the site
Database Checkpoints Compares data values from database
Table Checkpoint Compares values in a webtable
XML Checkpoints Checks content in XML
13. Error Handling
Error handling catches the error and handles them within the code.
Types of Error handling Methods :
SNO Error handling Methods Description
1 Error Handling Methods Using QTP Test settings, Errors can be handled in QTP.
2 Synchronization Matches the AUT and automation script time by adding wait or adding
3 On error method On error method is used to handle any runtime errors and decide the
flow of the test, Eg: On Error resume next.
4 Recovery Scenarios Recovery Scenarios handle the unexpected errors which occur at run
5 Reporter Objects Reporter Object helps us to report an event to the run results. It helps us
to identify if the concerned action/step is pass/fail.
6 Using Err object Err objects are used for storing errors generated at run time.
7 Conditional statements If else statements can be used to write conditions to handle errors.
14. Recovery Scenarios
Recovery Scenarios handle the unexpected errors which occur at run time.
Recovery scenario consists of
Trigger Event - The action or event which interrupts the application. For E.g.: Pop Up.
Recovery Operations - The operation which helps to recover from that scenario. E.g. : Closing
the pop up.
Post Recovery Test Run – The instruction on how the rest of the test should run and continue.
Eg: Repeating the test or skipping it etc.
Recovery scenarios are saved in recovery scenario files having the extension .rs.
A recovery scenario file is a logical collection of recovery scenarios, grouped according to
your own specific requirements.
15. Author Biography
Professional History and Credentials:
Archana Krushnan is currently working as Test Analyst at Nihilent Technologies Pvt
Ltd. She has been in the field of Software Testing for more than 5 years and
worked on several domains such as Telecom, Ecommerce and Healthcare. She has
previous experiences of working with companies like Reliance Communications Ltd
and Fab.com. Her interests include exploring new things in testing and sharing on
16. Thanks !!!
Prepared By :
For any queries Please email,
Email : email@example.com