UFT

What Are The Checkpoints Available in QTP/UFT

Checkpoints in Automation UFT
Checkpoints in Automation UFT

Automatic Web site Testing using Checkpoint

You just completed developing your company’s web site. You have analyzed it you and experienced other business staff take a look at it. The web page now goes dwell. A several weeks afterwards you commence finding e-mail from irate shoppers who complain that they are not able to location their orders mainly because specified actions in the “Obtain Now” course of action give faults.

You immediately deal with the difficulty. A several times later on you get complaints about some other difficulty and you once again react immediately to resolve the internet site. This continues for a few months till the complaints eventually halt and issues stabilize.

At this place you make some enhancements to your site. A number of days later on a customer electronic mail alerts you to the truth that in the approach of earning this improvement you “broke” a thing else on the web site.

Again you expend time to obtain and correct the trouble but by now you are perplexed and not a tiny disappointed. These troubles have charge you lots of clients in the final couple of months and possibly spread sick will across the broader consumer neighborhood. It appears to you that the only way to have detected these issues in advance of they went “dwell” was to have used a significant military of program testers, a little something your company is not able to afford to pay for.

Enter automatic software package testing. When almost nothing can switch very good human testers, wide examination coverage needs some degree of program automation for it to be economically feasible. Automated tests instruments can give a massive workforce multiplier and do a really very good position complimenting human testers.

Every transform to your website no make a difference how compact necessitates comprehensive screening to ensure that very little else was impacted. This gets to be really time consuming really rapidly owing to the massive range of doable conditions to examination. A strategy whereby assessments are automated working with software package becomes an financial requirement.

There are two courses of automatic tests equipment. The initially variety, practical and regression tests resources, will help to make absolutely sure that the internet site behaves as it should: for illustration if a shopper clicks on button X, web site Y is exhibited with out faults. Functional and regression testing tools are capable to automate a large amount of eventualities to make sure that your web page functions as meant.

The second sort, load tests applications gauge how perfectly your internet site performs when subjected to a large pressure, this kind of as a significant range of simultaneous end users. I will be speaking about load testing in a individual report.

I will now give you an overview of the simple properties of purposeful tests. In advance of you can commence any type of useful check automation you will need to have to discover the examination scenarios you want to automate. When this is carried out, you will need to crank out take a look at scripts that go over these scenarios.

A purposeful tests tool will usually file person interactions with a web site. As you complete various operations on your web site or application, the resource documents each and every stage. When you finish recording, it generates an automated script from your interactions with your web site. Alternatively you could use the instrument to construct the script by hand. Typically testers are likely to do a blend of the two. They will use the recorder to produce the standard framework of their scripts and then tweak the scripts by hand to integrate unique cases.

Scripts can be graphical and/or textual content dependent in nature. A superior practical screening device does not need customers to have a programming background. End users not proficient in programming will do the job predominantly with graphical scripts. In most instruments graphical scripts will commonly display all interactions in a tree structure and consumers can edit any node of the tree to modify the script. Some customers nonetheless, who have programming backgrounds could wish to program their scripts. These end users will normally perform with a textual content script written in a regular language these types of as JavaScript or VBScript.

At the time you have generated your script you will require to insert checks in your scripts to examination if your web site is functioning the right way. These checks are generally named checkpoints. A checkpoint verifies that values of a house received when tests the web site match envisioned values. Checkpoints permit you to established the requirements for evaluating anticipated values with obtained values. The anticipated value of a assets is derived from recording interactions with the website website. It is viewed and modified from checkpoints. The latest price is retrieved all through replay (i.e. all through the execution of the examination case).

There are several diverse types of checkpoints. A webpage checkpoint verifies the resource of a webpage or body as effectively as its statistical homes. You can test for damaged back links, validate connection URLs, picture sources, the hierarchy of HTML tags or even the overall HTML resource of the Website web site or frame. You can also established thresholds for the loading time of a page. A text checkpoint verifies that a provided text is displayed or is not displayed in a specified region on a world wide web page. A world wide web item checkpoint verifies the houses of a web item e.g. the price of an HTML Enter field. A databases checkpoint verifies the contents of a databases utilized by your web site.

When you replay a examination script, the tests instrument will open the recorded application and execute the recorded steps in the exact same sequence they have been specified in the script. As it replays the script it will also operate through all the checkpoints you have inserted into the script. In addition, you can exam your application’s conduct with varying details inputs. For case in point you can test to submit a page soon after moving into distinct values in the edit box of a net website page. At the end of the replay a comprehensive report is typically be generated.

Practical check automation will allow you to automate the repetitive testing of a big range of eventualities throughout your site. Purposeful testing equipment are an important weapon in your enhancement arsenal whose use delivers a massive productivity get and allows for tiny testing teams to accomplish drastically more function. There is a quite robust financial circumstance for the use of Practical Testing Equipment as part of the advancement and deployment cycle of a site.

Without any further do lets come back to the topic.

Automation can not test all cases. It requires a stable environment to work.All automation tools nowadays capable of storing screenshot and video. So execution verification and debugging is very easy.Every automation has its own reporting process.Most of the functional automation cases are capable of providing value to performance testing.Mostly automation scripts are for regression testing.
With the advancement of functional automation testing, it became very important to verify the flow. Verification can be of link,text,count of links,appearance of images,images etc. QTP provides different approaches to verify these points.Checkpoint approach is one of them. Check points play very important role while designing our automated scripts. It really checks if whatever we are expecting are there or not.Check point is a verification point, it takes expected result from the user and compares with actual results during execution and provides test results. Mainly Checkpoints are used for Data validation.When combined with regular expression,it can be a great tool for assertion in QTP/UFT.
In expert view once Check point is configured QTP/UFT prompts to use the same.

So a checkpoint tells us if the website or application under test is functioning properly or not by comparing a current value for a particular property with the expected value. Once we add a checkpoint UFT adds the same checkpoint to the current row in the keyword view and adds a checkpoint statement in the Expert view. By default the checkpoint takes the name of the test object(on which the checkpoint is performed). However we can change the name by renaming option.

However we need to keep in mind that checkpoints can not added manually. They can only be inserted via UFT interface.

Results of the checkpoints can be viewed in the test result only.

There are 10 Checkpoints available in QTP: They are listed below:

Serial No#Checkpoint NameDescriptionExample or use
1Standard checkpointChecks values of objectsMostly check if the checkbox is checked or editbox is enabled etc
2Text checkpointChecks if the text string is displayed in correct placeCheck if the correct string has appeared
3Text Area checkpointtext area is a place in web or window based application where a long text string can be placed. This checkpoint checks if the text appeared in the defined area.Checks if the text is appear in correct area.
4Bitmap checkpointCheck an area of a web page or application after capturing it as bitmapCheck that Web page or any portion of it is displayed as expected.
5Database checkpointChecks the contents of databaseCheck that the value in a database query is correct.
6Accessibility checkpointIdentify areas of website to check for section 508 complianceMostly checks the W3C guidelines.
7XML Checkpoint (from Application)/(from Resource)Checks the data content of XML documentschecks the contents of an element to make sure that it’s tag attributes and values have not changed.
8Page checkpointChecks the characteristics of a webpagelike load time,checks if the page is loaded correctly, checks the broken links
9Image checkpointChecks the property value of an image.Checks the source of a file and correctness about the same.
10Table checkpointChecks the information in a table.Checks if the value in a table cell is correct.

Note 1: From 6 to 10 checkpoints are only for Web.

Note 2: From 9 to 10 checkpoints are hidden checkpoints, we can insert these checkpoints through standard checkpoint.

How to create Checkpoints in UFT?

We can insert standard checkpoints in 3 ways.
  1. Through Expert view
  2. Through keyword view.
  3. Through Active screen.
  4. Through Insert Menu.

Insert checkpoint through Expert view:

  • Place the cursor on the step in an Expert view
  • Right click
  • Insert Standard Checkpoint option.
  • Select Properties
  • Pass Parameters either through constant or Parameter
  • Click on OK.

Insert checkpoint through Keyword view:

  • Select the object through Keyword view.
  • Select Insert standard Checkpoint option
  • Select properties
  • Pass parameters (Constant or Parameter)
  • Click on OK
  • Select Insert statement option
  • Click on OK.

Insert checkpoint through Active screen:

  • Place the cursor on the required object in Active screen area.
  • Right click
  • Select standard checkpoint option
  • Select Properties
  • Pass Parameters either through constant or Parameter
  • Click on OK.

 Insert Checkpoint through Insert Menu:

  • Keep tool under recording mode
  • Place cursor in desired location
  • Insert
  • Check point
  • Standard checkpoint
  • Show the object
  • click ok
  • Select property and enter expected results
  • Click Ok and stop Recording.

Where Checkpoint Information are stored?

These checkpoints can not be added manually they can only be inserted via QTP’s/UFT’s recommended way to insert or via QTP’s interface. Remember here except standard checkpoints, all checkpoints need to configure during recording mode. So please do it during recording phase only.

QTP stores the checkpoint information in the Action’s resource.mtr location which is located in the test script directory (/Action#/resource.mtr, where Action# is the action
containing the checkpoint).
Ex:
If your checkpoint is in ActionX{x may be 1,2,3,…N} of the test script MyTest,
the path would be “MyTest/ActionX/resource.mtr”.
The checkpoint information is stored in binary form. It is better if we do not alter/ manipulate these files.But if you are comfortable with this you can alter and use according to your need.

The checkpoints information get stored in Object Repository. “.mtr” file .That  is inside the local action folder. That’s why we will capture all these checkpoints during record mode.

Result of checkpoint can be viewed in the test result window. In case if we want to modify the checkpoint, then just right click on the checkpoint and change the property of the object.
It is seen that many a time test engineers keep changing these property to test different check points,but this is not good for maintainability. As per best practices , we must create different checkpoints for different testing.

Apply Parameters in Checkpoints

Using parameter option in every checkpoint we can check every property and data with multiple expected values.

Navigation:

  • Start recording
  • Insert a checkpoint
  • Standard checkpoint
  • Select number of properties by putting tick mark in Checkpoint properties.
  • Click on Parameter option
  • Change the expected values by selecting appropriate parameter name if required
  • Click on OK
  • Pass multiple expected values on data table.

Standard Checkpoint:

It checks object property values. We can use this checkpoint for checking any property value for a web or application under test. The standard checkpoint evaluates the expected values during a run session.
Standard checkpoints can be created for all supported testing environments(if the correct addins are loaded).
Standard checkpoint can be applied to the following objects:
  • Image
  • Tables
  • Webpages properties
  • Other objects

Using standard object checkpoint, we can verify all properties of a single object at a single go.

How to insert Standard Checkpoint?

It is described above . Please refer the article.

Navigation for Editing standard checkpoint

  • Select Checkpoint statement and right click
  • Choose checkpoint properties option
  • Modify the value
  • Click Ok.

Navigation for Deleting standard checkpoint:

  • Select Checkpoint statements and right click
  • Choose delete option.

Inserting Standard check points through active screen:

  • View
  • Active Screen
  • Place cursor in desired location
  • Place mouse pointer on active screen & right click
  • Choose insert standard checkpoint option
  • Click ok
  • Enter expected result
  • Click ok
Note: Inserting Standard check points through keyword view same as in expert view.
Note:

Mainly below can be tested through QTP/UFT Standard Checkpoints…

  • Image
  • Web Table
  • General window table
  • Web page general properties
  • Any custom property for web

Example:

Window("X").WinButton("Y").Check CheckPoint("CheckpointName")

Accessibility check point:

Like another checkpoints,QTP/UFT provides check point to check websites.web industry is becoming boom now. Designers create a lot of webpages with their customized codes,logos,pictures etc. But they must follow the w3 school’s guidelines for developing web.Mostly it is based on customer’s requirements and guideline that abide by the W3 school’s guidelines.

Accessibility check point:

It verifies whether the webpage in our web application is developed according to W3C (World Wide Web consortium) Rules and Regulations.

This can be configured as below written:

Active X control check

  1. alt property for images check
  2. Applet check
  3. Frame title check
  4. Multimedia link check
  5. Server side image check
  6. Table check

 

Configuring accessibility checkpoint:

Tools menu–> options–>web–> advanced–> check/uncheck items–> click apply–> click ok
How to insert:
under recording mode with web environment >insert>checkpoint>accessibility checkpoint>show the webpage>click ok>click ok>stop recording.

Database Checkpoint:

When we talk about the client server architecture, we talk about  front end and back end. So whenever we give any value from front end it stores data in back end database. Database checkpoint checks the contents of database accessed by application(front end). Database check points creates a check on record set.
QTP/UFT captures the the current record set and treats as it as Expected data.However Database can be inserted into test or components and it can be modified as per our need.here we do not need to put tool under Recording mode and we do not need AUT since data is from back end.There are two ways by which we can configure database checkpoint:
  1. Microsoft Query builder
  2. Manual query creation

   Navigation:

Insert  Menu > checkpoint > Database checkpoint >choose “specify SQL statement manually” option >click next > click create > select machine data source > Select DSN (QT_flight32) > click ok > enter SQL statement (select * from orders) > finish > click ok.

BitMap Checkpoint:

It compares bitmaps; we can compare complete bitmaps as well as part of the bitmaps.Mostly we use to check if selected area of a webpage is bitmap image or not.

Navigation:

Keep tool under Recording mode > Insert menu > Checkpoint > Bitmap checkpoint > show the Bitmap >click ok >select “check only selected area” option if we want to compare part of the bitmap > click ok >stop recording.

While testing map,Zooming functionality We use Bitmap frequently.

Text Area Checkpoint:

It checks the text area present in the application.Sometimes we say that TextArea check point is nothing but text check point.

Navigation:

Keep tool under Recording mode > Insert menu> Checkpoint > Text area checkpoint > Mark the area of text > select one or more options (Match case, ignore spaces, exact match, text not displayed.)
Click ok and stop recording. Mostly while after doing some operation if we are expecting some text to be appeared in the application, We use this type of check point.

Like–after successful login Welcome UserName should present in the application.
or after successful upload of a file Uploaded successfully text should be present in the application.

Text Checkpoint:

It Checks object’s text property value in different ways. Text checkpoint checks that a string is displayed in the appropriate place of our application or on a webpage.Using text checkpoint we can verify the text present in object and also can verify selected string in object.

Text Recognition Configuration

This feature enables you to configure how UFT identifies text in our application. We can use this pane to modify the default text capture mechanism,OCR(Optical Character Recognition) mechanism mode, and the language dictionary the OCR mechanism uses to identify text.

Navigation for Text recognition configuration
  • Go to Tools
  • Options
  • General
  • Text Recognition

Navigation to insert Text checkpoint:

  • Keep tool under Recording mode
  • Insert menu
  • Checkpoint
  • Text checkpoint
  • Show the object
  • Click ok
  • Select options
    (Match case; ignore spaces, exact match, text not displayed.)
    We can select one or more options > click ok & stop Recording.We can insert a text checkpoint while recording a script in qtp.

Example:

If we want to insert a text checkpoint for agent name in sample Flight application.follow the steps

  1. Click on record button
  2. Invoke the Flight application
  3. Insert the agent name
  4. In qtp,uft click insert menu
  5. Select the text checkpoint option
  6. Place the cursor over the Agent name text field.
  7. Select the text checkpoint properties
  8. Click on ok
  9. Continue to record the remaining script
  10. Stop the recording and replay the script
  11. See the report

 

Table checkpoint:

It checks content of the web tables.like-content,cells,cells information,cells content,No of coloumn,No of rows.
Navigation: Under Recording mode under web environment > Insert menu > checkpoint > standard checkpoint >Click on the web table > click ok >(Select no of cells—pass parameters either through constant or parameter)—Click ok–>stop recording.

Image checkpoint:

It checks Image property values of an web image. Mainly location,alt property,link attached etc are checked. It is used to see if the image check point is prepared as per w3 school standard.
Navigation:
Under Recording mode with web environment > Insert menu > checkpoint >standard checkpoint > show the image > select image > click ok > click ok >stop recording.

Page checkpoint:

Mostly by this check points, functional test engineer checks the below written features:
1.number of Links,
2.Broken links
3.Images and Loading time in a web page.
4.DOM handling.
It is a hidden checkpoint;
we can insert this through standard checkpoint.
Navigation:
Under Recording mode with web environment > Insert menu > checkpoint > Standard checkpoint >show the web page > click ok > click ok > stop recording.
You can check out this link to know how the checkpoint info is saved in QTP
So the bottom line is that this check point checks the attributes of the page.

XML Checkpoint:

This is a kind of check point where test engineers checks for the content of XML.XML-extensible mark of Language is such language which is used to transfer data in web applications in Internet.

Advantages of XML:

It is compatible for all network
Secure from all network attacks(Noise & Distortion)
Independent of distance time
Connection and data transfer with Multiple languages is possible

How to Configure:

XML Check point (from Application)
It checks content of the XML file.
Navigation:
Under Recording mode in web environment > insert menu > checkpoint (from application)> show the xml pages >click ok > stop Recording.
XML Check point (from Resource)
It checks content of the XML file.
Navigation: Insert menu > checkpoint >xml checkpoint (from resource) > browse path of the XML File > click ok > click ok.
 If XML file is an individual and path available, and then we can go for inserting xml checkpoint from resource or if XML file is part of web application, separate path is not available then we can choose inserting XML checkpoints from application.
Using XML Check point we can check whether the values entered in the webpage (content) are covered into XML File.

How to validate check points in UFT?

Checkpoint returns on True or False.Based on that it can be coded..
Below is the example.

value_chkpoint = Browser(...).Page(...).WebEdit(...).Check (Checkpoint("Check1"))
if value_chkpoint then
MsgBox "Check Point passed"
else
MsgBox "Check Point failed"
end if

Share and Enjoy !

1 thought on “What Are The Checkpoints Available in QTP/UFT”

  1. Hi! This is my first visit to your blog! We are a group of volunteers and starting a new project in a community in the same niche. Your blog provided us useful information to work on. You have done a wonderful job!

Leave a Comment

Your email address will not be published. Required fields are marked *