Sunday, June 26, 2011

Understanding Checkpoints

A checkpoint is a verification point that compares a current value for a specified property.

When you add a checkpoint, QuickTest adds a checkpoint to the current row in the Keyword View and adds a Check Checkpoint statement in the Expert View.
When you run the test or component, Quickest compares the expected results of the checkpoint to the current results.
If the results do not match, the checkpoint fails.
You can view the results of the checkpoint in the Test Results window with the expected value for that property.
If you want to retrieve the return value of a checkpoint (a Boolean value that indicates whether the checkpoint passed or failed), you must add parentheses around the checkpoint argument in the statement in the Expert View. For example: a = browser("MyBrowser").page("MyPage").check (checkPoint("MyProperty"))

Check Points
1.Standard Check point
Check values of the object's property
2.Image Check point
Checks the property values of the image
3.Table Check point
Checks information in the table
4.Page Check point
Check the characteristics of the web page
5.Text/Text Area Check point
Checks that a text string is displayed in the appropriate place or application window

Adding Check points to Test
You can add checkpoints during a recording session or while editing your test or component. It is generally more convenient to define checks once the initial test or component has been recorded.

Quickest adds a checkpoint to the current row in the Keyword View and adds a Check Checkpoint statement in the Expert View.

To add checkpoints while recording or editing:

Use the commands on the Insert menu, or click the arrow beside the Insert Checkpoint button on the Testing toolbar. This displays a menu of checkpoint options that are relevant to the selected step in the Keyword View
To add a checkpoint while editing only:
Right-click the step in the Keyword View where you want to add the checkpoint and choose
Insert Standard Checkpoint

Right-click any object in the Active Screen and choose Insert Standard Checkpoint. This option can be used to create checkpoints for any object in the Active Screen (even if the object is not part of any step in the Keyword View).

Understanding the checkpoint property dialog box
Different type of checkpoints in detail:

Standard Checkpoint
Standard checkpoints are supported for all add-in environments.
The standard checkpoint checks a variety of objects such as buttons, radio buttons, combo boxes, lists, etc.
Example : you can check that a radio button is activated after it is selected or you can check the value of an edit field.
Page Checkpoint
checks the characteristics of a Web page. For example, you can check how long a Web page takes to load or whether a Web page contains broken links. You create a page checkpoint by inserting a standard checkpoint on a page object.
Note :- Page checkpoints are supported for the Web environment only
Image Checkpoint

checks the value of an image in your application or Web page. For example, you can check that a selected image’s source file is correct.
Note: You create an image checkpoint by inserting a standard checkpoint on an image object.
Text Checkpoint
Checks that a text string is displayed in the appropriate place in your application or on a Web page.
Example  suppose your application or Web page displays the sentence Flight departing from New York to San Francisco. You can create a text checkpoint that checks that the words “New York” are displayed between “Flight departing from” and “to San Francisco”.

Text Area Checkpoint

Checks that a text string is displayed within a defined area in a Windows application, according to specified criteria.
Suppose your Visual Basic application has a button that says View Doc , where is replaced by the four digit code entered in a form elsewhere in the application.
You can create a text area checkpoint to confirm that the number displayed on the button is the same as the number entered in the form
Accessibility Checkpoint
identifies areas of your Web site that may not
conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines.

 Bitmap Checkpoint
Checks an area of your Web page or application as a bitmap.
Suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly.
Table Checkpoint
checks information within a table. For example, suppose
our application or Web site contains a table listing all available flights from New York to San Francisco. You can add a table checkpoint to check that the time of the first flight in the table is correct.
Note: You create a table checkpoint by inserting a standard checkpoint on a table object.

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.
XML Checkpoint
Checks the data content of XML documents in XML files or XML documents in Web pages and frames

Sunday, June 12, 2011

Regular Expressions

Regular expressions enable QuickTest to identify objects


and text strings with varying values.

You can use regular expressions when:

• defining the property values of an object

• parameterize a step

• creating checkpoints with varying values

A regular expression is a string that specifies a complex search phrase.

Common Options used in the regular expression
Using the Backslash Character ( \ )

Matching Any Single Character ( . )
Matching Any Single Character in a List ( [xy] )
Matching Any Single Character Not in a List ( [^xy] )
Matching Any Single Character within a Range ( [x-y] )
Matching Zero or More Specific Characters ( * )
Matching One or More Specific Characters ( + )
Matching Zero or One Specific Character ( ? )
Matching One of Several Regular Expressions ( |)
Matching the Beginning of a Line ( ^ )
Matching the End of a Line ( $ )
Matching Any AlphaNumeric Character Including the
Underscore ( \w )
Matching Any Non-AlphaNumeric Character ( \W )
Combining Regular Expression Operators



Error Recovery

Recover Scenario:
Unexpected events, errors, and application crashes during a run session can disrupt your run session and distort results.
This is a problem particularly when running tests or components unattended—the test or component is suspended until you perform the operation needed to recover.
A recovery scenario consists of the following:
1.Trigger Event
2. Recovery Operation(s)
3. Post Recovery Test Run option
Deciding When to use Recovery Scenarios
• If we can predict that a certain event may happen at a specific point in your test or component.
• For e.g., say overwrite file message.
Defining Recovery Scenario
• The Recovery Scenario Manager dialog box enables to create recovery scenarios and save them in recovery files.
We can create recovery scenarios using the Recovery Scenario Wizard, which leads through the process of defining each of the stages of the recovery scenario.
• We then save the recovery scenarios in a recovery file, and associate them with specific tests or components.

Understanding the Recovery Scenario Wizard

Defining the trigger event that interrupts the run session
• Specifying the recovery operation(s) required to continue
• Choosing a post-recovery test run operation
• Specifying a name and description for the recovery scenario
• Specifying whether to associate the recovery scenario to the current test and/or to all new tests

Understanding the recovery scenario wizard
  Welcome screen


Trigger Event Screen


Trigger Event Screen - Pop-Up Window Trigger Event




Trigger Event Screen - Object State Trigger Event


Trigger Event Screen - Object State Trigger Event


Trigger Event Screen - Test Run Error Trigger event
 
Any Error


Item in the list or menu is not unique                                      

Item in the list or menu is not found
More that one object responds to the physical description

Object is disabled
Object not found
Object not visible




Trigger Event Screen - Application Crash Trigger Event

Recovery Operations Screen

Keyboard or mouse operations

Close Application process
Function Call
Restart Ms windows


Click button or press key Close processes screen

Recovery Operations Screen - Function Call Screen

Post Recovery Test Run Options Screen


Repeat current step and continue


Proceed to nest step

Proceed to next action iteration

Proceed to next test Iteration

Restart current test run

Stop the test run

Name and Description Screen                   Finish Screen
Managing Recovery Scenarios


Managing Recovery Scenarios
Recovery Scenario Manager enables us to manage existing scenarios by:

Viewing Recovery Scenario Properties
Modifying Recovery Scenarios
Deleting Recovery Scenarios
Copying Recovery Scenarios between
Recovery Scenario files

Setting Recovery Scenarios List for the Tests
Adding Recovery Scenarios to the tests

Viewing Recovery Scenario Properties
Setting Recovery Scenario Priorities
Enabling and Disabling Recovery Scenarios
Setting Default Recovery Scenario Settings for All New Tests


Programmatically Controlling the Recovery Mechanism

We can use the Recovery object to control the recovery mechanism programmatically during the run session. For example:
 

Enable or disable the entire recovery mechanism or specific recovery scenarios for certain parts of a run session.
Retrieve status information about specific recovery scenarios
Explicitly activate the recovery mechanism at a certain point in the run session
By default, QuickTest checks for recovery triggers when an error is returned during the run session.
We can use the Recovery object’s Activate method to force QuickTest to check for triggers after a specific step in the run session

Programmatically Controlling the Recovery Mechanism
Recovery Object


Represents the Recovery tab of the Test Settings or Business Component Settings dialog box, which enables you to configure which recovery scenarios to associate with a test or business component.
Methods
Add Adds the specified recovery scenario to the specified position.
Find The position of the specified recovery scenario.
MoveToPos Changes the order of the recovery scenarios by moving a recovery scenario from its current position to a specified position.
Remove Removes the recovery scenario that is located in the specified position.
RemoveAll Removes all recovery scenarios from the Recovery collection.
SetActivationMode Sets the activation mode for all the recovery scenarios associated with the test or component.
SetAsDefault Sets the current list of recovery scenarios as the default recovery scenarios for all new tests or business components.
Add

object.Add ScenarioFile, ScenarioName, [Position]
Find
object.Find (ScenarioFile, ScenarioName)
MoveToPos
object.MoveToPos CurPosition, NewPosition
Remove
object.Remove Position
Remove All
object.RemoveAll
SetActivationMode
object.SetActivationMode Mode
SetAsDefault
object.SetAsDefault



Monday, June 6, 2011

Descriptive programming

Introduction:


Using Descriptive Programming automation scripts can be created even if the application has not been developed.

Descriptive Programming:

Whenever QTP records any action on any object of an application, it adds some description on how to recognize that object to a repository of objects called object repository. QTP cannot take action on an object until unless its object description is in the Object Repository. But descriptive programming provides a way to perform action on objects which are not in Object repository

Object Identification:

To identify an object during the play back of the scripts QTP stores some properties which helps QTP to uniquely identify the object on a page. Below screen shots shows an example Object repository:






Now to recognize a radio button on a page QTP had added 2 properties the name of the radio button and the html tag for it. The name the left tree view is the logical name given by QTP for the object. This can be changed as per the convenience of the person writing the test case. QTP only allows UNIQUE logical name under same level of hierarchy. As we see in the snapshot the two objects in Browser->Page node are “WebTable” and “testPath”, they cannot have the same logical name. But an object under some other node can have the same name. Now with the current repository that we have, we can only write operation on objects which are in the repository. Some of the example operations are given below


Browser("Browser").Page("Page").WebRadioGroup ("testPath").Select "2"

a = Browser("Browser").Page("Page").WebTable ("WebTable").GetCellData (1,1)

Browser("Example2").Page("Page").WebEdit("testPath").Set "Test text"

When and Why to use Descriptive programming?

Below are some of the situations when Descriptive Programming can be considered useful:

1. The objects in the application are dynamic in nature and need special handling to identify the object. The best example would be of clicking a link which changes according to the user of the application, Ex. “Logout <>”.

2. When object repository is getting huge due to the no. of objects being added. If the size of Object repository increases too much then it decreases the performance of QTP while recognizing a object.

3. When you don’t want to use object repository at all. Well the first question would be why not Object repository? Consider the following scenario which would help understand why not Object repository

Scenario 1: Suppose we have a web application that has not been developed yet. Now QTP for recording the script and adding the objects to repository needs the application to be up, that would mean waiting for the application to be deployed before we can start of with making QTP scripts. But if we know the descriptions of the objects that will be created then we can still start off with the script writing for testing


Scenario 2: Suppose an application has 3 navigation buttons on each and every page. Let the buttons be “Cancel”, “Back” and “Next”. Now recording action on these buttons would add 3 objects per page in the repository. For a 10 page flow this would mean 30 objects which could have been represented just by using 3 objects. So instead of adding these 30 objects to the repository we can just write 3 descriptions for the object and use it on any page.


4. Modification to a test case is needed but the Object repository for the same is Read only or in shared mode i.e. changes may affect other scripts as well.

5. When you want to take action on similar type of object i.e. suppose we have 20 textboxes on the page and there names are in the form txt_1, txt_2, txt_3 and so on. Now adding all 20 the Object repository would not be a good programming approach.

How to use Descriptive programming?

There are two ways in which descriptive programming can be used

1. By creating properties collection object for the description.

2. By giving the description in form of the string arguments.

1. By creating properties collection object for the description.

To use this method you need first to create an empty description

Dim obj_Desc ‘Not necessary to declare

Set obj_Desc = Description.Create

Now we have a blank description in “obj_Desc”. Each description has 3 properties “Name”, “Value” and “Regular Expression”.

obj_Desc(“html tag”).value= “INPUT”

When you use a property name for the first time the property is added to the collection and when you use it again the property is modified. By default each property that is defined is a regular expression. Suppose if we have the following description

obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt.*”

This would mean an object with html tag as INPUT and name starting with txt. Now actually that “.*” was considered as regular expression. So, if you want the property “name” not to be recognized as a regular expression then you need to set the “regularexpression” property as FALSE

obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt.*”

obj_Desc(“name”).regularexpression= “txt.*”

This is how of we create a description. Now below is the way we can use it

Browser(“Browser”).Page(“Page”).WebEdit(obj_Desc).set “Test”

When we say .WebEdit(obj_Desc) we define one more property for our description that was not earlier defined that is it’s a text box (because QTPs WebEdit boxes map to text boxes in a web page).

If we know that we have more than 1 element with same description on the page then we must define “index” property for the that description

Consider the HTML code given below





Now the html code has two objects with same description. So distinguish between these 2 objects we will use the “index” property. Here is the description for both the object

For 1st textbox:

obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt_Name”

obj_Desc(“index”).value= “0”


For 2nd textbox:

obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt_Name”

obj_Desc(“index”).value= “1”

Consider the HTML Code given below:






We can use the same description for both the objects and still distinguish between both of them

obj_Desc(“html tag”).value= “INPUT”

obj_Desc(“name”).value= “txt_Name”


When I want to refer to the textbox then I will use the inside a WebEdit object and to refer to the radio button I will use the description object with the WebRadioGroup object.

Browser(“Browser”).Page(“Page”).WebEdit(obj_Desc).set “Test” ‘Refers to the text box

Browser(“Browser”).Page(“Page”).WebRadioGroup(obj_Desc).set “Test” ‘Refers to the radio button

But if we use WebElement object for the description then we must define the “index” property because for a webelement the current description would return two objects.

Hierarchy of test description:

When using programmatic descriptions from a specific point within a test object hierarchy, you must continue to use programmatic descriptions

from that point onward within the same statement. If you specify a test object by its object repository name after other objects in the hierarchy have

been described using programmatic descriptions, QuickTest cannot identify the object.

For example, you can use Browser(Desc1).Page(Desc1).Link(desc3), since it uses programmatic descriptions throughout the entire test object hierarchy.

You can also use Browser("Index").Page(Desc1).Link(desc3), since it uses programmatic descriptions from a certain point in the description (starting

from the Page object description).

However, you cannot use Browser(Desc1).Page(Desc1).Link("Example1"), since it uses programmatic descriptions for the Browser and Page objects but

then attempts to use an object repository name for the Link test object (QuickTest tries to locate the Link object based on its name, but cannot

locate it in the repository because the parent objects were specified using programmatic descriptions).

Getting Child Object:

We can use description object to get all the objects on the page that matches that specific description. Suppose we have to check all the checkboxes present on a web page. So we will first create an object description for a checkboxe and then get all the checkboxes from the page

Dim obj_ChkDesc

Set obj_ChkDesc=Description.Create

obj_ChkDesc(“html tag”).value = “INPUT”

obj_ChkDesc(“type”).value = “checkbox”

Dim allCheckboxes, singleCheckBox

Set allCheckboxes = Browse(“Browser”).Page(“Page”).ChildObjects(obj_ChkDesc)

For each singleCheckBox in allCheckboxes

singleCheckBox.Set “ON”

Next

The above code will check all the check boxes present on the page. To get all the child objects we need to specify an object description i.e. we can’t use the string arguments that will be discussed later in the 2nd way of using the programming description.

Possible Operation on Description Object

Consider the below code for all the solutions

Dim obj_ChkDesc



Set obj_ChkDesc=Description.Create

obj_ChkDesc(“html tag”).value = “INPUT”

obj_ChkDesc(“type”).value = “checkbox”

Q: How to get the no. of description defined in a collection

A: obj_ChkDesc.Count ‘Will return 2 in our case

Q: How to remove a description from the collection

A: obj_ChkDesc.remove “html tag” ‘would delete the html tag property from the collection

Q: How do I check if property exists or not in the collection?

A: The answer is that it’s not possible. Because whenever we try to access a property which is not defined its automatically added to the collection. The only way to determine is to check its value that is use a if statement “if obj_ChkDesc(“html tag”).value = empty then”.

Q: How to browse through all the properties of a properties collection?

A: Two ways

1st:

For each desc in obj_ChkDesc

Name=desc.Name

Value=desc.Value

RE = desc.regularexpression

Next

2nd:

For i=0 to obj_ChkDesc.count - 1

Name= obj_ChkDesc(i).Name

Value= obj_ChkDesc(i).Value

RE = obj_ChkDesc(i).regularexpression

Next

2. By giving the description in form of the string arguments.

You can describe an object directly in a statement by specifying property:=value pairs describing the object instead of specifying an object’s

name. The general syntax is:

TestObject("PropertyName1:=PropertyValue1", "..." , "PropertyNameX:=PropertyValueX")

TestObject—the test object class could be WebEdit, WebRadioGroup etc….

PropertyName:=PropertyValue—the test object property and its value. Each property:=value pair should be separated by commas and quotation

marks. Note that you can enter a variable name as the property value if you want to find an object based on property values you retrieve during a run session.

Consider the HTML Code given below:





Now to refer to the textbox the statement would be as given below

Browser(“Browser”).Page(“Page”).WebEdit(“Name:=txt_Name”,”html tag:=INPUT”).set “Test”

And to refer to the radio button the statement would be as given below

Browser(“Browser”).Page(“Page”).WebRadioGroup(“Name:=txt_Name”,”html tag:=INPUT”).set “Test”

If we refer to them as a web element then we will have to distinguish between the 2 using the index property

Browser(“Browser”).Page(“Page”).WebElement(“Name:=txt_Name”,”html tag:=INPUT”,”Index:=0”).set “Test” ‘ Refers to the textbox

Browser(“Browser”).Page(“Page”).WebElement(“Name:=txt_Name”,”html tag:=INPUT”,”Index:=1”).set “Test” ‘ Refers to the radio button


Friday, June 3, 2011

Using Library Files

QTP Library Files:

Library file is nothing but a VB script file containing code in VB Script format. Library files in QTP are used to declare functions that are needed to be used across actions. There are two ways to load a Library file in to your test:


1.    Specify the Library file in the settings of the script

Create the VB Script file that you need and save to your PC

In QTP go to Test->Settings… Menu as shown in the image below



 

Go to the Resources tab of the Test Settings window and Click on “+” button. A new line in the list box will appear

Click on “…” button to choose the location of the file

If you specify 2 or more library having a function with same name then QTP will execute the one that comes first i.e. by looking at the order you specify the files. There is no need to specify an order for dependent library file Ex- if file2 uses functions defined in file1 then it is not necessary to specify file1 above file2 any order will work fine.

Click on the “Check Syntax” button to verify that the script is a valid one


 

The VB script file has been associated with your test and functions it can be used in all the actions present in the script. If you click on the “Set as Default” button then all the library files specified in your current test would be automatically added to the new tests that you create from now on.

Variables, classes, functions etc… declared in the Library files are accessible to all the Actions present with in the test. Specifying library files using this method makes it impossible to restrict the use of the Library to specific actions.

2. Loading the library file at run-time

Instead of specifying the library file in test settings we can load it at run-time by using the execute file function.

ExecuteFile “C:\Documents and Settings\tarun_lalwani\Desktop\Demo.vbs”
This would load all the variables, classes, structures etc… declared in the Library but they would be accessible on in the action that has called the ExecuteFile function i.e. if Action1 loads a library file using ExecuteFile then everything present in the library file would only be accessible to Action1 and not any other action.

To Load a library file present in Test Director the path can be specified as “[Quality Center] Subject\PathInTD”

Once a Library file is loaded using ExecuteFile it can’t be unloaded. It is unloaded automatically when the action ends.

The below table gives advantages of both the methods
Specifying Library File in Test Setting Loading Library File at Run-Time


For declaring Global Variable, Functions, classes etc…

Add all global variables to a VB Script file and specify it in settings. For restricting functions of the library to specific Actions

For loading libraries depending upon conditions at run-time. Ex-

If Condition1 then

ExecuteFile “C:\File1.vbs”

Else

ExecuteFile “C:\File2.vbs”

End If