In the preceding QTP coaching session, we compiled a comprehensive list of all checkpoints offered in QTP. These checkpoints are fundamental in inserting verification points into QTP examinations to equate the existing and anticipated object values. The comparison establishes whether the test is successful or unsuccessful.
=> Explore the QTP Training Tutorials Series Here
Recommended IPTV Service Providers
- IPTVGREAT – Rating 4.8/5 ( 600+ Reviews )
- IPTVRESALE – Rating 5/5 ( 200+ Reviews )
- IPTVGANG – Rating 4.7/5 ( 1200+ Reviews )
- IPTVUNLOCK – Rating 5/5 ( 65 Reviews )
- IPTVFOLLOW -Rating 5/5 ( 48 Reviews )
- IPTVTOPS – Rating 5/5 ( 43 Reviews )
Today, we will concentrate on how to use the QTP Standard and Image checkpoints.
Standard Checkpoint
#1) It is employed to validate an object property’s value.
#2) It correlates the expected value to the actual value while the program is running.
#3) When recording or amending a test, a standard checkpoint can be incorporated.
#4) It can also be implemented with the assistance of the active screen. Adequate object information on your active screen is vital for successful checkpoint integration.
Taking an instance, if the active screen contains elements like a login edit box, password edit box, and OK, Cancel, and Help buttons, and if you want to validate the visibility of the Cancel button, you would place a checkpoint on the “Visible” object property of the Cancel button.
During recording, if only Login, Password, and OK operations are apprehended on the active screen, the Cancel button can’t be chosen to insert since the active screen lacks information about the button.
Hence, it’s critical to record all items on the page before inserting a checkpoint via the active screen. This ensures the active screen has all the necessary information for checkpoint placement.
#5) The “Checkpoint Properties” dialog box can be utilized to alter the properties of a checkpoint.
#6) Every checkpoint that is established is stored in a local object repository and, when needed, can be transferred to the shared object repository.
#7) It is compatible with all environments where the suitable add-ins are enabled.
#8) Several objects, including web images, edit boxes, static text, and web tables, among others, can be employed for standard checkpoints.
Procedure to Include a Standard Checkpoint During Recording
Step #1: After initiating a record session, select Insert -> Checkpoint from the dropdown menu.
Step #2: – To get the same outcome, click on this icon.
Step #3: A sequence of related checkpoints applicable to the current or chosen step will be displayed.
Step #4: Choose the checkpoint type, for instance, “Standard.”
Step #5: The QTP interface will be hidden, allowing you to select the object in the AUT (Application under Inspection) over which the checkpoint should be implemented.
Step #6: After choosing the object, the properties dialog box should emerge.
Step #7: Hearken the object and hit OK, the checkpoint properties dialog box should surface.
Step #8: Pick the properties to be examined and hit OK. In this illustration, we are opting for the name property. These properties can be tweaked to apply a fixed value or parameterization. Furthermore, a timeout parameter can be set.
QTP waits for the duration specified for the object’s property value to be accomplished prior to completing the check.
Step #9: Set the constraints and select OK.
Step #10: This is how the checkpoint looks in the keyword view.
Step #11: The following code is exposed in the expert view.
Browser("Gmail: Email from Google").Page("Gmail: Email from Google").WebButton("Sign in").Check CheckPoint("Sign in_2")
Procedure to Include a Standard Checkpoint During Modification
#1) Active Screen: Right-click an object on the Active Screen and pick the option to incorporate a standard checkpoint. Follow the steps outlined above to finalize the insertion.
#2) At any stage during the QTP test, pick the menu option “Insert -> Checkpoint” and select “Standard checkpoint”. Follow the steps outlined above.
How to Access and Adjust Checkpoint Properties?
Checkpoint properties can be adjusted as needed post-creation using the “Checkpoint Properties” dialog box.
This dialog can be accessed in the following ways:
#1) During the creation of a checkpoint, this dialog is employed for the initial property definition.
#2) Choose an existing checkpoint statement in the Keyword view, right-click, and pick “Checkpoint properties”.
#3) Unlock the object repository to see the available properties.
All the properties of a checkpoint can be modified as needed using this dialog.
With the exhaustive steps provided above, you are able to incorporate standard checkpoints into different circumstances and modify them in several ways. We will next enumerate the properties and characteristics that are exclusive to each checkpoint type.
Bear in mind that the procedure for incorporating, employing, and modifying checkpoints is largely similar for the majority of checkpoints. The approach detailed above can be generically applied to other checkpoints unless explicitly mentioned otherwise.
Image Checkpoint
A slight difference in the standard checkpoint arises when it’s implemented to web images.
If the object where the checkpoint is inserted is a web image, the subsequent dialog box will appear:
Observe that this dialog is almost indistinguishable from the “Checkpoint Properties” dialog, but is exclusively for images.
The sole supplementary parameter is the “Compare Image Content” checkbox. When checked, the image during runtime is matched with the one accumulated during checkpoint formation to verify if they’re precisely the same. If they align, the test results will only display the identical image. If they vary, both images will be showcased in the test results.
Taking an illustration, when trying to encompass a standard checkpoint on one of the images from the Active Screen on the Gmail page, the consequent dialog surfaces:
In this example, no modifications have been made to the dialog, although you have the freedom to adjust the settings and select OK.
Here is how the implemented checkpoint will appear:
Expert View Code:
Browser("Gmail: Email from Google").Page("Gmail: Email from Google").Image("nosign-r42").Check CheckPoint("nosign-r42")
That concludes our session for now! We’ll go over the remaining checkpoints in forthcoming sessions. Feel invited to ask any queries.