QTP Interview Questions and Answers

When the QTP program learns any new object, the program stores it in its object repository along with all its properties. QTP has two types of object repositories:

• Local Object Repository: Linked to only one test, and easy to make changes and actions with it. Here objects are saved with .mtr extension.
• Shared Object Repository: Can be used between multiple test cases, but no changes can be made here. Objects are saved here with TSR extension.

QTP has a total number of five test steps which can be executed for any test case.

• Test object identification
• Test functions
• Commenting
• Session controlling steps
• Programming logic

QTP can operate alone as well as can be work with the integrated environment.

QTP has the following phases:

• Application analysis
• Testing infrastructure preparation
• Preparation of test cases
• Test enhancement
• And, defect reporting

The user has to select Java Add-In and launch QTP. Then the tester has to record operations on the Java Tree. If any issue appears while testing, the examiner can choose Tools > Object Identification > Java, tree object and make changes in assistive and mandatory properties to enable the identification.

QTP identifies GUI object based on corresponding properties. At the time of recording, the tool will detect and store beautiful features in the GUI object’s object repository. It will compare the stored property values with the present on-screen properties to uniquely identify the GUI object.

QTP tool supports three types of recording modes:

• Contextual Recording Mode: It’s the default recording mode of QTP and recognizes test objects regardless of their on-screen position.
• Low-level Recording Mode: It records the exact x,y coordinates of mouse operations, and useful in testing hashmaps and objects not identified by contextual mode.
• Analog Mode: This records the exact mouse and keyboard movements that users perform about the application window.

An object spy is a tool present in QTP that helps testers to view the object operations and properties linked to then in AUT. The object spy can retrieve all the object properties and their values, and uniquely identify the objects with a set of features to store them.

Action split is used to split the actions in QTP to two parts.

• Splitting into two sibling actions: The action breaks here are independent.
• Splitting into parent-child nested action: This action is only conducted when the first action of parent gets executed.

Add-in is used to increase the capability of the tool. Then can be added as required to different scenarios, such as:

• To enhance system capabilities
• To load a particular function into the memory
• To improve available graphics quality and communication interface
• To access separate tasks that are needed for script execution

There are three types of actions that can be performed in QTP.

• Reusable Action: Can be used multiple times from where they are stored.
• Non-Reusable Action: Can be used a single time from where they are the store.
• External Action: Reusable but stored in external tests. Available only in read-only mode.

QTP has various checkpoints which can be inserted in the test to compare two object values, current and expected values. The tool has the following inspections:

• Page checkpoint
• Bitmap checkpoint
• Image checkpoint
• Database checkpoint
• Text checkpoint
• Accessibility checkpoint
• Standard inspection
• XML checkpoint