QTP Tutorial #16 – Steps to Insert XML, Accessibility, and Database Checkpoints

Today we will continue with remaining QTP checkpoints i.e XML, Accessibility, and Database Checkpoints. This is the last tutorial on QTP checkpoints. We have covered details of all QTP checkpoints in last 4 tutorials.

XML checkpoint:

By adding XML checkpoints to your test, you can check the contents of individual XML data files or documents that are part of your Web application.

  1. You can perform checkpoints on XML documents contained in Web pages or frames, on XML files, and on test objects that support XML.
  2. An XML checkpoint is a verification point that compares a current value for a specified XML element, attribute and/or value with its expected value. Continue reading →

QTP Tutorial #15 – Using Text Area, Table, and Page Checkpoints in QTP

In the last article, we were discussing the ways in which QTP can compare text. We also saw how standard checkpoint can be used to check the text and discussed the text checkpoint in detail. The next checkpoint is Text area checkpoint. Let’s begin exploring it.


Note – We have aggregated links to all these QTP training tutorials on this first QTP tutorial.

Text area checkpoint:

  • This is used for windows applications.
  • Compares a text string within a defined area according to the criteria specified.
  • Defining the properties for this checkpoint is almost the same as that for a text checkpoint.
  • Continue reading →

QTP Tutorial #14 – How to Add Bitmap and Text Checkpoints in QTP Tests

Let us just continue our journey of familiarizing with the important QTP concept of adding checkpoints in today’s QTP tutorial too. In a previous tutorial, we learned how to add Standard and Image checkpoints in QTP tests.

In today’s QTP training session we will learn how to insert Bitmap and Text Checkpoints in QTP tests.

Bitmap checkpoint

A lot can be inferred from the name of this checkpoint itself.  However, it is often confused with the Image checkpoint.

Differences between Image and Bitmap checkpoints:

Difference #1: Image checkpoint works only on Web environment whereas Bitmap checkpoint works on any supported environments.

Difference #2: Bitmap checkpoint can be used to compare an area of an application Continue reading →

QTP Tutorial #13 – Steps to Insert Standard and Image Checkpoint in QTP Tests

In the previous QTP training session, we listed all the checkpoints that QTP provides. All these checkpoints are very important to insert verification points in QTP tests to check if current and expected values of an object match or not. This determines the PASS or FAIL status of that test.

In today’s tutorial, we will deal with QTP standard and image checkpoints in detail.

Standard Checkpoint:

1) It is used to check the Object Property value.

2) Compares the expected value with the actual value during runtime.

3) It can be set during recording or editing a test.

4) The active screen can also be used to insert this checkpoint. It is important that sufficient information be available in the active screen to be able to insert a checkpoint.

For Example: If there is a screen with, Login edit box, Password Edit box, OK, Cancel and Help buttons. We need to check if the Cancel button is visible. We are trying to achieve this by placing a checkpoint on Continue reading →

Adding Conditional and Loop Statements in Keyword View – QTP Tutorial #4

Let’s continue HP QTP training series with our next QTP tutorial #4 – Adding Conditional and Loop Statements in Keyword View.

Understanding QTP keyword and expert view feature in detail is very important to learn QTP. So we have divided this Keyword View tutorial into four articles. This is the third article in Keyword View series.

Check out all the articles in this QTP training series @ Quick Test Professional (QTP) training series

[Note – Click on any image to enlarge]

Condition and Loop Statements in Keyword view

A quick recap of what we learned so far

We acquainted ourselves with the Keyword View of the QTP and we are trying to understand the different features this view provides and see how these features can be used to write effective tests. To do that, we are working with a Continue reading →