Count number of Links on a web page

SystemUtil.Run "C:\Program Files\Internet Explorer\iexplore.exe", "http://newtours.demoaut.com/"
Browser("Welcome: Mercury Tours").Page("Welcome: Mercury Tours").WebEdit("userName").Set "test"
Browser("Welcome: Mercury Tours").Page("Welcome: Mercury Tours").WebEdit("password").SetSecure "4cb4513bfbdc1da7fa533425cf4f"
Dim obj,AllLink
Set obj=description.Create
obj("micclass").value="link"
set AllLink=browser("Welcome: Mercury Tours").Page("Welcome: Mercury Tours").ChildObjects(obj)
msgbox "Total Links : " & AllLink.count
iLinkCount=AllLink.count
msgbox iLinkCount

Script to Count No. of Items in a List Box & Display theie names.

This sample script uses mercury Flight Reservation site & count number of items in list box "From Day" & display their name one by one.

 

• SystemUtil.Run "C:\Program Files\Internet Explorer\iexplore.exe", "http://newtours.demoaut.com/"
• Dim list_count
• Browser("Welcome: Mercury Tours").Page("Welcome: Mercury Tours").WebEdit("userName").Set "test"
• Browser("Welcome: Mercury Tours").Page("Welcome: Mercury Tours").WebEdit("password").SetSecure "4cb4513bfbdc1da7fa533425cf4f"
• Browser("Welcome: Mercury Tours").Page("Welcome: Mercury Tours").Image("Sign-In").Click
• list_count=Browser("Find a Flight: Mercury").Page("Find a Flight: Mercury").WebList("fromDay").getroproperty("items count")
• msgbox list_count
• For i = 1 to list_count
• Item_Name = Browser("Find a Flight: Mercury").Page("Find a Flight: Mercury").WebList("fromDay").getitem(i)
• msgbox Item_Name
• Next

Checkpoints in QTP

Checkpoint is a verification point in you tests which compares existing value of a property of the object with an existing value. With the help of checkpoint you test that if a property of the object is same or changing.

When you add a checkpoint to your test QTP adds a checkpoint to the current row in keyword view and adds a Check Checkpoint statement to expert view. The name of the checkpoint is by default the name of the object on which checkpoint is applicable.

Why we use checkpoint. When you record a test in your application you simply record various objects & store them in repository but have you done any testing yet…No you haven’t….when you check that if the property of an object is not changing during run time you perform actual test. For this simple reason you insert checkpoints in your test. As application changes vey frequently & you want to keep your test unchanged you apply some checkpoints on object/properties which may change. When you run your test you can checks if Checkpoint Pass/Fail for baseline.

Checkpoints can be inserted using Menu>Insert>Checkpoint or you can use Descriptive Programming for inserting checkpoints in you test.

QTP uses following types of Checkpoints

1. Standard Checkpoint:  Standard Checkpoints used to check properties of an object.You can apply standard checkpoint on an object & test if a property change during run time. This checkpoint is applicable on variety of objects i.e. List Box, Button, Link, Combo Box, Edit Box etc. With help of this checkpoint you can test if a CheckBox is checked, a radio button is enabled or you can check value of an edit box.
2. Image Checkpoint: This check for the values of an image i.e. source of the image.Image checkpoint is supported in web environment only. You can create an Image Checkpoint by applying Standard Checkpoint on Image.
3. Bitmap Checkpoint: Test area of an image as a bit map. This checkpoint is used to check if the image is right. You can use this checkpoint anywhere in you application for Button, Text Box etc.This checkpoint is supported in all add-in environment.
4. Table Checkpoint: This checkpoint checks if data within a table is correct. You can create Table Checkpoint by adding standard checkpoint on table object.
5. Text Checkpoint: Text Checkpoint checks that a string is placed at an appropriate place on application. For example in your application text displays as “Neeraj Kumar Bhatnagar”.you can use Text Checkpoint to check that if Kumar displayed between Neeraj & Bhatnagar
6. Text Area Checkpoint: Enables you to check if the text string is appearing within a defined area in your application. Text Area Checkpoint is only applicable to windows environment such as Standard Windiw, ActiveX, and Visual Basic.
7. Page Checkpoint: Checks for the characteristics of a web page, ie. Time Taken to web page, broken link etc.You can create a Page Checkpoint by inserting a standard checkpoint on page object.
8. Database Checkpoint: Database Checkpoint checks the contents of a database accessed by your application. For example, you can use a database checkpoint to check the contents of a database containing flight information for your Web site.
9. Accessibility Checkpoint: Accessibility Checkpoint identifies areas of your Web site that may not conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines. For example, guideline 1.1 of the W3C Web Content Accessibility Guidelines requires you to provide a text equivalent for every non-text element. You can add an Alt property check to check whether objects that require the Alt property under this guideline, do in fact have this tag.
10. XML Checkpoint : checks the data content of XML documents in XML files or XML documents in Web pages and frames.The XML Checkpoint (Web Page/Frame) option is supported for the Web add-in environment. The XML Checkpoint option is supported for all add-in environments

Ref : QTP Help

Object Repositories in QTP

Object repository is a place where all objects are stored.QTP uses 2 types of object repository

1. Per Action (Local)
2. Shared

Per Action Repository:  By default qtp makes & uses Per Action repository .When qtp learned any object it create a local repository (for new test) within that test or action & stores description of the object in corresponding Action’s local repository automatically.

Objects stored in Per Action Repository will be available to corresponding actions only other actions can not access these objects. If you modify an object in the local object repository, your changes do not have any effect on any other action or any other test

When working with local object repositories:

• QTP creates new object repositories for each action.
• When QTP learns new objects it automatically add description of the objects in local object repository of corresponding action.QTP adds all new objects to local object repository even though one or multiple shared object repositories associated to that action.
•  If a child object are added to local object repository & its parent is in associated shared object repository, its parent automatically moved to local object repository.
•  Every time you create a new action its corresponding local object repository created automatically & as you learn object in you application these object are stored in local repository.
• If QTP stores same object with in two different actions, its stores the object as separate object in both repository.
• When you save your test local object repository save automatically.

Shared Object Repository: Objects are stored in one or multiple shared repository & other actions can also use them. By storing objects in shared object repositories and associating these repositories with your actions, you enable multiple actions to use the objects. For each action, you can use a combination of objects from your local and shared object repositories, according to your needs. You can also transfer local objects to a shared object repository, if required. This reduces maintenance and enhances the reusability of your tests because it enables you to maintain the objects in a single, shared location instead of multiple locations.

For the ease of use & access it’s always advised to use Shared Object repository as you can use same object repository for multiple actions if the actions include same object.

As all objects are stored at one central location at any point of time if object in application change you can update them in all the associated actions that used shared repository.

If the object with same name exists in both PerAction as well as shared repository for an action that action uses Per Action Repository.

When we open a test that was created in an earlier version of qtp a message displays that if you want to convert your test or view it as Read-Only. If the test previously using Per Action Repository the object of each Per Action Repository is transferred to the local object repository of each action.

If Object of previous test was using shared repository the same object repository is associated with each of the actions in the test & local object repository remains empty.

When working with a Shared Object Repository:

• If QTP learns an object which is already existed in either shared or local object repository associated with that action it uses existing information & does not add that object to repository.
•  If a child object are added to local object repository & its parent is in associated shared object repository, its parent automatically moved to local object repository.
• When QTP learns a new object it adds to this object to corresponding action’s local object repository. You can export object from local object repository to shared object repository or you can export the entire local object repository & replace it with shared object repository & your local object now will be accessible to other actions as well. You can also merge objects from the local object repository to a shared object repository that is associated with the same action.

Ref : QTP Help

Smart Identification Explained

When qtp fails to identify any object uniquely with help of learned description of the object it uses smart identification.Normally qtp uses its learned description for identifying an object & this learned description is sufficient to identify any object uniquely as it does not frequently but anyhow if any point of time qtp unable to identify object using its description or it finds more than one object, then it use smart identification techniques.

The Smart Identification Technique uses two properties :

• Base Filter Properties. The most fundamental properties of a particular test object class; those whose values cannot be changed without changing the essence of the original object. For example, if a Web link’s tag was changed from <A> to any other value, you could no longer call it the same object.

• Optional Filter Properties. Other properties that can help identify objects of a particular class. These properties are unlikely to change on a regular basis,but can be ignored if they are no longer applicable.

Smart Identification Process : 

QTP initiate smart identification Process when it is not able to identify any object during run session or more than one object with same description.Th following process is followed to identify object.

1. As soon as smart identification initiate qtp forget all learned description based on mandatory & assistive properties & ordinal identifiers & create a new object candidate list containing the object which matches all of the defined base filter properties.
2. QuickTest filters out any object in the object candidate list that does not match the first property listed in the Optional Filter Properties list. The remaining objects become the new object candidate list.
3. QuickTest evaluates the new object candidate list:
   • If the new object candidate list still has more than one object, QuickTest uses the new (smaller) object candidate list to repeat step2 for the next optional filter property in the list.
   •  If the new object candidate list is empty, QuickTest ignores this optional filter property, returns to the previous object candidate list, and repeats step2 for the next optional filter property in the list.
   •  If the new object candidate list is empty, QuickTest ignores this optional filter property, returns to the previous object candidate list, and repeats step2 for the next optional filter property in the list.
4. If the new object candidate list is empty, QuickTest ignores this optional filter property, returns to the previous object candidate list, and repeats step2 for the next optional filter property in the list.If the object candidate list contains exactly one object, then QuickTest concludes that it has identified the object and performs the statement containing the object QuickTest continues the process described in steps2 and3 until it either identifies one object, or runs out of optional filter properties to use.
   If, after completing the Smart Identification elimination process, QuickTest still cannot identify the object, then QuickTest uses the learned description plus the ordinal identifier to identify the object.If the combined learned description and ordinal identifier are not sufficient to identify the object, then QuickTest stops the run session and displays a Run Error message.

Reference : QTP help.

Object Identification Properties

In my last post i told you how qtp identify any object. Now we will discuss what all properties of an object qtp uses to uniquely identify it.

QTP uses following properties to uniquely identify any object 

1.    Mandatory Property 

2.    Assistive Property 

3.    Ordinal Identifier 

4.    Smart Identification

Before recording, these properties has to be defined for each object by a test engineer in QTP>Tools>Object Identification.

Let’s discuss these in detail.

1.    Mandatory Property :

As per qtp help “Quick Test has a list of mandatory properties that it always learns”. Whenever we record any object as Test Object QTP learns its specified mandatory properties which helps to uniquely identify any object. If QTP feel that these are more objects with same description it learns Assistive Properties.

2.    Assistive Properties :

As per qtp help are “Assistive Properties are properties that QuickTest learns only if the mandatory properties that QuickTest learns for a particular object in your application are not sufficient to create a unique description. If several assistive properties are defined for an object class, then Quick Test learns one assistive property at a time, and stops as soon as it creates a unique description for the object. If QuickTest does learn assistive properties, those properties are added to the test object description.”

3.    Ordinal Identifier :

As per qtp Help - The ordinal identifier assigns the object a numerical value that indicates its order relative to other objects with an otherwise identical description (objects that have the same values for all properties specified in the mandatory and assistive property lists). This ordered value enables QuickTest to create a unique description when the mandatory and assistive properties are not sufficient to do so.

The assigned ordinal property value is a relative value and is accurate only in relation to the other objects displayed when QuickTest learns an object. Therefore, changes in the layout or composition of your application page or screen can cause this value to change, even though the object itself has not changed in any way. For this reason, QuickTest learns a value for this backup ordinal identifier only when it cannot create a unique description using all available mandatory and assistive properties.

In addition, even if QuickTest learns an ordinal identifier, it will use the

identifier during the run session only if the learned description and the Smart Identification mechanism are not sufficient to identify the object in your application.

If QuickTest can use other identification properties to identify the object during a run session, the ordinal identifier is ignored.

QuickTest can use the following types of ordinal identifiers to identify an

object:

• Index. Indicates the order in which the object appears in the application code relative to other objects with an otherwise identical description.
• Location. Indicates the order in which the object appears within the parent window, frame, or dialog box relative to other objects with an otherwise identical description.
• Creation Time. (Browser object only.) Indicates the order in which the browser was opened relative to other open browsers with an otherwise identical description.

When qtp identifies any object first, it learn all of its specified mandatory properties, if object is uniquely identified with these mandatory properties qtp stop learning its properties if qtp feel it is not able to identify object uniquely with help of all mandatory properties, it learns first assistive properties & verify if it is  ok to identify object uniquely, if still it feels that it need some more properties it learns second assistive property & this process continues till QTP identify the object uniquely.

Some time Mandatory & Assistive Properties are not sufficient for description of an object so it uses ordinal identifier to identify.

As last attempt to learn description the object if above all Properties fail to identify object uniquely it uses Smart Identification.

We will discuss Smart Identification later in detail.

How QTP identifies objects ???

How QTP identifies objects ???

QTP uses human like methods to identify any object. How we identify our friends/relatives????? Have you ever thought what process we follow to identify & remember any object in real world?....OK its rather simple as it seems when we see anything first time our mind remember some unique properties of this object….just like when I first saw Eiffel Tower I remember its design, Place,Colour,Height etc.So next time when I will see this my brain will use that information as repository of properties & check if any property of that building matches with same object…if both of the properties matches I will recognize this building as Eiffel Tower.

Some time you have experienced that you teach a kid A for Apple. How he remember Apple ? He identifies that apple is red colour fruit so when you show him some other red colour fruit look like apple he gets confused. Now later on when he retires & learns more properties of Apple on showing another fruit with same/different properties he identifies Apple successfully.

Now process of identifying objects might me clear in your mind same way QTP behaves like human when QTP records any object its captures its properties with its logical name & Physical description.i.e. Name, URL, html id etc & stores them in its object repository (Local/Shared), this object is save as Test Object. These properties are not dependent on location in AUT so even though in successive builds if your objects change location in AUT your test will not fail. When we run our test qtp checks for same objects which it stores in its repository in AUT & identify them using its properties stored in repository.

QTP uses following properties of Test Object to identify.

1. Mandatory Property
2. Assistive Property
3. Ordinal Identifier
4. Smart Identification

We will discuss these properties in detail in my next post….