This is my personal blog for my software testing study purposes. The topics posted in this blog are mine and from some other sources (credits are given). I always add those topics which helps me. Hope these topics will help you guys also.
- Happy testing

Recent Posts

QTP & Keyword Driven Testing

Tricky Questions in QTP

Asset Upgrade tool in QTP

New Features in QTP 10

Sep 4, 2008

QTP Tutorials 5 - Page Checkpoint

Subscribe the QA and Software Testing Newsletter
Post Your Queries | QA and Testing - Table of Contents

SPONSORED LINKS Reading: QTP Tutorials 5 - Page CheckpointTweet this Post

Page checkpoint:It is for web applications only.Common things to check with this are load time, broken links etc.

  1. Open a blank test.
  2. Make sure that http://www.google.co.in/ is open.(Now only QTP with blank test and www.google.co.in should be open.)
  3. Click on Record. When we click on Record, "Record and Run Settings" window opens up. Go to "Web" tab and choose first option "Record and run test on any open browser." and click ok.
  4. Go to Insert (menu)->Checkpoint->Standard Checkpoint (or press F12).
  5. The mouse pointer will become hand and QTP will be minimized.
  6. Click anywhere on the white space on the Google.co.in page.
  7. It will Open "Object Selection - Checkpoint Properties" window. Click on 'Page : Google' option which has a page icon on left of it with right corner of the page slightly folded.
  8. Click ok.
  9. A 'Page Checkpoint Properties' window opens up. Let all the options be default. Click ok.
  10. Click on Stop in order to stop the Recording.

In the Expert view it will add just one line:


Browser("Google").Page("Google").Check CheckPoint("Google")


We will explore this line later on.


I ran this test by opening www.google.co.in in offline mode (not on internet). It recorded the following properties:


Property Name Property Value
load time "0"
number of images "2"
number of links "20"


Here it shows the load time as 0 because I did not open Google at the time of running the test, it was already open.


When you run it, in the results window, on left hand side, it will show (when every option is expanded):


Test Checkpoint-page Summary (where Checkpoint-page is the name with which I saved the test

Run-Time Data Table
Checkpoint-page Iteration 1 (Row 1)
Action1 Summary
Google (This will be the browser)
Google (This will be the Page)
Checkpoint "Google"


If you run this test on www.google.com it may fail.

SPONSORED LINKS

Comments :

0 comments to “QTP Tutorials 5 - Page Checkpoint”

Software testing Metrices-Test Case Review

Metrics are the means by which the software quality can be measured; they give you confidence in the product.

 

Energize your test team

You're waist deep in your third month of late nights, weekends, and shipping stress; you can see and feel your team's energy waning.

 

The Value of Positive Testing

There is a school of thought in software testing that debunks the value of positive testing. This school basically states that any test that does not produce a defect is not a good test.

Impact Analysis Checklist for Req. Changes
___    Implications of the Proposed Change* Identify any existing requirements in the baseline that

The Process of Test Process Improvement

Software testing is still a pain-in-the-neck for many organizations. Because it is only marginally addressed in software process improvement models like CMMi

 

Software Defect-bug Management Philosphy

Imperfect processes cause most of the software defects. Thus to prevent defects, the development process needs to be overhauled.

 

Software testing Metrices-Test Case Review

Metrics are the means by which the software quality can be measured; they give you confidence in the product.

 

Energize your test team

You're waist deep in your third month of late nights, weekends, and shipping stress; you can see and feel your team's energy waning.

 

The Value of Positive Testing

There is a school of thought in software testing that debunks the value of positive testing. This school basically states that any test that does not produce a defect is not a good test.

Blog Archive