We delved into the various techniques for text comparison by QTP in our prior discussion.
We also touched upon the text checkpoint intricacies and how regular checkpoints could be employed for text verification. Presently, we transition to the text area checkpoint.
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 )
Checkpoint for Text Area
- This specific checkpoint is crafted for windows applications.
- It compares a textual string within a predefined area based on specific criteria.
- Establishing properties configuration for this checkpoint resembles the methods used for a text checkpoint.
- The primary distinction between the Text checkpoint and the Text Area checkpoint, besides the environment they operate in, is that the Text checkpoint focuses on a unique object, while the Text Area checkpoint concentrates on a chosen region.
- Despite the availability of the text area checkpoints menu option throughout web app recording, its selection will trigger an error message indicating the web environment’s incompatibility with this checkpoint.
Checkpoint for Table
- This checkpoint serves to affirm whether a specific table cell contains a particular value, or to verify if the table itself possesses the specified number of rows or columns.
- When a web table or a similar table object is designated for checkpoint insertion, the attributes of the Table checkpoint are activated.
- During recording, the menu option for the Table checkpoint is “Standard Checkpoint,” hence the principles for its creation, modification, and maintenance remain the same.
Let’s illustrate with an example:
Pick a random website encompassing a web table. Launch Internet Explorer, initiate recording, and introduce a standard checkpoint by choosing the table object on the webpage.
Pick the Web Table component and press OK.
Within the attributes window, pinpoint the cell and specify whether there should be a constant or a parameterized value present.
The settings tab will outline the verification process.
Cell Identification: This section enables the user to customize settings for identifying specific rows or columns.
As mentioned above, although this built-in feature for table checking is available, its utility may be limited. There exist other functions such as GetRowCount, GetColumnCount, GetRowItem, etc. for table verification. We’ll delve deeper into this prior to moving on.
- In practical situations, verifying a single cell might prove inadequate, and constructing a separate checkpoint for each table value could become a tedious task. For instance, a 3X3 table would necessitate 9 checkpoints to affirm each cell. If the value in the first or second cell doesn’t match, it doesn’t automatically denote a faulty table, making subsequent cell verifications pointless.
- Alternatively, by examining the table and using functions like GetRowCount, GetColumnCount, and GetRowItem, a looping mechanism can be implemented to verify the table as needed and exit upon failure. Testers should ensure that appropriate test outcomes are recorded for clarity’s sake.
- Furthermore, table checkpoints might fail in instances of dynamic tables.
Checkpoint for Page
Page checkpoint is another standard checkpoint variant, which is utilized with webpages.
- Links verification
- Image source confirmation
- Checking for broken links
Let’s insert a page checkpoint and observe its functionality.
Launch Google.com in Internet Explorer or another browser which is compatible with your QTP version. Record a fresh test in QTP, select “Insert Checkpoint -> Standard checkpoint” and opt for the Web Page object.
Subsequently, the following dialog box will emerge:
As evident, each property available for verification comes equipped with a checkbox option. Users can freely select any quantity of properties as required.
Similarly to other checkpoints, each property can possess a constant value or can be parameterized.
The subsequential segment pertains to HTML verification:
- HTML Source: It checks whether the HTML code for the webpage aligns with the actual code during runtime. Users can modify it as per need while configuring the checkpoint to ensure it matches during runtime.
- HTML Tags: It verifies the HTML tags on the webpage during both recording and runtime. HTML tags can also be modified.
Section on ‘All Objects in the Page’:
#1) Links: When activated, this option validates all links. For specific link checks, users can select the “Filter Link Check” option, and a dialog box will display:
Users can opt to select or deselect specific links. The link’s URL value can either be constant or parameterized.
#2) Images: When this feature is enabled, the presence of images on the page can be validated during runtime. Choosing “Filter Image Check” grants the ability to select the precise images to be verified and the ones to be overlooked.
The following tab will display once you decide to filter the images:
As always, the values can be adjusted as needed.
#3) Broken Links: Ordinarily, this feature remains unchecked. Nonetheless, when activated, it examines the webpage for any broken links.
Users can search for broken links that exclusively inhabit the same host as the parent page. The relevant setting can be adjusted in the subsequent screen accessible via the “Tools -> Options -> Web” menu option.
Upon executing this checkpoint, any failures will be evident in the Test Results. If there aren’t any failures, the checkpoint is successful.
Several Page Checkpoint options are only accessible while checkpoint creation is in progress. They aren’t available in either the Active Screen or the Keyword View.
Conclusively, the page checkpoint:
#1) Proves valuable when verifying webpages in the web add-in for maintaining their integrity.
#2) Serves as a variation of a standard checkpoint, hence the same rules of creation, editing, and maintenance apply.
#3) Enables QTP to implement a checkpoint on every page automatically. This feature can be turned on by navigating to the “Tools -> Options -> Web -> Advanced” menu option and activating the same.
#4) Moreover, QTP can be instructed to bypass automatic checkpoint allocations. Choose the relevant option in the same window as mentioned in point 3.
With that, we wrap up the topics of Accessibility, Database, and XML checkpoints, which will be discussed in the subsequent session. We welcome any comments or questions that you might have below.