QTP Question 20: What is the Diff between Image check-point and Bit map Check point?

What is the Diff between Image check-point and Bit map Check point?
Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly.

You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded).
Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

QTP Question 19: What are Supported Check-Points in QTP?

QTP Question 18: What is Object Spy in QTP?

What is Object Spy in QTP?

Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.

QTP Question 17: What is test object model in QTP?

What is test object model in QTP?
The test object model is a large set of object types or classes that QuickTest uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that QuickTest can record for it.

A test object is an object that QuickTest creates in the test or component to represent the actual object in your application. QuickTest stores information about the object that will help it identify and check the object during the run session.

A run-time object is the actual object in your Web site or application on which methods are performed during the run session. When you perform an operation on your application while recording,
QuickTest:

➤ identifies the QuickTest test object class that represents the object on which you performed the operation and creates the appropriate test object
➤ reads the current value of the object’s properties in your application and stores the list of properties and values with the test object
➤ chooses a unique name for the object, generally using the value of one of its prominent properties
➤ records the operation that you performed on the object using the appropriate QuickTest test object method

For example, suppose you click on a Find button with the following HTML
source code:

< type="submit" name="Find" value="Find">
QuickTest identifies the object that you clicked as a WebButton test object. It creates a WebButton object with the name Find, and records the following properties and values for the Find WebButton. It also records that you performed a Click method on the WebButton.

QuickTest displays your step in the Expert View like this:

Browser("Mercury Interactive").Page("Mercury Interactive").
WebButton("Find").Click

QTP Question 16: What is Parameterizing Tests?

What is Parameterizing Tests?
When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.