QTP Discussion

An overview on Test Automation

2011-12-24T09:45:00.001-08:00

An overview on Test Automation

Test Automation

Basically Software Testing is 2 types

1) Manual Testing

2) Test Automation

Manual Testing:

Testing software manually is called Manual Testing. we can test all accepts of software manually.

Below Testing Types can be tested manually

Test Types:
a) Functional Testing
b) Regression Testing
c) GUI Testing
d) Usability Testing
e) Security Testing
f) Compatibility Testing
g) Recovery Testing
h) Reliability testing
Etc…

Drawbacks of Manual Testing

(i)Time consuming.
(ii) More resources required.
(iii)Human Errors
(iv)Repetition of the Task is not much
(v)Tiredness
(vi)Simultaneous auctions are not possible (Parallel)

Test Automation:

Testing Software using any Automation tools is called Test Automation

Advantages of Test Automation:

a) Fast: Tools are faster in execution than human users

b) Reliable: Tools are reliable in complex calculations and tasks

c) Reusable: we can reuse Automated Tests at any number of times

d) Repeatable: we can repeat same operations for required number of times

e) Programmable:we can use flow control statements for appalying logic

f) Comprehensive: we can execute test batches without human interaction also

Test Automation can be used in below areas of Testing:

a) Functional & Regression Testing

b) Load/Stress/Performance Testing

c) Security Testing

d) Unit Testing

Drawbacks of Automation Testing
1)It is expensive
2)We cannot automate all areas.
3)Lack of expertisation.
4)It has some limitations (It cannot test every thing)

Which Software Testing should be automated?

Tests that need to be execute of every build of the application (Sanity Testing)

Tests that use multiple data values (Retesting / Data Drives Testing)

Tests that required data from application intimates (G.U.I. Attributes) Load and Stress Testing

Which Software Testing should not be automated?

Usability Testing One time testing

Quick look Tests or A.S.A.P (As soon as possible) Testing Ad-hoc testing / Random Testing

Customers requirement are frequently changing.

-------------------------------------------
Types of Test tool:
-------------------

Business:
-----------------
a) Vendor tools

Ex: HP- WinRunner, LoadRunner, QTP, QC
IBM-Rational Robot, ,RFT, RPT, QA Director
Borland-SilkTest, Silk Performer etc..

b) Open Source Tools:
Ex: Selenium, Jmeter, QAWebLoad, Bugzilla etc...

c) In-house tools:

Technical:
-----------------
a) Functional & Regression Test Tools:
Ex:WinRunner, QTP, Rational Robot, ,RFT, SilkTest,Selenium etc..

b) Performence/load/stress test tools

Ex: LoadRunner, RPT, Silk Performer,Jmeter, QAWebLoad etc...

c) Test Management Tools:
Ex: QC, QA Director Etc...

d) Defect Management tools

e) Unit Test tools (Ex: JUnit)

Search Engine Submission - AddMe

QTP Basic Features

2011-12-24T09:44:00.001-08:00

QTP Basic Features

• QTP was Launched in 2002 (Nov). By Mercury Interactive. Later taken over by HP, in 2007.

• QTP is an Object Based Testing Tool.

(Object based means; QTP Follows Test Object Model for Performing Testing operations. Based on either Test Objects or Automation Objects or Utility Objects only, we can automate test operations)

(LoadRunner is a Protocol based Test Tool)
• QTP is for Functional and Regression Testing.

(Basically QTP is a Functional and Regression Test tool but we can use it for little bit Compatibility Testing and Performance Testing)
• It follows Keyword Driven Approach.

(Keyword Driven Approach means; Keywords, example: Commands, functions, methods, statements etc.. are used for creating Test scripts)
• It supports Windows Operating Environment only.

(QTP basically depends on User Interface to automate test operations and it is not depends on server side interactions, where as LoadRunner depends on server side Operations, so HP developed LoadRunner for Windows as well as UNIX versions)

• It supports GUI based (Graphical user interface) and Web based Applications Automation, does not support CUI (Command user interface) Applications.

• It has multilingual support. (It supports English, Chinese, Japanese, Korean, etc languages with respect to license.)

• It has adapted Microsoft Visual Basic Scripting edition for programming and Excel like spread sheet for Data driven testing.

Tools support for QTP:
------------------------------
• VB Script for Scripting (for implementing programming logic)

• VB Script engine integrated in QTP, so apart from scripting features we can use File system, Excel, word, Adodb etc. Object models from QTP.

• SQL (Structured query language) engine integrated in QTP, so we can use SQL Statements in QTP to perform Database Operations

• Excel like spread sheet integrated in QTP for performing Data driven Testing

• We can install MS Script Debugger with QTP for Debugging Test scripts.

• QTP uses XML format for Test results, Environment variables and for exporting object repositories.
-------------------------------------------------------

• QTP can be integrated with other Tools like WinRunner and Quality Center.

• QTP can be used for user interface (UI) test case automation and some limited (Non UI) Test case automation like File system operations and Data base operations.

• It was derived from Astra QuickTest (mother tool of QTP).

• It supports IE (Internet Explorer) only for recording tests, for execution it supports other browsers like Mozilla and AOL, opera Etc apart from IE.

• QTP is a Desktop Application (I-Tier/Stand alone).

• QTP developed in .NET Technology.

• Since it is Stand-alone Application, It doesn't have Database, It stores resources as files (Internal and External). We can't share qtp services from one machine to another, but we can share resources(Ex: Object Repository files, Function Libraries, Environment variable files, Recovery scenario files etc...)

QTP has two types of License;

• Seat or Node locked License,

• Concurrent or float license.

• We have to use Seat license from fixed system/machine and Concurrent License, we can use from any system but one user at a time. If we want multiple concurrent licenses that we can purchase.

• QTP has UNI code support.

Version History of QuickTest Professional

• Astra QuickTest (Mother tool of QTP) 1.0 to 5.0

* QTP derived from Astra QuickTest and influenced by WinRunner.

Quick Test Professional

• 5.6 – Nov 2002

• 6.5 – 2003

• 8.0 – 2004

• 8.2, 8.3 –2005

• 9.0,9.1-2006

• 9.2- 2007 Mercury Interactive

• 9.5 –2008 H.P

• 10.00 –2009 January

• 11.00 –2010** (It is Latest Version)

QTP Add ins Info

2011-12-24T09:43:00.001-08:00

QTP Add ins Info

This document provides QuickTest Professional add ins information like Activex, web, visual basic, SAP, Java, .NET, People soft, TE, Web services and Oracle environments.

I) ActiveX Environment

Object Description

----------------------------------------------------

ActiveX An ActiveX control.

----------------------------------------------

AcxButton An ActiveX button.

-------------------------------------------------

AcxCalendar An ActiveX calendar object.

----------------------------------------------------

AcxCheckBox An ActiveX check box.

----------------------------------------------------

AcxComboBox An ActiveX combo box object.

--------------------------------------------------------

AcxEdit An ActiveX edit box.

------------------------------------------------------

AcxRadioButton An ActiveX radio button.

-----------------------------------------------

AcxTable An ActiveX table.

------------------------------------------------

AcxUtil An object that enables you to work with objects returned by performing an operation (usually via the Object property) on an ActiveX test object.

********************************************************

II) Delphi Environment

Object Description

-----------------------------------------

DelphiButton A Delphi button.

--------------------------------------------------

DelphiCheckBox A Delphi check box.

----------------------------------------------------

DelphiComboBox A Delphi combo box.

-----------------------------------------------------

DelphiEdit A Delphi edit box.

-----------------------------------------------------

DelphiEditor A Delphi multi-line editor.

-------------------------------------------------------------

DelphiList A Delphi list.

------------------------------------------------------------

DelphiListView A Delphi list-view control.

-------------------------------------------------------------

DelphiNavigator A Delphi navigator control.

--------------------------------------------------------------

DelphiObject A Delphi object.

--------------------------------------------------------------

DelphiRadioButton A Delphi radio button.

---------------------------------------------------------------

DelphiScrollBar A Delphi scroll bar.

------------------------------------------------------

DelphiSpin A Delphi spin box.

-----------------------------------------------------

DelphiStatic A Delphi static control.

-----------------------------------------------------------

DelphiStatusBar A Delphi status bar.

-------------------------------------------------------------

DelphiTable A Delphi table.

------------------------------------------------------------

DelphiTabStrip A Delphi tab strip.

-----------------------------------------------------------

DelphiTreeView A Delphi tree-view control.

------------------------------------------------------------

DelphiWindow A Delphi window or dialog box.

***************************************************

III) Java Environment

Object Description

JavaApplet Java applet.

------------------------------------

JavaButtonA Java button.

-----------------------------------------

JavaCalendar A Java calendar.

-----------------------------------------

JavaCheckBox A Java check box.

-----------------------------------------

JavaDialog A Java dialog box.
--------------------------------------------

JavaEdit A Java edit box.
-------------------------------------------

JavaExpandBar A Java control that contains labeled bar items, which can be expanded or collapsed by the user.

--------------------------------------------------------

JavaInternalFrame An internal frame that can be activated from the Java applet.

----------------------------------------------------------

JavaLink A Java control that displays text with links.

-----------------------------------------------------------------

JavaList A Java list box with single or multiple selection.

--------------------------------------------------------------------

JavaMenu A Java menu item.

-----------------------------------------------------

JavaObject A generic Java object.

---------------------------------------------

JavaRadioButton A Java radio button.

--------------------------------------------

JavaSlider A Java slider.

-------------------------------------------

JavaSpin A Java spin object.

-------------------------------------------

JavaStaticText A Java static text object.

------------------------------------------------------

JavaTab A Java tabstrip control containing tabbed panels.

----------------------------------------------------------------

JavaTable A Java table.

---------------------------------

JavaToolbar A Java toolbar.

-----------------------------------

JavaTree A Java tree.

-----------------------------

JavaWindow A Java window.

---------------------------------------

******************************************

IV) .NET Web Forms Environment

Object Description
--------------------------------------

WbfCalendar A .NET Web Forms calendar control.

----------------------------------------------------------------

WbfGrid A .NET Web Forms DataGrid object.

----------------------------------------------------------------

WbfTabStrip A .NET Web Forms tabstrip control.

--------------------------------------------------------------

WbfToolbar A .NET Web Forms toolbar control.

-------------------------------------------------------------

WbfTreeView A .NET Web Forms tree view object.

-------------------------------------------------------------

WbfUltraGrid A .NET Web Forms UltraGrid object.

**************************************************

V) .NET Windows Forms Environment

Object Description
---------------------------------

SwfButton

A .NET Windows Forms button object.

SwfCalendar

A DateTimePicker or a Month Calendar .NET Windows Forms calendar object.

SwfCheckBox

A .NET Windows Forms check box.

SwfComboBox

A .NET Windows Forms combo box.

SwfEdit

A .NET Windows Forms edit box.

SwfEditor

A .NET Windows Forms multi-line edit box.

SwfLabel

A .NET Windows Forms static text object.

SwfList

A .NET Windows Forms list.

SwfListView

A .NET Windows Forms ListView control.

SwfObject

A standard .NET Windows Forms object.

SwfPropertyGrid

A property grid control based on the .NET Windows Forms library.

SwfRadioButton

A .NET Windows Forms radio button.

SwfScrollBar

A .NET Windows Forms scroll bar.

SwfSpin

A .NET Windows Forms spin object.

SwfStatusBar

A .NET Windows Forms status bar control.

SwfTab

A .NET Windows Forms tab control.

SwfTable

A grid control based on the .NET Windows Forms library.

SwfToolBar

A .NET Windows Forms toolbar.

SwfTreeView

A .NET Windows Forms TreeView control.

SwfWindow

A .NET Windows Forms window.

VI) Windows Presentation Foundation Environment

Object Description

WpfButton

A button control in a Windows Presentation Foundation application.

WpfCheckBox

A check box control in a Windows Presentation Foundation application.

WpfComboBox

A combo box control in a Windows Presentation Foundation application.

WpfEdit

A document, rich text box, or text control in a Windows Presentation Foundation application.

WpfGrid

A grid control in a Windows Presentation Foundation application.

WpfImage

An image control in a Windows Presentation Foundation application.

WpfLink

A hyperlink control in a Windows Presentation Foundation application.

WpfList

A list control in a Windows Presentation Foundation application.

WpfMenu

A menu control in a Windows Presentation Foundation application.

WpfObject

An object control in a Windows Presentation Foundation application.

WpfProgressBar

A progress bar control in a Windows Presentation Foundation application.

WpfRadioButton

A radio button control in a Windows Presentation Foundation application.

WpfScrollBar

A scroll bar control in a Windows Presentation Foundation application.

WpfSlider

A slider control in a Windows Presentation Foundation application.

WpfStatusBar

A status bar control in a Windows Presentation Foundation application.

WpfTabStrip

A tab control in a Windows Presentation Foundation application.

WpfToolbar

A toolbar control in a Windows Presentation Foundation application.

WpfTreeView

A tree control in a Windows Presentation Foundation application.

WpfWindow

A window control in a Windows Presentation Foundation application.

VII) Oracle Environment

Object Description

OracleApplications

An Oracle Applications session window.

OracleButton

An Oracle button.

OracleCalendar

An Oracle calendar.

OracleCheckbox

A check box Oracle field.

OracleFlexWindow

An Oracle flexfield window.

OracleFormWindow

An Oracle Form window.

OracleList

An Oracle poplist (combo box) or list.

OracleListOfValues

An Oracle window containing a list of values for selection.

OracleLogon

An Oracle Applications sign-on window.

OracleNavigator

An Oracle Navigator window.

OracleNotification

An Oracle error or message window.

OracleRadioGroup

An Oracle option (radio button) group.

OracleStatusLine

The status line and message line at the bottom of an Oracle Applications window.

OracleTabbedRegion

An Oracle tabbed region.

OracleTable

An Oracle block of records.

OracleTextField

An Oracle text field.

OracleTree

An Oracle tree.

VIII) PeopleSoft Environment

Object Description

PSFrame

A frame object within a PeopleSoft application.

IX) PowerBuilder Environment

Object Description

PbButton

A PowerBuilder button.

PbCheckBox

A PowerBuilder check box.

PbComboBox

A PowerBuilder combo box.

PbDataWindow

A PowerBuilder DataWindow control.

PbEdit

A PowerBuilder edit box.

PbList

A PowerBuilder list.

PbListView

A PowerBuilder listview control.

PbObject

A standard PowerBuilder object.

PbRadioButton

A PowerBuilder radio button.

PbScrollBar

A PowerBuilder scroll bar.

PbTabStrip

A PowerBuilder tab strip control

PbTreeView

A PowerBuilder tree-view control.

PbWindow

A PowerBuilder window.

X) SAP Web Environment

Object Description

SAPButton

An SAP Gui for HTML application button, including icons, toolbar buttons, regular buttons, buttons with text, and buttons with text and image.

SAPCalendar

A calendar in a Web-based SAP application.

SAPCheckBox

An SAP Gui for HTML application toggle button, including check boxes and toggle images.

SAPDropDownMenu

A menu that is opened by clicking a menu icon within an SAP Gui for HTML application.

SAPEdit

An SAP Gui for HTML application edit box, including single-line edit boxes and multi-line edit boxes (text area).

SAPFrame

An SAP Gui for HTML application frame.

SAPiView

An SAP Enterprise Portal application iView frame.

SAPList

A drop-down or single/multiple selection list in an SAP Gui for HTML application.

SAPMenu

An SAP Gui for HTML application top-level menu.

SAPNavigationBar

A navigation bar in a Web-based SAP application.

SAPOKCode

An OK Code box in an SAP Gui for HTML application.

SAPPortal

An SAP Enterprise Portal desktop.

SAPRadioGroup

An SAP Gui for HTML application radio button group.

SAPStatusBar

An SAP Gui for HTML application status bar.

SAPTable

An SAP Gui for HTML application table or grid.

SAPTabStrip

An SAP Gui for HTML application tab strip object (an object that enables switching between multiple tabs).

SAPTreeView

An SAP Gui for HTML application tree object.

XI) SAP GUI for Windows Environment

Object Description

SAPGuiAPOGrid

An APO grid control in an SAP GUI for Windows application.

SAPGuiButton

A button in an SAP GUI for Windows application.

SAPGuiCalendar

A calendar object in an SAP GUI for Windows application.

SAPGuiCheckBox

A check box in an SAP GUI for Windows application.

SAPGuiComboBox

A combo box in an SAP GUI for Windows application.

SAPGuiEdit

An edit box in an SAP GUI for Windows application.

SAPGuiElement

Any object in an SAP GUI for Windows application.

SAPGuiGrid

A grid control in an SAP GUI for Windows application.

SAPGuiLabel

A static text label in an SAP GUI for Windows application.

SAPGuiMenubar

A menu bar in an SAP GUI for Windows application.

SAPGuiOKCode

An OK Code box in an SAP GUI for Windows application.

SAPGuiRadioButton

A radio button in an SAP GUI for Windows application.

SAPGuiSession

Represents the SAP GUI for Windows session on which an operation is performed.

SAPGuiStatusBar

A status bar in an SAP GUI for Windows application.

SAPGuiTable

A table control in an SAP GUI for Windows application.

SAPGuiTabStrip

A tab strip in an SAP GUI for Windows application.

SAPGuiTextArea

A text area in an SAP GUI for Windows application.

SAPGuiToolbar

A toolbar in an SAP GUI for Windows application.

SAPGuiTree

A column tree, list tree, or simple tree control in an SAP GUI for Windows application.

SAPGuiUtil

A utility object in an SAP GUI for Windows application.

SAPGuiWindow

A window or dialog box containing objects in an SAP GUI for Windows application.

XII) Siebel Environment

Object Description

SblAdvancedEdit

An edit box whose value can be set by a dynamic object that opens after clicking on a button inside the edit box

SblButton

A Siebel button.

SblCheckBox

A check box with an ON and OFF state.

SblEdit

An edit box.

SblPickList

A drop-down pick list.

SblTable

A Siebel table containing a variable number of rows and columns.

SblTabStrip

A number of tabs and four arrows that move its visible range to the left and to the right.

SblTreeView

A tree view of specific screen data.

SiebApplet

An applet in a Siebel test automation environment.

SiebApplication

An application in a Siebel test automation environment.

SiebButton

A button control in a Siebel test automation environment.

SiebCalculator

A calculator control in a Siebel test automation environment.

SiebCalendar

A calendar control in a Siebel test automation environment.

SiebCheckbox

A checkbox in a Siebel test automation environment.

SiebCommunicationsToolbar

The communications toolbar in a Siebel test automation environment.

SiebCurrency

A currency calculator in a Siebel test automation environment.

SiebList

A list object in a Siebel test automation environment.

SiebMenu

A menu or menu item in a Siebel test automation environment.

SiebPageTabs

A page tab in a Siebel test automation environment.

SiebPDQ

A predefined query in a Siebel test automation environment.

SiebPicklist

A pick list in a Siebel test automation environment.

SiebRichText

A rich text control in a Siebel test automation environment.

SiebScreen

A screen object in a Siebel test automation environment.

SiebScreenViews

A screen view in a Siebel test automation environment.

SiebTaskAssistant

The Task Assistant in a Siebel test automation environment.

SiebTaskUIPane

The task UI pane in a Siebel test automation environment.

SiebText

A text box in a Siebel test automation environment.

SiebTextArea

A text area in a Siebel test automation environment.

SiebThreadbar

A threadbar in a Siebel test automation environment.

SiebToolbar

A toolbar in a Siebel test automation environment.

SiebTree

A tree view object in a Siebel test automation environment.

SiebView

A view object in a Siebel test automation environment.

SiebViewApplets

A view applet in a Siebel test automation environment.

XIII) Standard Windows Environment

Object Description

Desktop

An object that enables you to access top-level items on your desktop.

Dialog

A Windows dialog box.

Static

A static text object.

SystemUtil

An object used to control applications and processes during a run session.

WinButton

A Windows button.

WinCalendar

A Windows calendar.

WinCheckBox

A Windows check box.

WinComboBox

A Windows combo box.

Window

A standard window.

WinEdit

A Windows edit box.

WinEditor

A Windows multi-line editor.

WinList

A Windows list.

WinListView

A Windows list-view control.

WinMenu

A Windows menu.

WinObject

A standard (Windows) object.

WinRadioButton

A Windows radio button.

WinScrollBar

A Windows scroll bar.

WinSpin

A Windows spin box.

WinStatusBar

A Windows status bar.

WinTab

A Windows tab strip in a dialog box.

WinToolbar

A Windows toolbar.

WinTreeView

A Windows tree-view control.

XIV) Stingray Environment

Object Description

WinTab

A Windows tab strip in a dialog box.

WinTable

A Stingray grid.

WinToolbar

A Windows toolbar.

WinTreeView

A Stingray tree control.

XV) Terminal Emulators Environment

Object Description

TeField

A terminal emulator field that fully supports HLLAPI.

TeScreen

A terminal emulator screen that fully supports HLLAPI.

TeTextScreen

A terminal emulator screen that uses text-only HLLAPI or does not support HLLAPI.

TeWindow

A terminal emulator window.

XVI) Visual Basic Environment

Object Description

VbButton

A Visual Basic button.

VbCheckBox

A Visual Basic check box.

VbComboBox

A Visual Basic combo box.

VbEdit

A Visual Basic edit box.

VbEditor

A Visual Basic multi-line editor.

VbFrame

A Visual Basic frame.

VbLabel

A static text object.

VbList

A Visual Basic list.

VbListView

A Visual Basic list-view control.

VbRadioButton

A Visual Basic radio button.

VbScrollBar

A Visual Basic scroll bar.

VbToolbar

A Visual Basic toolbar.

VbTreeView

A Visual Basic tree-view control.

VbWindow

A Visual Basic window.

XVII) VisualAge Smalltalk Environment

Object Description

WinButton

A button in the VisualAge Smalltalk application.

WinEdit

An edit box in the VisualAge Smalltalk application.

WinList

A list in the VisualAge Smalltalk application.

WinObject

An object in the VisualAge Smalltalk application.

WinTab

A tab strip in the VisualAge Smalltalk application.

WinTable

A table in the VisualAge Smalltalk application.

WinTreeView

A tree-view control in the VisualAge Smalltalk application.

XVIII) Web Environment

Object Description

Browser

A Web browser (or browser tab).

Frame

An HTML frame.

Image

An image with or without a target URL link.

Link

A hypertext link.

Page

An HTML page.

ViewLink

A Viewlink object.

WebArea

A section of an image (usually a section of a client-side image map).

WebButton

An HTML button.

WebCheckBox

A check box with an ON and OFF state.

WebEdit

An edit box, usually contained inside a form.

WebElement

A general Web object that can represent any Web object.

WebFile

An edit box with a browse button attached, used to select a file from the File dialog box.

WebList

A drop-down box or multiple selection list.

WebRadioGroup

A set of radio buttons belonging to the same group.

WebTable

A table containing a variable number of rows and columns.

WebXML

An XML document contained in a Web page.

XIX) Web Services Environment

Object Description

Attachments An object that supports attachment-related operations

-----------------------------------------------------------------------------------------

Configuration An object that supports configuration-related operations

-----------------------------------------------------------------------------------------

headers

An object that supports header-related test object operations.

Security

An object that supports security-related test object operations.

WebService

A test object representing a Web service.

WSUtil

A utility object used to check WSDL files

QTP Tool Window

2011-12-24T09:42:00.001-08:00

Key Elements of QTP Tool Window

1) Test Pane:

It is programming interface of QTP, used for creating, editing, viewing and deleting test scripts.

Test: It is a set of statements or set of one or more actions. (It is a local concept)

Action: It is a set of Statements. (It is a local concept)

Statement: A minimal executable unit. Statements may have keywords. (Keyword such as function, method, statement etc). It is a global concept.

Test pane has 2 views.

Expert view- Test in VB script format.

Key word view- Test in Icon based GUI format.

Note1: Here in test pane Test is same but views are different, if you perform any modifications in one view those automatically reflects in another view.

Note 2: Technical users use expert view and business user use key word view.

Note 3: User can customize Test pane view options.

Navigation: Tools Menu> view options> we can use font size and colors etc.

2) Active Screen

It has an optional element of QTP, it takes snap shots of every statement that user performed action or operation on AUT.

It can be used for understanding and editing the test easily.

Navigation: View menu>active screen (for launching and closing)

Configuring Active Screen: Tools > Options > Active screen tab > Increase / Decrease capture level, Apply and OK.

Note 1: Generally novice testers use this feature but it occupies lot of memory space on QTP.

3) Data Table

It has an integrated spread sheet (Excel like), used for Data driven testing.

Navigation: View menu>Data table (for launching and closing)

Data driven Testing: Testing the same task(S) or same operation with multiple sets of test data.

It can be used in two ways.

1. Enter test data directly into Data Table and use.

2. Importing data from external files (Flat files, excel sheets, etc) and Data bases (MS access, Sql Server, oracle, etc.)

It has two types of sheets.

1). Global Sheet- for entire Test /used for all actions in the Test.

2). Action Sheets- for specific Action only.

Data table available in 2 ways:

1). Design time data table. (Attached with every test)

2). Run time data table. (Available in result window)

Run time is a carbon copy of design time data table.

QTP has Data table methods for performing operations on data table.

4) Debug Viewer

It is used for locating and rectifying or fixing errors.

It can be used for debugging the tests by step-by-step execution.

We use Step into, Step over and Step out commands for debugging. (debug commands)

Navigation: View menu>debug viewer (for launching and closing)

Through Debug viewer user can watch variables and change values of variables temporarily.

5) Missing Resources

It can be used for showing missing resources that attached to current test such as (Recovery Scenarios, Library files etc).

Navigation: View menu >missing resources (for launching and closing)

6) Information

This pane shows syntax errors automatically during saving the test.

Navigation: view menu> information

7) QTP Commands

QTP Commands are available in 3 ways.

1). Menu options

2). Tool Bar options

3). Short cut keys (for Some important operations only)

QTP Tool Window Menus

File menu: Through file menu user can create, save tests, open existing tests, export tests in zip format.

Edit Menu: It provides editing options and renaming, deleting and splitting actions.

View menu: Through this menu we can launch and close, active screen, Data Table, Debug viewer, information, missing resources etc.

Insert Menu: Through this menu user can inserting check points, out put values, synchronizing points.

In this menu step generator available, using this user can generate recordable and non-recordable scripts.

Through insert menu user can insert VB Script conditional and loop statements and transaction points (Start and End).

Through insert menu user can create new actions, call existing actions and copy existing actions.

Automation Menu: This menu provides Record, Run options and Run setting options

Through this menu we can start normal recording, analog recording and Low level recording.

Through this menu we can stop recoding, running and also we run tests.

Resources Menu: This menu provides object repository and recovery scenarios options.

Through this menu we can create /modify/delete objects information and we can associate repositories.

Through this menu we can create, modify and delete recovery scenarios.

Debug Menu:

This menu provides debug commands for step by step execution.

Through this menu we can insert/remove/break points.

Tools Menu: This menu provides Tools settings option, view options and object identification configuration.

Through this menu we can set tool options as well as test pane view options.

In this menu object spy option available, through this we can get object’s information.(Properties and values)

In this menu Virtual object option available; through this option we can create virtual objects.

Window Menu: This menu provides QTP tool window style settings.

Help Menu: This menu provides QTP help as well as VB Script help.

Through this menu we can contact technical support people and we can send feedback.

Through this menu we can check for updates and download or install directly.

QTP Commands

2011-12-24T09:41:00.001-08:00

QTP Commands

QTP Commands are available in 3 ways.

1.Menu options

2.Tool Bar options

3.Short cut keys (for Some important operations only)

File menu: Through file menu user can create, save tests, open existing tests, export tests in zip format.

Command	Function
New > Test	Creates a new test.
New > Business Component	Creates a new business component.
New > Scripted Component	Creates a new scripted component.
New > Application Area	Creates a new application area.
New > Function Library	Creates a new function library.
Open > Test	Opens an existing test.
Open > Business/Scripted Component	Opens an existing business or scripted component.
Open > Application Area	Opens an existing application area.
Open > Function Library	Opens an existing function library.
Close	Closes the active function library.
Close All Function Libraries	Closes all open function libraries.
Quality Center Connection	Opens the Quality Center Connection dialog box, enabling you to connect to a Quality Center project.
Quality Center Version Control	Provides a sub-menu of options for managing versions of QuickTest assets in Quality Center. The sub-menu is available only when you are connected to version-control enabled Quality Center project.
Save	Saves the active document.
Save As	Opens the relevant Save dialog box so you can save the open document.
Save Test with Resources	Saves a standalone copy of the current test together with its resource files.
Save All	Saves all open documents.
Enable Editing	Makes read-only function libraries editable.
Export Test to Zip File	Creates a zip file of the active document.
Import Test from Zip File	Imports a document from a zip file.
Convert to Scripted Component	Converts a business component to a scripted component.
Print	Prints the active document.
Print Preview	Displays the Keyword View as it will look when printed and enables you to modify the page setup.
Settings	Opens the Settings dialog box, enabling you to define settings for the open document. (Not relevant for function libraries)
Process Guidance Management	Opens the Process Guidance Management dialog box, enabling you to manage the list of processes that are available in QuickTest.
Associate Library '' with ''	Associates the active function library with the open document. (Available only from function libraries)
Recent Files	Lists the recently viewed files.
Exit	Closes the QuickTest session.

Edit Menu: It provides editing options and renaming, deleting and splitting actions.

Command	Function
Undo	Reverses the last command or deletes the last entry you typed.
Redo	Reverses the most recent operation of the Undo command.
Cut	Removes the selection from your document.
Copy	Copies the selection from your document.
Paste	Pastes the selection to your document.
Delete	Deletes the selection from your document.
Copy Documentation to Clipboard	Copies the content of the Documentation column of the Keyword View, enabling you to paste it in an external application.
Action > Split Action	Separates an action into two sibling actions or into parent-child nested actions.
Action > Rename Action	Changes the name of an action.
Action > Delete Action	Enables you to remove the selected call to the action, or delete the action and its calls from the active test.
Action > Action Properties	Enables you to specify options, parameters, and associated object repositories for a stored action.
Action > Action Call Properties	Enables you to specify the number of run iterations according to the number of rows in the Data Table, and to define the values of input parameters and the storage location of output parameters.
Step Properties > Comment Properties	Opens the Comment Properties dialog box for a comment step. Available only when the selected step is a comment.
Step Properties > Object Properties	Opens the Object Properties dialog box for a selected object. Available only when the selected step contains a test object.
Step Properties > Checkpoint Properties	Opens the relevant Checkpoint Properties dialog box for a selected object. Available only when the selected step is a checkpoint step.
Step Properties > Output Value Properties	Opens the relevant Output Value Properties dialog box for a selected object. Available only when the selected step is an output value step.
Step Properties > Report Properties	Displays the Report Properties dialog box for a report step. Available only when the selected step is a Reporter.ReportEvent step.
Find	Searches for a specified string.
Replace	Searches and replaces a specified string.
Go To	Moves the cursor to a particular line in the test.
Bookmarks	Creates bookmarks in your script for easy navigation.
Advanced > Comment Block	Comments out the current row, or selected rows.
Advanced > Uncomment Block	Removes the comment formatting from the current or selected rows.
Advanced > Indent	Indents the step according to the tab spacing defined in the Editor Options dialog box.
Advanced > Outdent	Outdents the step (reduces the indentation) according to the tab spacing defined in the Editor Options dialog box.
Advanced > Go to Function Definition	Navigates to the definition of the selected function.
Advanced > Complete Word	Completes the word when you type the beginning of a VBScript method or object.
Advanced > Argument Info	Displays the syntax of a method.
Advanced > Apply "With" to Script	Generates With statements for the action displayed in the Expert View, and enables IntelliSense within With statements.
Advanced > Remove "With" Statements	Converts any With statements in the action displayed in the Expert View to regular (single-line) VBScript statements.
Optional Step	Inserts an optional step (a step that is not required to successfully complete a run session).

View menu: Through this menu we can launch and close, active screen, Data Table, Debug viewer, information, missing resources etc.

Insert Menu: Through this menu user can inserting check points, out put values, synchronizing points.

In this menu step generator available, using this user can generate recordable and non-recordable scripts.

Through insert menu user can insert VB Script conditional and loop statements and transaction points (Start and End).

Through insert menu user can create new actions, call existing actions and copy existing actions.

Automation Menu:

This menu provides Record, Run options and Run setting options

Through this menu we can start normal recording, analog recording and Low level recording.

Through this menu we can stop recoding, running and also we run tests.

Command	Function
Record	Starts a recording session.
Run	Starts a run session from the beginning or from the line at which the session was paused.
Stop	Stops the recording or run session.
Run Current Action	Runs only the active action.
Run from Step	Starts a run session from the selected step.
Maintenance Run Mode	Starts a run session during which the Maintenance Run Mode wizard opens for steps that failed because an object was not found in the application (if applicable).
Update Run Mode	Starts a run session to update test object descriptions and other options (if applicable).
Analog Recording	Starts recording in Analog Recording mode.
Low Level Recording	Starts recording in Low Level Recording mode.
Record and Run Settings	Opens the Record and Run Settings dialog box, enabling you to define browser preferences for recording and running your test.
Process Guidance List	Lists the processes that are available for the current document type and for the currently loaded QuickTest add-ins, enabling you to open them.
Results	Enables you to view results for a test run session.

Resources Menu:

This menu provides object repository and recovery scenarios options.

Through this menu we can create /modify/delete objects information and we can associate repositories.

Through this menu we can create, modify and delete recovery scenarios.

Command	Function
Object Repository	Opens the Object Repository window, which displays a tree containing all objects in the current test or component.
Object Repository Manager	Opens the Object Repository Manager dialog box, enabling you to open and modify multiple shared object repositories.
Associate Repositories	Opens the Associate Repositories dialog box, enabling you to manage the object repository associations for the test.
Map Repository Parameters	Opens the Map Repository Parameters dialog box, enabling you to map repository parameters, as needed.
Recovery Scenario Manager	Opens the Recovery Scenario Manager dialog box.
Associated Function Libraries	Lists the function libraries associated with the active document, enabling you to open them.

Debug Menu:

This menu provides debug commands for step by step execution.

Through this menu we can insert/remove/break points.

Tools Menu:

This menu provides Tools settings option, view options and object identification configuration.

Through this menu we can set tool options as well as test pane view options.

In this menu object spy option available, through this we can get object’s information.(Properties and values)

In this menu Virtual object option available; through this option we can create virtual objects.

Command	Function
Options	Opens the Options dialog box, enabling you to modify global testing options.
View Options	Opens the Editor Options dialog box, enabling you to customize how tests and function libraries are displayed in the Expert View and Function Library windows.
Check Syntax	Checks the syntax of the active document.
Object Identification	Opens the Object Identification dialog box, enabling you to specify how QuickTest identifies a particular test object.
Object Spy	Opens the Object Spy dialog box, enabling you to view the native properties and operations of any object in an open application, as well as the test object hierarchy, identification properties, and operations of the test object that QuickTest uses to represent that object.
Web Event Recording Configuration	Opens the Web Event Recording Configuration dialog box, enabling you to specify a recording configuration level. (Relevant for tests only)
Data Driver	Opens the Data Driver dialog box, which displays the default Constants list for the action. (Relevant for tests only)
Change Active Screen	Replaces the previously recorded Active Screen with the selected Active Screen. (Relevant for tests only)
Virtual Objects > New Virtual Object	Opens the Virtual Object Wizard, enabling you to teach QuickTest to recognize an area of your application as a standard test object.
Virtual Objects > Virtual Object Manager	Opens the Virtual object Manager, enabling you to manage all of the virtual object collections defined on your computer.
Customize	Opens the Customize dialog box, which enables you to customize toolbars and menus, and create new menus.

Window Menu:

This menu provides QTP tool window style settings.

Help Menu:

This menu provides QTP help as well as VB Script help.

Through this menu we can contact technical support people and we can send feedback.

Through this menu we can check for updates and download or install directly.

QTP Test Process

2011-12-24T09:40:00.001-08:00

7 Stages of QTP Testing Process

1) Planning

o Analyzing the AUT

o Automation Test Plan Generation

o Automation Framework Implementation

o Generating/Selecting Test cases for Automation

o Collecting Test Data

o QTP Tool Settings Configuration

2) Generating Tests

o Recording

o Keyword driven methodology

o Descriptive Programming

3) Enhancing Tests

o Inserting Checkpoints

o Inserting Output values

o Adding Comments

o Synchronization

o Parameterization

o Inserting Flow Control Statements

o Calling User defined functions and/or Reusable Actions

o Generating Steps though Step Generator

o Inserting Transaction Points

o Regular Expressions

4) Debugging Tests

o Debug Commands & Break Points

o Step by step execution

o Watching Variables

o Changing values of variables

5) Running Tests

o Normal Execution

o Batch Execution

o Through AOM Scripting

o Tests Running through framework

o Scheduled Execution

6) Analyzing Results

o QTP Result window

o Defining our own Results

o Exporting Results

o Deleting Results

7) Reporting Defects

o Manual Defect Reporting

o Tool based Defect Reporting

o Working with Quality Center
-----------------------------------------------------------

Types of Statements in QTP Test / Test Script

i) Declarations (Variables and constants)

Dim x, y, z
Const City, Price

ii) Object calls

Ex1: Dialog("Login").WinEdit("Agent Name:").Set "gcreddy"
Ex2: Browser("Google").Page("Google").Link("Gmail").Click

iii) Comments

iv) Flow Control Statements (Conditional & Loop)

Ex:) If Total=Tickets*Price Then
Msgbox "Test Passed"
Else
Msgbox "Test Failed"
End If

v) Function / Action calls

Ex: Call Login("gcreddy","mercury")
vi) Utility Statements
Ex1: SystemUtil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"
**It launche the Application
Ex2:
SystemUtil.Run "C:\Program Files\Internet Explorer\IEXPLORE.EXE","http://www.icicibank.com/"

vii) VB script other statements

Examples:
Option Explicit
Wait (14)

Recording Tests

2011-12-24T09:39:00.000-08:00

Recording and Running

a) Test Recording Process

It is a Process of Recording user operations on AUT (Application Under Test). During Recording QTP Creates steps in Keyword view, and generates them in a script in the Expert view. Simultaneously it adds Objects information into Object Repository.

b) Running /Execution Process

During Running QTP reads statements one by one and gets Object Information from the Object Repository, based on that Information performs operations on AUT.

c) Recording Modes

QTP has 3 Recording Modes to generate Tests / Test Scripts

i) Normal Recording

It records User Mouse and Keyboard operations on AUT with respect to objects, but unable to record continuous mouse operations like Digital Signatures, graphs, paints etc.

During recording QTP generates VbScript statements in Test Pane, Simultaneously it stores objects information into object repository.

Navigation: Automation>Record

Select Record option on automation toolbar

Use short cut key (F3)

Steps for preparing a Test (through Recording):

1.Put AUT in base state

2.Select Record Option

3.It shows Record and Run Settings, Select type of Environment (Windows or Web)

4.Select Record Option

(It shows two Options :

1.Record and Run Test on any open window based applications

2.Record and Run only on)

If we select first option it records on any opened application on Desktop.

If we select Second option, it asks for the path of the AUT, After Providing the path it records only on that particular application.)

5.Click OK

6.Perform actions on AUT

7.Stop recording.

8.Save the Test

ii) Analog Recording:

It records the exact mouse and keyboard operations. We can use this mode for recording continuous mouse operations. It is not useful for recording normal operations why because it does not generate steps for each operation, generates total user actions in a Track File. The Track file is not editable.

Navigation:

1.Keep tool under recording mode

2.Automation >Analog Recording

Use Short cut Key (Shift + ALT+F3)

Steps for preparing a Test (through Analog Recording):

1.Launch AUT (or we can launch AUT through QTP)

2.Select Record option

3.Automation>Analog Recording

4.Analog Recording Settings Dialog box opens

(In this Dialog box two options available.

1.Record relative to the screen

2.Record relative to the following window)

(If we select first option QTP records User operations with respect to Desktop co-ordinates.

If we select Second option, we have to show the window (AUT), after showing the Window it records with respect to that window co-ordinates.)

5.Select any one option in the dialog box and click Start Analog record.

6.It records User actions

7.Stop Recording

iii) Low Level Recording

It records some operations on Non-supported environments apart from Normal operations.

This mode records at the object level and records all run time objects as window or winobject Test objects.

Use Low Level Recording for recording in an environment not recognized by QTP.

Navigation:

1.Keep tool under recording mode

2.Automation >Low Level Recording

Steps for preparing a Test (through Low Level Recording):

1)Launch AUT (or we can launch AUT through QTP)

2)Select Record option

3)Automation> Low Level Recording

4)Perform options on AUT

5)Stop Recording

6)Save the Test

d) Disadvantages of Recording

• It occupies a lot of memory space(due to duplicate objects), So QTP performance will be reduced

• No Centralized Maintenance mechanism , So Modifications are very difficult

• User may not have command on the Recorded script, So locating errors is difficult

• Recorded scripts are QTP internal files, they may corrupt.

e) Advantages of Recording/ Where Applicable

• It is used for Analyzing the AUT in the initial stage to find out weather the QTP tool is Recognizing all of our Application Objects or not

• It is easy to create Tests / Test Scripts

•It is used for frequently changing UI (User Interface)

• It takes less time to create Tests

Object Repository

2011-12-24T09:33:00.001-08:00

Object Repository:

It is a storage place of QTP where objects information can be stored and it also acts as interface between the Test script and the AUT in order to identify the objects during execution.

Object:

Object is something, which has structure and properties.

Software objects:

We call Windows, Web Pages, Buttons, Edit boxes, Check boxes etc.. as software objects.

Types of Object in QTP:

There are four types of object available in QTP.

1. Run time objects

2. Test objects

3. Utility objects

4. Automation objects/User defined objects.

Run time objects: The objects present in the AUT. Ex: Buttons, Links, etc…

Test Objects: References of Run time objects. Ex: WinEdit, WinButton, WebButton, Link, etc…

Note:

Test objects names vary from one environment to another.

Utility objects

They are QTP reserved objects used for Testing and Result reporting.

Ex:

1. SystemUtil for launching/closing the application.

2. Reporter for defining results.

3. Services for inserting transaction points

4. Environment for using environment variables

Automation objects/User defined objects

User can create objects; those can be used for performing specific operations. Ex: Creating objects in filesystemobject class, adodb.connection class, dictionary object class, Excel. Application class etc.

There are two types of repository available in QTP.

1. Local repository (.MTR extension)

2. Shared repository(.TSR extension)

Local Repository:

QTP creates a Local Repository for every Action automatically during Recording. That cannot be shared among tests.

User can add some more objects to Local repository

User can perform rename, delete operations on local repository. As it is QTP internal file user no need to save modifications.

Shared Repository:

User (Test Engineer) creates the Shared Repository by adding objects. That can be shared among number of tests.

Using this method user can perform modifications on objects easily.

Operations on Object Repository

Adding objects

a. Local Repository:

Navigation: open Local Repository (Resource Menu > Object Repository)

objects>Add objects to Local> Show the Object>Click Ok

(No need to save separately, it saves automatically)

B. Shared Repository:

Navigation: Resource menu>object repository manager>object>Add objects>show the window/object>click ok

o Selected object only

o Default object types

o All objects types

o Selected object types

(If we select first option it stores Selected objects only, if we select second option it stores all default objects, if we select third option it stores All objects including static objects, if we select fourth option, we have to select object classes then it stores that class objects, we can select more than one class also.)

Renaming Objects

a. Local Repository:

Resources > object repository >select object and right click >choose rename option >modify the name>release the mouse.>close repository

b. Shared Repository:

Resources >object repository manager>file>open>browse path of the repository file >file>enable editing>select object &Right click>choose rename option>modify the name > release mouse>save the file & close repository manager.

Deleting Objects

a. Local Repository:

Resources > object repository >select object and right click >choose delete option >confirm deletion>. >close repository

b. Shared Repository:

Resources >object repository manager>file>open>browse path of the repository file >file>enable editing>select object &Right click>choose delete option>confirm the deletion >save the file & close repository manager.

Associating Object Repositories to an Action/Test

Resources>Associate repositories>click add icon (+)>browse path of the repository>Associate with an action>click ok

Merging Repositories

Resources > object repository manager>tools>object repository merge tool >browse path of the first repository> browse path of the second repository>click ok>click close>save the merged repository>close the repository manager.

Note: After merging also, source repository files will be available, if we do not want source files we can delete.

Defining New Test Objects

Navigation: Object>Define new test object >Select Environment>Select Class of the object>Enter name of the object>Click Add>click close>Select object >select property name>enter value (like this select one by one properties and enter values)>save

Note: This feature can be used for preparing tests before the AUT is ready.

Spying Objects

For getting objects information, (Test objects names, property & Values) QTP is providing a feature called Object Spy, using this we can get objects information.

Navigation>Tools>object spy>take hand icon & Show the object>get information (Object Spy shows the specific objects all available properties with their values)

Note: As Object spy is an important feature, it can be available in 3 Areas.(1. In tools Menu 2. In local repository 3. In Repository manager)

View Options

Locate in Repository

This feature can be used for identifying objects from application to repository.

Navigation: View>Locate in repository >show the object>click Ok>it locates specified object in the repository.

Highlight in Application

This feature can be used for identifying objects from repository to application.

Navigation: Select object in the repository >view>highlight in application>it highlights specified objects in the application.

Exporting Repository to an XML file

We can export our repository file to an xml file.

Navigation: File >export Test objects to XML Enter the file name and Save with xml extension.

Importing Repository from XML file.

We can import XML file to our repository.

Navigation: File>import from XML >browse path of the XML file >it loads objects.

Note: The purpose of this feature is Editing objects information outside of the QTP

Navigation: Resource menu>object repository (Short cut key Ctrl+R)

Object Identification Configuration

2011-12-24T09:32:00.001-08:00

Object Identification Configuration

Overview:

Generally for every object 20-25 properties information available, qtp recognizes object using 2 0r 3 important properties.

Qtp has default object identification configuration for every environment, if we feel that config is not sufficient for recognizing objects in our application, we can configure some more

Object Identification Types

a) Normal identification

1) Mandatory properties
2) Assistive properties

b) Smart identification

1) base filter properties
2) optional filter properties

c) Ordinal identifier

1) location
2) index
3) creation time(only for web)

QTP learns information in the following in case of normal identification:

First of all the qtp learns all the mandatory properties at a time and thinks whether these properties sufficient to identify the object uniquely. if it feels sufficient then it stops learning otherwise,
It learns first assistive property and once again stops and thinks, like this qtp learns one by one. At the end of assistive properties list also if it feels not satisfied and it finally goes to Ordinal Identifier.

QTP learns information in the following in case of Smart Identification:

Smart identification is an optional feature, if we feel normal identification is not sufficient for any object, and then we configure Smart Identification for that object, in order to avoid Ordinal Identifier.

After normal identification if qtp feels not satisfied then it goes to smart identification. in smart identification 2 types of properties available, first qtp learns all base filter properties at a time and thinks whether these properties are sufficient for identifying the object uniquely. If it feels sufficient, then it stops learning otherwise it goes Optional Filter Properties and learns one by one. Still it feels not satisfied finally it goes to Ordinal Identifier.

Ordinal identifiers:

There are 3 types of ordinal identifiers available

1) Location: is based on object location in the AUT ,location starts from zero.

2) index: it is based on sequence of the programs, index starts from zero

3) Creation time: it is based on loading time of the web objects. qtp generates 0,1,2 like numbers.

Tool Settings Globalization:

As QTP is a I-tier(Stand-alone) application,making Tool settings globally is not possible.

For making tool settings global, QTP is providing a special feature called "Generate Script".

STEPS:

1) Settings available in 3 areas.

a) File->Settings
b) Tools->Options
c) Tools->Object Identification

2) Perform required settings and generate Scripts

3) Share Script files to team members and ask them to execute those scripts.

NOTE: After executing these scripts all team members can get same settings.

QTP Methods

2011-12-24T09:31:00.003-08:00

QTP Methods / Operations

1) Activate Method

It activates dialog boxes/Windows

Syntax: Object hierarchy. Activate

Ex:

Dialog(“Login”).Activate

Window(“Flight Reservation”).Activate

2) Click Method

It clicks on an object (Buttons)

Syntax: Object hierarchy. Click

Ex:

Dialog(“Login”).Winbutton(“ok”).click

3) Close Method

It closes the window,Dialog box, Browser window etc.

Syntax: Object hierarchy. Close

Ex:

Window(“Flight Reservation”).Close

Browser(“Browser”).Close

4) Dblclick

It Double clicks the object.

5) Set Method

It can be used in three ways.

a. For setting the value of an edit box

Syntax: Object Hierarchy. SET “Value”

Ex: Dialog (“Login”).WinEdit(“Agent Name”).Set “asdf”

b. Selecting a Radio Button

Syntax: Object Hierarchy. Set

Ex: Window("Flight Reservation").WinRadioButton("Business").Set

c. Selecting/Deselecting check boxes

Syntax:object Hierarchy.Set “ON/off”

Ex: Window ("Flight Reservation"). Dialog("Open Order").WinCheckBox("Order No.").Set "ON"

6) Select Method:

It is used for selecting an item from a combo box or list box.

Syntax: Object hierarchy.select “item”

Ex:

Window("Flight Reservation").WinComboBox("Fly From:").Select "London"

Window("Flight Reservation").Dialog("Flights Table").WinList("From").Select "12572

7) GetVisibletext: It returns Text from the specified area.

Syntax: Variable =object hierarchy.getvisibletext

Ex:

x=Window("Flight Reservation").WinComboBox("Fly From:").GetVisibleText

msgbox x

8) GetRoproperty:

It returns current object property value. It can be used for getting any object’s, any property value.

Syntax: Variable = object hierarchy.getroproperty (“property name”)

Ex: x=Window("Flight Reservation").WinEdit("Tickets:").GetROProperty ("width")

msgbox x

9) Navigate Method:

It opens a specified URL in the Browser.

Syntax: object hierarchy.navigate “URL”

Ex: Browser("Yahoo!").Navigate http://www.google.co.in/

10) Getitemscount: It returns number of items in a combobox.

Syntax: Variable=object hierarchy.getitemscount

Ex: x=Window("Flight Reservation").WinComboBox("Fly From:").GetItemsCount

msgbox x

11) Getcontent: It returns all items from a combobox.

Syntax: variable=object hierarchy.GetContent

Ex: x=Window("Flight Reservation").WinComboBox("Fly From:").GetContent

msgbox x

12) Exist property: It checks whether the object is available or not.

Syntax: Object hierarchy.exist(time in seconds)

Ex: Window("Flight Reservation").Exist(5)

Data Table Methods

2011-12-24T09:31:00.001-08:00

QTP Data Table Methods

(1) Add Sheet:
We can use this method to “add” one new sheet to the run time data table.
Syntax: DataTable.AddSheet "sheet name"
Ex: DataTable.AddSheet "gcreddy"

(2) Delete Sheet:

We can use this method to “delete” one specified sheet from the Run Time Data table.

Syntax: datatable.DeleteSheet (Sheet_ID)
Ex: datatable.DeleteSheet (3)

(3) GetSheetCount

We can use this method to count number of sheets in the run time data table.

Syntax:
datatable.GetSheetCount
msgbox datatable.GetSheetCount

(4) GetRowCount

We can use this method to count number of rows in the 1st sheet
(longest column) of the Run time data table.

Syntax: datatable.GetRowCount

Ex: msgbox datatable.GetRowCount

(5) GetSheet

We can use this method to return a specified sheet from the Run Time data table.

Syntax: datatable.GetSheet(SheetID)

Ex: msgbox datatable. GetSheet(1).GetRowCount

(6) Value

We can use this method to set or get value of cell in the specified parameter and the current row of the Rum time data table.

To set data

Syntax: datatable.Value(Parameter_Name, Sheet_Name) = Value / variable Or

datatable(Parameter_Name, Sheet_Name) = Value / variable

To get data

Syntax: Variable = datatable.Value(Parameter_Name, Sheet_Name) Or

Variable = datatable(Parameter_Name, Sheet_Name)

Ex:

Option explicit Dim a, b, c

a=datatable.Value (1,1) b=datatable.Value (2,1) c=cint(a)+cint(b) datatable.Value (3,1) = c

Note: Default property of Datatable is value

(7) SetCurrentRow

We can use this method to take a specified row as current row in the Run Time Datatable (By default it is 1st Row of 1st Sheet)

Syntax: datatable.SetCurrentRow(Row_Number)

g="gcreddy"
datatable.SetCurrentRow (3) datatable.Value (1,1) = g

(8) SetNextRow

We can use this method to take the row after the current Row as New Current Row in the Run time data table.

Syntax: datatable.SetNextRow

Ex: g="gcreddy"

datatable.SetCurrentRow (3) datatable.SetNextRow datatable.Value (1,1) = g

(9) SetPrevRow

We can use this method to take the row before the current Row as New Current Row in the Run time data table.

Syntax: datatable.SetPrevRow

Ex: g="gcreddy"

datatable.SetCurrentRow (3) datatable.SetPrevRow datatable.Value (1,1) = s

(10) Import

We can use this method to import Microsoft Excel File to the Runtime Data Table (Including all sheets)

Syntax: datatable.Import “Path of File”

Ex: datatable.Import “F:\Inputdata.xls”

11) ImportSheet

We can use this method to import a specified sheet of Microsoft Excel Sheet to the Runtime Data table.

Syntax: datatable.ImportSheet “Path of File”, “Source Sheet”, “Destination Sheet”

Ex: datatable.ImportSheet “E:\gcreddy.xls”,3,1

(12) Export

We can use this method to export a copy of Run Time Data table to another location (Including all sheets)

Syntax: datatable.Export “Path of File”

Ex: datatable.Export “F:\gcreddy.xls”

13) ExportSheet

We can use this method to export a copy specified sheet of Run Time Data table to the existing or new Excel File.

Syntax: datatable.ExportSheet “Path of File”, “Sheet Name / Source Sheet”

Ex: datatable.ExportSheet “F:\gcreddy.xls”, 2

**********************

Data Driven Testing for Login Operation using Data Table methods

Datatable.AddSheet "Login"
Datatable.ImportSheet "C:\Documents and Settings\gcr\Desktop\gcreddy.xls",1,3
Rows_count=Datatable.GetSheet(3).GetRowCount

For i= 1 to Rows_count
Datatable.SetCurrentRow(i)
SystemUtil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe","","C:\Program Files\HP\QuickTest Professional\samples\flight\app\","open"
Dialog("Login").Activate
Dialog("Login").WinEdit("Agent Name:").Set Datatable("Agent",3)
Dialog("Login").WinEdit("Password:").Set Datatable("Pwd",3)
Dialog("Login").WinButton("OK").Click

If window("Flight Reservation").exist(10) Then
Login="Login Operation Successful"
Datatable("Result",3)=Login
Reporter.ReportEvent micPass,"res","Passed"
else
Reporter.ReportEvent micFail,"res","Failed"
Login="Login Operation Failed"
Datatable("Result",3)=Login

Dialog("Login").Dialog("Flight Reservations").WinButton("OK").Click
Dialog("Login").WinButton("Cancel").Click
End If

If Window("Flight Reservation").Exist(3)Then
Window("Flight Reservation").Close
End if
Next

Descriptive Programming

2011-12-24T09:30:00.001-08:00

Descriptive Programming

Entering / Providing objects information directly into the test script is called Descriptive Programming.

In this method of script creation, we no need to have Object Repositories.

Advantages:

a) Descriptive Programming based Test scripts are faster in execution than Repository based Test scripts.

b) Scripts are portable (we can run these scripts from any machine easily)

c) Maintenance is easy (less amount of resources)

d) We can start Test Execution process even though Application is not ready.

Descriptive programming is basically 2 types.

1. Static Programming

2. Dynamic Programming

Static Programming

In this style of script generation, we provide objects information directly into the script.

Example:

1) Invokeapplication "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"

2) dialog("text:=Login").Activate

3) dialog("text:=Login").Winedit("attached text:=Agent Name:").Set "gcreddy"

4) dialog("text:=Login").Winedit("attached text:=Password:").Set "mercury"

5) dialog("text:=Login").Winbutton("text:=OK","width:=60").Click

Note:

1. Dialog, WinEdit and WinButton – Test Objects

2. text, attached text - Property names

3. Login, Agent Name:, Password:, OK - Property values or Logical Names of the Object

4. Activate, Set, Setsecure, Click - Methods

Note2:

If we feel one property information is not sufficient for recognizing the object uniquely, then we can provide more properties information by separating with commas.

Note 3:

If we want to get objects information (Test objects, properties and values), we can use object spy feature. This feature is available in Tools Menu, in local repository and in repository manager.

Example 2:

SystemUtil.Run "C:\Program Files\Internet Explorer\IEXPLORE.EXE","","C:\Program Files\Internet Explorer","open"
Browser("title:=Google").Page("title:=Google").Sync
Browser("title:=Google").Navigate "http://www.icicibank.com/"

-------------------------------------------------------------------
If we want maintain ‘Objects information’ in centralized location then we can use Constants.

Steps:

Creating Constants:

Const Login="text:=Login", Agent="attached text:=Agent Name:"

Const Pwd ="attached text:=Password:", Ok="text:=OK"

Note: we can declare no of Constants in a line by separating with Camas (,), if we take other line then we have to use Const Statement again.

Creating a Library file

Place Constants in Notepad and save as .vbs file

Associate the Library file to QTP (File->Settings->Resources-> Click add (+) icon-> Browse path of the Library file->Click Apply and click Ok buttons

Otherwise, we can load the library file during run-time

Syntax:

ExecuteFile “Path of the Library file(.vbs)”

After that create the Test Script using Constants

Creating the Test Script using Constants:

Invokeapplication "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"
Dialog(Login).Activate
Dialog(Login).Winedit(Agent).Set "asdf"
Dialog(Login).Winedit(Pwd").Set "mercury"
Dialog(Login).Winbutton(Ok).Click

Advantages:

If we maintain Object Information in the centralized location, then we can handle modifications easily.

Web Examples:

Gmail Login Operation: (www.gmail.com)

----------------------------

SystemUtil.Run "C:\Program Files\Internet Explorer\IEXPLORE.EXE", "www.gmail.com"
Browser("title:=Gmail: Email from Google").Page("title:=Gmail: Email from Google").WebEdit("name:=Email").Set "gcrindia@gmail.com"
Browser("title:=Gmail: Email from Google").Page("title:=Gmail: Email from Google").WebEdit("name:=Passwd").Set "Kurugonda7"
Browser("title:=Gmail: Email from Google").Page("title:=Gmail: Email from Google").WebButton("value:=Sign in").Click

---------------------------
'Code optimization
--------------------
SystemUtil.Run "C:\Program Files\Internet Explorer\IEXPLORE.EXE", "www.gmail.com"
Set myPage=Browser("title:=Gmail: Email from Google").Page("title:=Gmail: Email from Google")
myPage.WebEdit("name:=Email").Set "gcrindia@gmail.com"
myPage.WebEdit("name:=Passwd").Set "abcd1234"
myPage.WebButton("value:=Sign in").Click

Shopping Portal Registration Operation: (http://www.dealsdirect.com.au/)

SystemUtil.Run "C:\Program Files\Internet Explorer\IEXPLORE.EXE", "http://www.dealsdirect.com.au/"
Browser("title:=.*").Page("url:=http://www.dealsdirect.com.au").Link("text:=Register").Click
Browser("title:=.*").Page("title:=DealsDirect.com.au Secure Login Page").WebEdit("name:=cEmail2").Set "bhavani123@gmail.com"
Browser("title:=.*").Page("title:=DealsDirect.com.au Secure Login Page").WebEdit("name:=cEmail3").Set "bhavani123@gmail.com"
Browser("title:=.*").Page("title:=DealsDirect.com.au Secure Login Page").WebEdit("name:=cPass2").Set "abcd123"
Browser("title:=.*").Page("title:=DealsDirect.com.au Secure Login Page").Image("name:=Image","file name:=image-register-and-continue-button.jpg").Click

-------------------------------------------------------------------

Dynamic Programming

Creating Description Objects, Generating Statements using Description Objects is called Dynamic descriptive Programming

-------------------------------------------

Step1: Create Description Object

Syntax:

Set Variable = Description.Create

Example:

Set Login = Description.Create

----------------------------------

Step2: Enter Properties information into Description Object

Syntax:

Description Object("Property name").Value = "Property value"

Example

Login("text").Value = "Login"

Login("width").Value = 320

----------------------------------------------------------------
Step3: Generating Statements using Description Objects

Syntax:

Test Object(Description Object).Method / Operation

Example:

Dialog(Login).Activate
---------------------------------------------------------------------------------

In this style of script generation, first we create description objects, provide properties information and use description objects in the test script.

Creating Properties Collection Objects

Set oLogin=description.Create

Set oAgent=description.Create

Set oPassword=description.Create

Set oOk=description.Create

Entering Properties Information into Objects

oLogin("text").value="Login"

oLogin("width").value=320

oLogin("height").value=204

oAgent("attached text").value="Agent Name:"

oPassword("attached text").value="Password:"

oOk("text").value="OK"

Generating Tests using Properties collection Objects

Invokeapplication "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"

Dialog(oLogin).Activate

Dialog(oLogin).Winedit(oAgent).Set "gcreddy"

Dialog(oLogin).Winedit(oPassword).Set "mercury"

Dialog(oLogin).Winbutton(oOK).Click

Note1: Create Description objects and put into one library file, by associating that library file, we can generate tests.

Note2: Dynamic programming is some difficult in preparation than static programming but maintenance is very easy.

------------------------------------------------------

Examples:

Handling similar/Duplicate Objects using Index Property

SystemUtil.Run "C:\Program Files\Internet Explorer\IEXPLORE.EXE"

Browser("name:=Google").Page("title:=Google").Sync

Browser("name:=Google").Navigate http://www.jjperfumes.com/

Browser("name:=JJ Perfumes-Discount perfume cheap brand name perfumes, fragrance & cologne online").page("title:=JJ Perfumes-Discount perfume cheap brand name perfumes, fragrance & cologne online").Link("innertext:=Register","index:=0").Click

Inserting Checkpoints

2011-12-24T09:29:00.001-08:00

Inserting Checkpoints

Check point is a verification point, it takes expected result from the user and compares with actual results during execution and provides test results.

There are 11 Checkpoints available in QTP:

1. Standard check point

2. Text check point

3. Text area check point

4. Bit map check point

5. Data base check point

6. Accessibility check point

7. XML Check point (from Application)

8. XML Check point (from Resource)

9. Page check point

10. Image checkpoint

11. Table checkpoint

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

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

1. Standard Checkpoint:

It checks object property values. We can use this checkpoint for checking any property value.

Navigation for Inserting standard checkpoint

Keep tool under recording mode > place cursor in desired location > Insert > check point > Standard checkpoint > Show the object > click okay > select property and enter expected results & click Ok and stop Recording.

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: We can insert standard checkpoints in 3 ways.

a. Through expert view,

b. Through keyword view,

c. Through Active screen.

2) Text Checkpoint:

It Checks object’s text property value in different ways.

Navigation:

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.

3) Text Area Checkpoint:

It checks the text area present in the application.

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.

4. Bitmap checkpoint:

It compares bitmaps; we can compare complete bitmaps as well as part of the bitmaps.

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.

5. Database checkpoint:

It checks Content of the back end Database.

Navigation:

Insert > 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.

Note: here we do not need to put tool under Recording mode and we do not need AUT since data is from backend.

6. Accessibility check point:

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

It is a configurable checkpoint, according to our requirements, we can customize.

Configuring accessibility checkpoint:

Tools menu> options >web > advanced > check/uncheck items > click apply > click ok

Invigilation:

Keep tool under recording mode with web environment >insert>checkpoint>accessibility checkpoint>show the webpage>click ok>click ok>stop recording.

Result Criteria:

a) If item is available but not according to W3C rules then fail.

b) If an item is available, according to W3C rules then Pass.

c) If an item is not available then result would be pass

7. XML Check point (from Application)

It checks content of the XML file.

Navigation:

Keep tool under Recording mode in web environment > insert menu > checkpoint (from application)> show the xml pages >click ok > stop Recording.

8. 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.

Note: 1. If XML file is an individual and path available, and then we can go for inserting xml checkpoint from resource.

Note: 2. If XML file is part of web application, separate path is not available then we can choose inserting XML checkpoints from application.

9. Page checkpoint:

It checks number of Links, Images and Loading time in a web page.

It is a hidden checkpoint; we can insert this through standard checkpoint.

Navigation:

Keep tool under Recording mode with web environment > Insert menu > checkpoint > Standard checkpoint >show the web page > click ok > click ok > stop recording.

10. Image checkpoint:

It checks Image property values.

Navigation:

Keep tool under Recording mode with web environment > Insert menu > checkpoint >standard checkpoint > show the image > select image > click ok > click ok >stop recording.

11. Table checkpoint:

It checks content of the web tables.

Navigation: Keep tool under Recording mode under web environment > Insert menu > checkpoint > standard checkpoint >show the web table > click ok >stop recording.

Inserting Output values

2011-12-24T09:28:00.001-08:00

Inserting Output Values

It is a step in which one or more values are captured during test execution.

The values can later be used as input at a different point in the run session or we can use as input for another test.

It is stored in run time data table; it is located in QTP result window and can be retrieved later.

Types of Output Values:

1. Standard output value

2. Text output value

3. Text area output value

4. Database output value

5. XML output value (From Application)

6. XML output value (From Resource)

1) Standard output value:

We can use standard output values to output the properties values of most objects.

Navigation:

Keep tool under Recording mode > Insert menu >output value> standard output value > show the object > click ok > select property > modify the column name (if required) > click ok >click ok >stop recording.

2) Text output value:

We can use Text output values to output text strings displayed in an application. When creating a text output value we can output a part of the objects text and we can also specify text before and after options.

Navigation:

Keep tool under recording mode> Insert menu> output value > text output value > show the text >select one of the option(output text/text before/text after) > click modify if you want to change the column name > click ok > click ok.> check in runtime table after running it.

3) Text Area output value:

We can use text area output values to output text strings displayed within a defined area of the screen.

Navigation:

Keep tool under recording mode > insert menu >output value > text area output value >Mark the text area >click modify the column name if necessary > click ok > again click ok > check in run time table after running it..

4) Database output value:

We can use Database output values to output the value of the contents of database cells.

Navigation:

Insert menu> output value > Database output value> choose specify SQL statements manually >click next >click create >Select Machine Data source > Select Driver (QT_flight32) > click ok > enter SQL statement (select *from orders) > click finish > select data cells > click ok > Run and it will capture and see the results in run time table.

5) XML output value (from application):

we can use XML output values to output the values of XML elements in XML documents.

Navigation: Keep tool under recording mode with web environment > Insert menu > output value > XML output value from application > Show the XML document > select elements > click ok >stop recording.

6) XML output Value (From Resource):

We can use XML output values to output the values of XML elements in XML documents.

Navigation:

Insert menu >output value> XML output value from resource > browse path of the XML file > click ok > select elements >click ok.

Parameterization

2011-12-24T09:27:00.002-08:00

Parameterization

Passing parameters, through this we can pass multiple values.

We use parameterization in Data Driven Testing.

Data Driven Testing: Testing the Same operation with multiple sets of test data.

Types of Parameterization: We can parameterize tests in several ways in QTP

1. Through Loop Statements

2. Dynamic Test Data Submission

3. Through Data Table

4. Fetching Test Data directly from External files (Flat files & Spreadsheets)

5. Fetching Test Data directly from Databases (MSAcess, Oracle etc).

6. Getting Test Data from front end objects.

1. Through Loop Statements: We can use loop statements for passing sequential numbers & Logical Numbers.

Note: We can’t generate Strings.

For orderno=1 to 10 step 1 ' for one increment step keyword is not mandatory

Window("Flight Reservation").Activate

Window("Flight Reservation").WinButton("Button").Click

Window("Flight Reservation").Dialog("Open Order").WinCheckBox("Order No.").Set "ON"

Window("Flight Reservation").Dialog("Open Order").WinEdit("Edit").Set orderno

Window("Flight Reservation").Dialog("Open Order").WinButton("OK").Click

2.Dynamic Test Data Submission: Through Loop Statements we can give strings also but every time user has to enter data.

For x=1 to 3

Agent =inputbox("enter an Agent Name")

Password=inputbox("enter a password")

invokeapplication "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.exe"

Dialog("Login").Activate

Dialog("Login").WinEdit("Agent Name:").Set Agent

Dialog("Login").WinEdit("Agent Name:").Type micTab

Dialog("Login").WinEdit("Password:").SetSecure password

Dialog("Login").WinButton("OK").Click

Window("Flight Reservation").Close

3. Through Data Table: QTP adds one data table (Spreadsheet) for every test, we can use Data Table for Data Driven Testing.

It has 3 types of usage .

a. Entering test data directly into data table and use

b. Importing test data from external Flat files

c. Importing test data from external Spread sheets

d. Importing test data from Data bases.

a. Entering test data directly into data table and use.

Steps:

i) Generate the basic test>open data table(View>Data Table)

ii) Click on column header>enter the name of the field (like this we can create number of columns) > Enter Data>connect the data to test

(variable=datatable(“column name”, Sheet id)

Example: agent=datatable(“agent”,1)

Pass parameters.)

iii) Run the test.

Example:

Agent = Datatable("Agent",1)

pwd=Datatable ("Password",1)

Invokeapplication "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.exe"

Dialog("Login").Activate

Dialog("Login").WinEdit("Agent Name:").Set Agent

Dialog("Login").WinEdit("Agent Name:").Type micTab

Dialog("Login").WinEdit("Password:").SetSecure pwd

Dialog("Login").WinButton("OK").Click

Window("Flight Reservation").Close

b. Importing test data from external files:

Open Data Table (view>Data table)>place mouse pointer on data table and right click>file>import from file>Click ok>Browsw path of the file(it imports data from the flat file)

Connecting Test Data to QTP Test as above and run the test.

c. Importing test data from external Spread sheets:

Open Data Table (view>Data table)>place mouse pointer on data table and right click>file>import from file>Click ok>Browse path of the excel sheet (it imports data from the excel sheet)

Connecting Test Data to QTP Test as above and run the test.

d. Importing test data from Data bases:

Through Data table we can import Test Data from Data bases, but first we have to create /get the DSN(Data source Name)& we have to use SQL Commands.

i). Creating a Test Database: open MS Access (or we can use any other database).

ii) Start programs>MS Office>MS Access>file >new>Select blank Database>enter name of the database>Save with mdb extension.

iii)

Creating Tables: Select Create table in design view>Enter field name(Agent)and Select data type(text) Like this we can create number of fields>save&enter table name.

iv)

Entering Data into Tables: Select table>enter the data.

Creating DSN & importing data

Navigation:
view>data table>Place mouse pointer on Data table>sheet>import>from database(Database query wizard opens)>choose ‘specify SQL statements manually>click next >click create>click new>select driver type>click next >browse path to store> enter DSN Name>Click Save>click next>click finish>select>browse the database& select>click ok>click ok>select DSN>click ok>enter SQL statement (select *from login)>click finish.

Note: DSN Creation is one time activity, by using the DSN we can get data for number of tests.

4. Fetching Test Data directly from Flat files

Dim fso, myfile

Set fso=createobject("scripting.filesystemobject")

Set myfile=fso.opentextfile("d:\trigun.txt",1)

myfile.skipline

While myfile.atendofline <> true

x=myfile.readline

S=split(x,"@")

SystemUtil.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.exe","","C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\","open"

Dialog("Login").Activate

Dialog("Login").WinEdit("Agent Name:").Set s(0)

Dialog("Login").WinEdit("Agent Name:").Type micTab

Dialog("Login").WinEdit("Password:").SetSecure S(1)

Dialog("Login").WinEdit("Password:").Type micReturn

Window("Flight Reservation").Close

Wend

Fetching Test Data directly from Excel Sheets

Fetching Test Data directly from Databases

Option explicit

Dim con,rs

Set con=createobject("adodb.connection")

Set rs=createobject("adodb.recordset")

con.provider=("microsoft.jet.oledb.4.0")

con.open "C:\Documents and Settings\pooja\My Documents\trigun.mdb"

rs.open "select * from login",con

do until rs.eof=true

Dialog("Login").Activate

Dialog("Login").WinEdit("Agent Name:").Set rs.fields ("agent")

Dialog("Login").WinEdit("Agent Name:").Type micTab

Dialog("Login").WinEdit("Password:").SetSecure rs.fields("password")

Dialog("Login").WinEdit("Password:").Type micReturn

Window("Flight Reservation").Close

rs.movenext

loop
--------------------------------------

Using Dictionary Object for Parameterization

Set inputdata=CreateObject("Scripting.Dictionary")

inputdata.Add "Agent","gcreddy"
inputdata.Add "Password","mercury"

SystemUtil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"
Dialog("Login").Activate
Dialog("Login").WinEdit("Agent Name:").Set inputdata("Agent")
Dialog("Login").WinEdit("Password:").Set inputdata("Password")
Dialog("Login").WinButton("OK").Click

Synchronization

2011-12-24T09:27:00.001-08:00

Synchronization

It is a process of matching the speeds of both QTP and AUT in order to get proper execution and results.

Where Synchronization is required:

During test execution QTP gives instructions one by one with same speed, but AUT takes less time for some operations execution and more time for some operations execution, that time we may not get proper execution and results. In order to get proper results in between QTP & AUT synchronization is required.

There are several methods available in QTP for synchronization.

1. Inserting Wait statements.

2. Inserting Synchronization points.

3. Increasing Tool default synchronization time.

4. Sync Method (Only for WEB)

5. Exist Property

Inserting Wait Statements:

We can insert wait statements in our test in order to make QTP to wait until AUT completes current operation.

Syntax: Wait(time in seconds)

Note: If we insert wait statements QTP waits up to maximum time even though operation is completed.

Inserting Synchronization points:

Place cursor in desired location>keep tool under recording mode>Insert menu>Synchronization point >show the object >click ok>select property name & Value(True)>enter time in Milli seconds>click ok>Stop recording.

Note: if we insert Synchronization points, it does not wait up to maximum time, after completion of the current operations, it goes to next step immediately.

Syntax: object hierarchy.waitproperty “property name”,value,time in milli seconds.

Increasing Tool default synchronization time:

Navigation: File>settings>run tab>increase object synchronization time out>apply>ok

Note: If we increase QTP tool default time that can be applied for all statements in the test, but QTP does not wait up to maximum time unnecessarily, After completion of one statement execution it goes to next statement immediately.

Sync Method: (only for WEB)

Waits for the browser to complete current navigation.

Syntax: Object Hirearchy.Sync

Ex: Browser("Yahoo! Toolbar").Page("Yahoo! Toolbar").Sync

Selecting an appropriate Method:

1. Suppose in our test one or more statements only are taking more time for execution then selecting “Inserting synchronization method” is better.

2. Suppose in our test more statements are taking more time for execution then selecting “increasing tool time out” .

3. Above two are local features but wait statement is Vbscript feature, even though some drawbacks are there in using wait statement, it is better to use wait statement in functions.

Advantages of Wait Statement:

1) It is a VBScript statement, we can use this globally

2) It is recommended, whenever we want to observe the Test Execution process

3) No object reference required to insert wait statements

4) It is useful to make QTP capture values and screen shots during test execution

Actions

2011-12-24T09:26:00.000-08:00

Action: Set of Statements for perfoming a Task(s)
We divide our test into actions to streamline the process of testing.

Purpose of Actions:

For understandability

For reusing components

Types of Actions:

1) Non Re usable actions
2) Re usable actions
3) External actions

Operations on Actions:

• Creating Actions

• Splitting Actions

• Renaming Actions

• Deleting Actions

• Calling an Action

• Copying an Action

• Making an Action Reusable/Non Reusable

Creating an Action:
Insert>call to new action>enter name of the action>click ok
Steps:

1. Create required actions(ex login, insert,delte)
2. Prepare Scripts for those actions.

Splitting an action:

Navigation: Place cursor in desired location>Edit menu>action>split action>Enter Action 1 name & action 2 name.

Steps:

1. Generate total test in the default action
2. Split into meaningful actions.

Note: At a time we can split one actions into 2 actions.

Renaming actions:
Select desired action in action drop down box> edit menu>action>rename action>modify the name>click ok.

Deleting Actions:
Select desired action in action drop down box>edit menu>action>delete action>confirm deletion.

Calling an action:
Insert>call to existing action>browse path of the test>select desired action>click ok.

Note: U can’t edit

Copying an action:
Insert>call to copy of action>browse path of the test>select desired action>click ok.

Note: we can edit this action.

Making an action reusable:
Select Non Reusable action >edit >action>action properties>check reusable action check box >click ok.

VB Script String Functions

2011-12-24T09:25:00.001-08:00

String Functions

1) Left Function

Returns a specified number of charectors of a given string from left side

Syntax:

variable=Left(string,Lengh)

Example:

Dim val,x
val="Hyderabad"
x=Left(val,3)
msgbox x ' Output: Hyd

val="9247837478"
x=Left(val,1)
msgbox x ' Output: 9

val="H92yderabad"
x=Left(val,3)
msgbox x ' Output: H92

x=Left(9247837478,5)
msgbox x ' Output: 92478

val=#10-10-10#
x=Left(val,3)
msgbox x ' Output: 10/

2) Right Function

Returns a specified number of charectors of a given string from Right side

Example:

Dim val,x
val="Hyderabad"
x=Right(val,3)
msgbox x ' Output: bad

val="9247837478"
x=Right(val,1)
msgbox x ' Output: 8

val="H92yderabad"
x=Right(val,3)
msgbox x ' Output: bad

x=Right(9247837478,5)
msgbox x ' Output: 37478

val=#10-10-10#
x=Right(val,5)
msgbox x ' Output: /2010

3) Mid function

Returns a specified number of charectors of a given string

Example:

Dim val,x
val="Hyderabad"
x=Mid(Val,5,3)
msgbox x ' Output: rab

val="Hyderabad"
x=Mid(Val,5)
msgbox x ' Output: rabad

val="9247837478"
x=Mid(val,6,5)
msgbox x ' Output: 37478

val="H92yderabad"
x=Mid(val,1)
msgbox x ' Output: H92yderabad

x=Mid(9247837478,5)
msgbox x ' Output: 837478

val=#10-10-10#
x=Mid(val,5)
msgbox x ' Output: 0/2010

4) StrReverse

retuns reverse value of a string

Example:

Dim val,x
val="Hyderabad"
x=StrReverse(val)
msgbox x 'Output dabaredyH

val="001"
x=StrReverse(val)
msgbox x 'Output: 100

val=1002
x=StrReverse(val)
msgbox x 'Output: 2001

val=#10-10-10#
x=StrReverse(val)
msgbox x 'Output: 0102/01/01

x=StrReverse("Hyderabad")
msgbox x 'Output: dabaredyH

x=StrReverse(100)
msgbox x 'Output: 001

5) StrComp Function

It compares two string (Binary and textual)

if

a) Both are equal, returns 0(zero)

b) String 1 greater than string 2, returns 1(one)

b) String 2 greater than string 1, returns -1

Example:

Dim str1,str2,x
str1="India"
str2="India"
x=StrComp(str1,str2,1)
msgbox x 'Output 0

str1="india"
str2="INDIA"
x=StrComp(str1,str2,1)
msgbox x 'Output 0

str1="India"
str2="Indian"
x=StrComp(str1,str2,1)
msgbox x 'Output -1

str1="Indian"
str2="Ndia"
x=StrComp(str1,str2,1)
msgbox x 'Output -1

str1="Indian"
str2="India"
x=StrComp(str1,str2,1)
msgbox x 'Output 1

str1=100
str2=100
x=StrComp(str1,str2,1)
msgbox x 'Output 0

str1=100
str2=101
x=StrComp(str1,str2,1)
msgbox x 'Output -1

6) Lcase function

Coverts Upper case values into Lower case

Dim val,x
val="HYDERABAD"
x=Lcase(val)
msgbox x 'Output hyderabad

val="Hyderabad"
x=Lcase(val)
msgbox x 'Output hyderabad

val="HederabaD"
x=Lcase(val)
msgbox x 'Output hyderabad

val="hyderabad"
x=Lcase(val)
msgbox x 'Output hyderabad

x=Lcase("HYDERABAD")
msgbox x 'Output hyderabad

7) Ucase function

Coverts Lower case values into Upper case

Example:

Dim val,x
val="HYDERABAD"
x=Ucase(val)
msgbox x 'Output HYDERABAD

val="Hyderabad"
x=Ucase(val)
msgbox x 'Output HYDERABAD

val="HederabaD"
x=Ucase(val)
msgbox x 'Output HYDERABAD

val="hyderabad"
x=Ucase(val)
msgbox x 'Output HYDERABAD

x=Ucase("HYDERABAD")
msgbox x 'Output HYDERABAD

8) LBound, UBound Functions

Example:

Dim x(3), y(4,5)

Msgbox Lbound(x) '0

Msgbox UBound(x)'3

'Find size of the Array

Msgbox UBound(x)+1

Msgbox Lbound(y,1) '0

Msgbox Lbound(y,2) '0

Msgbox UBound(y,1) '4

Msgbox UBound(y,2) '5

Environment Variables

2011-12-24T09:24:00.003-08:00

Environment Variables in QTP

These are global variables; if you want to use some variables globally (From number of tests) declaring as global variables is better. If we declare as local variables in number of tests, modifications are difficult.

Types of Environment variables:

1. Built in variables: These are system defined variables, we can access from all tests but these are designed as read only.

2. User defined variables: Variables that we predefine in the active external environment variables file. We can create as many files as we want and we can change values of variables.

Usage of environment variables:

Syntax:

Variable = Environment(“environment variable name”)

Ex:

X=Environment (“ActionName”)

Msgbox x

Example Script:

ProductDir =environment ("ProductDir")

app= "\samples\flight\app\flight4a.exe"

Systemutil.Run ProductDir & app

Dialog("Login").Activate

Dialog("Login").WinEdit("Agent Name:").Set "kajal"

Dialog("Login").WinEdit("Password:").SetSecure "4b3c86f2107ff565cc195ba6c24739091b656407"

Dialog("Login").WinButton("OK").Click

Creating user defined environment variables:

Navigation:

File > settings > Environment > select variable type as user defined > click add icon (+) > enter variable name & Value > click ok (like this we can create number of variables) > click export > browse path & enter file name, save with xml extension > click ok.

Associating environment variable file:

Navigation:

File > settings >Environment > select variable type as user defined > check “load variables and values from the external file” > browse path of the xml file > click apply & ok.

We can load environment file directly

Environment.loadfromfile”path of the xml file”

Usage of user defined Environment variables:

Associate environment file to current test:

Variable = Environment (“Variable Name”)

X=environment (“city”)

Msgbox x

Modifying Environment files:

Select XML file>open with notepad>modify the values>Save.

Regular Expressions

2011-12-24T09:24:00.001-08:00

Regular Expressions in QTP

What is Regular Expression?

It is a way of representing data using symbols. They are often used within matching, searching or replacing algorithms.

Regular Expressions in QTP:

Regular expressions can be used in QTP for identifying objects and text strings with varying values.

Where we use:

o Defining the property values of an object in Descriptive programming for handling dynamic objects

o For parameterizing a step

o creating checkpoints with varying values

Using Regular Expressions in QTP:

We can define a regular expression for a constant value, a Data Table parameter value, an Environment parameter value, or a property value in Descriptive programming.

We can define a regular expression in standard checkpoint to verify the property values of an object; we can set the expected value of an object's property as a regular expression so that an object with a varying value can be verified.

We can define the text string as a regular expression, when creating a text checkpoint to check that a varying text string is displayed on our application,
For XML checkpoints we can set attribute or element values as regular expressions.

Ways of Regular Expressions:

a) Backslash Character:

A backslash (\) can serve two purposes. It can be used in conjunction with a special character to indicate that the next character be treated as a literal character.
Alternatively, if the backslash (\) is used in conjunction with some characters that would otherwise be treated as literal characters, such as the letters n, t, w, or d, the combination indicates a special character.

b) Matching Any Single Character:

A period (.) instructs QTP to search for any single character (except for \n).
Ex:
welcome.
Matches welcomes, welcomed, or welcome followed by a space or any other single character.

c) Matching Any Single Character in a List:

Square brackets instruct QTP to search for any single character within a list of characters.
Ex:
To search for the date 1867, 1868, or 1869, enter:

186[789]

d) Matching Any Single Character Not in a List:

When a caret (^) is the first character inside square brackets, it instructs QTP to match any character in the list except for the ones specified in the string.
Example:
[^ab]
Matches any character except a or b.

e) Matching Any Single Character within a Range:

To match a single character within a range, we can use square brackets ([ ]) with the hyphen (-) character.
Example:
For matching any year in the 2010s, enter:

201[0-9]

f) Matching Zero or More Specific Characters:

An asterisk (*) instructs QTP to match zero or more occurrences of the preceding character.
For example:

ca*r

Matches car, caaaaaar, and cr

g) Matching One or More Specific Characters:

A plus sign (+) instructs QTP to match one or more occurrences of the preceding character.
For example:
ca+r
Matches car and caaaaaar, but not cr.

h) Matching Zero or One Specific Character:

A question mark (?) instructs QTP to match zero or one occurrences of the preceding character.
For example:
ca?r
Matches car and cr, but nothing else.

i) Grouping Regular Expressions:

Parentheses (()) instruct QTP to treat the contained sequence as a unit, just as in mathematics and programming languages. Using groups is especially useful for delimiting the argument(s) to an alternation operator ( | ) or a repetition operator ( * , + , ? , { } ).

j) Matching One of Several Regular Expressions:

A vertical line (|) instructs QTP to match one of a choice of expressions.

k) Matching the Beginning of a Line:

A caret (^) instructs QTP to match the expression only at the start of a line, or after a newline character.

l) Matching the End of a Line:

A dollar sign ($) instructs QTP to match the expression only at the end of a line, or before a newline character.

m) Matching Any AlphaNumeric Character Including the Underscore:

\w instructs QTP to match any alphanumeric character and the underscore (A-Z, a-z, 0-9, _).

n) Matching Any Non-AlphaNumeric Character:

\W instructs QTP to match any character other than alphanumeric characters and underscores.

o) Combining Regular Expression Operators:

We can combine regular expression operators in a single expression to achieve the exact search criteria we need.
For example,
start.*
Matches start, started, starting, starter, and so forth.
we can use a combination of brackets and an asterisk to limit the search to a combination of non-numeric characters.
For example:
[a-zA-Z]*
To match any number between 0 and 1200, we need to match numbers with 1 digit, 2 digits, 3 digits, or 4 digits between 1000-1200.
The regular expression below matches any number between 0 and 1200.
([0-9]?[0-9]?[0-9]|1[01][0-9][0-9]|1200)

RegExp object

VB Script is providing RegExp object for defining Regular expressions, It provides simple support for defining regular expressions.

Regular Expression Object Properties and Methods:

Properties:

a) Global Property

b) IgnoreCase Property

c) Pattern Property

Methods:

a) Execute Method

b) Replace Method

c) Test Method

Regular Expressions Examples:

1) Match File Names in a Directory against Regular Expression

Set objFS = CreateObject("Scripting.FileSystemObject")
Set objShell = CreateObject("WScript.Shell")
strCurrentDirectory = objShell.CurrentDirectory

Set objFolder = objFS.GetFolder(strCurrentDirectory)
Set colFiles = objFolder.Files

Set objRE = New RegExp
objRE.Global = True
objRE.IgnoreCase = False
objRE.Pattern = WScript.Arguments(0)

For Each objFile In colFiles
bMatch = objRE.Test(objFile.Name)
If bMatch Then
WScript.Echo objFile.Name
End If
Next

2) Match Content in a File against a Regular Expression
strFileName = "E:\gcreddy.txt"
Set objFS = CreateObject("Scripting.FileSystemObject")

Set objTS = objFS.OpenTextFile(strFileName)
strFileContents = objTS.ReadAll
WScript.Echo "Searching Within: "
WScript.Echo strFileContents
objTS.Close

Set objRE = New RegExp
objRE.Global = True
objRE.IgnoreCase = False
objRE.Pattern = WScript.Arguments(0)

Set colMatches = objRE.Execute(strFileContents)
WScript.Echo vbNewLine & "Resulting Matches:"
For Each objMatch In colMatches
WScript.Echo "At position " & objMatch.FirstIndex & " matched " & objMatch.Value
Next

Recovery Scenarios

2011-12-24T09:23:00.001-08:00

Recovery Scenario Manager

To recover from unexpected events and errors that are occurred in the test environment during run session, we can use Recovery Scenario Manager. For good recovery, error must be known the occurrence is unknown.

There are (4) Types of events such as:

(i) Application Crash

An open application fails during Test Run.

Navigation:

Resources Menu -> Recovery Scenario Manager-> Click New-> Click Next ->

Select Application Crash as Trigger event->Next ->Select selected executable

application->Next ->Select Recovery Operation [Keyboard, Mouse Operation,

Close Application Process, function Call, Restart, Microsoft Windows] ->Next ->If

you want to check Add another operation else uncheck->Next ->Next ->Enter

Scenario Name ->Next->Select Option ->Finish ->Close ->Save the scenario in

specified location with “.qrs”

(qrs stands for QuickTest Recovery Scenario.)

(ii) Popup Window.

To handle unwanted popups.

Navigation:

Resources Menu ->Recovery Scenario Manager ->New ->Next ->Select “Popup

Window” as Trigger event ->Next ->Click on Hand Icon ->Show unwanted

window with Hand icon ->Next ->Next ->Select function call as Recovery

Operation ->Next [Open Notepad ->Save empty file with .vbs extension] ->Browse

the .vbs fie path ->Next ->Uncheck Add another Recovery Operation ->Next ->

Select Post-Recovery Test Run Option [Repeat current step and continue, Proceed to

Next step, Proceed to Next Action, Proceed to next test iteration, Restart current test

run, Stop the Test Run] ->Next ->Enter Scenario Name ->Next ->Select Option ->

Finish ->Save the scenario with “.qrs” ->Record required Recovery Operation [Click

ok, Click Cancel] take the script into function ->Save the library file ->Click Run

(iii) Test Run Error.

A step in your test does not run successfully then Test Run Error

can be raised.

Navigation :

Resources Menu ->Recovery Scenario Manager ->New ->Next ->Select “Testrunerror

Window” as Trigger event ->Next ->select any error o ->Next ->Next ->Select function call as Recovery

Operation ->Next [Open Notepad ->Save empty file with .vbs extension] ->Browse

the .vbs fie path ->Next ->Uncheck Add another Recovery Operation ->Next ->

Select Post-Recovery Test Run Option [Repeat current step and continue, Proceed to

Next step, Proceed to Next Action, Proceed to next test iteration, Restart current test

run, Stop the Test Run] ��Next ��Enter Scenario Name ��Next ��Select Option ��

Finish ��Save the scenario with “.qrs” ��Record required Recovery Operation [Click

ok, Click Cancel] take the script into function ��Save the library file ��Click Run

(iv) Object State.

The property values of an object in your application match

specified values. You can specify property values for each object in the

hierarchy.

Navigation:

Resources Menu -> Recovery Scenario Manager -> New -> Next -> Select “Object state

Window” as Trigger event -> Next -> Click on Hand Icon -> Show object with hand icon

-> Next -> Next->select object property with value (enabled ,false)->click next -> Select function call as Recovery

Operation -> Next [Open Notepad -> Save empty file with .vbs extension] -> Browse

the .vbs fie path -> Next -> Uncheck Add another Recovery Operation -> Next ->

Select Post-Recovery Test Run Option [Repeat current step and continue, Proceed to

Next step, Proceed to Next Action, Proceed to next test iteration, Restart current test

run, Stop the Test Run] -> Next-> Enter Scenario Name -> Next -> Select Option ->

Finish -> Save the scenario with “.qrs” -> Record required Recovery Operation [Click

ok, Click Cancel] take the script into function -> Save the library file -> Click Run

File System Operations

2011-12-24T09:22:00.003-08:00

File System Operations

File System:

Its an operating system feature, it allows users to create, modify,

view and delete; drives,folders and files

VB Script is providing an object called scripting.filesystemobject

and some methods for performing file systems operations

File System Object Model:

The File System Object (FSO) model provides an object-based tool for working with folders and files. It allows us to use the familiar object.method syntax with a rich set of properties, methods, and events to process folders and files. We can also employ the traditional Visual Basic statements and commands.

The FSO model gives our application the ability to create, alter, move, and delete folders, or to determine if and where particular folders exist. It also enables us to get information about folders, such as their names and the date they were created or last modified.

The FSO model makes processing files much easier as well. When processing files, our primary goal is to store data in an efficient, easy-to-access format. We need to be able to create files, insert and change the data, and output (read) the data. Although we can store data in a database, doing so adds a significant amount of overhead to our application. We may not want to have such overhead, or our data access requirements may not call for the extra functionality associated with a full-featured database. In this case, storing our data in a text file or binary file is the most efficient solution.

The FSO model, contained in the Scripting type library (Scrrun.dll), supports the creation and manipulation of text files through the TextStream object; however, the FSO model does not support binary files. To manipulate binary files, use the FileOpen Function with the Binary keyword.

Examples:

1) Create a folder

Dim fso, strFolder

strFolder="D:\Documents and Settings\gcreddy\Desktop\Dibyalok"

Set fso=createobject("scripting.filesystemobject")

fso.CreateFolder(strFolder)

2) Create a folder

Dim fso, strFolder

strFolder="D:\Documents and Settings\gcreddy\Desktop\Dibyalok"

Set fso=createobject("scripting.filesystemobject")

If fso.FolderExists(strFolder) Then

msgbox "Folder already exists"

else

fso.CreateFolder(strFolder)

End If

3) Data Driven Testing by fetching Test data directly from a Text file.

'*********************************************************
'Test Requirement: Data Driven Testing by Fetching Test data directly from a Text file.

'Author: G C Reddy

'Date of Creation: 13-08-2010

'Pre-requisites:
'vinod.txt (Test Data)

'Test Flow:
'Creating an Automation Object in FileSystem class
'Opening the External Test Data file using the Object
'Read the Data & Split the Data
'Generating the Login Operation
'Pass Parameters
'********************************************************

Dim objFso, myFile, myLine, myField
Set objFso=CreateObject("Scripting.FileSystemObject")
Set myFile=objFso.OpenTextFile("C:\Documents and Settings\gcr.GCRC-9A12FBD3D9\Desktop\vindod.txt",1) '1 for Read, 2-Write & 8-Append
myFile.SkipLine

Do Until myFile.AtEndOfStream
myLine=myFile.ReadLine
myField=Split(myLine,",")
SystemUtil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"
Dialog("text:=Login").Activate
Dialog("text:=Login").WinEdit("attached text:=Agent Name:").Set myField(0)
Dialog("text:=Login").WinEdit("attached text:=Password:").Set myField(1)
wait 2
Dialog("text:=Login").WinButton("text:=OK").Click
Window("text:=Flight Reservation").Close
Loop
myFile.Close
Set objFso=Nothing

Database connections

2011-12-24T09:22:00.001-08:00

Database connections

Database connection is a facility in computer science that allows client software to communicate with database server software, whether on the same machine or not.

SQL Server connection strings

SQL ODBC connection strings

Standard Security:

"Driver={SQLServer};Server=Your_Server_Name;Database=Your_Database_Name;Uid=Your_Username;Pwd=Your_Password;"

Trusted connection:

"Driver={SQLServer};Server=Your_Server_Name;Database=Your_Database_Name;Trusted_Connection=yes;"
SQL OLE DB connection strings

Standard Security:

"Provider=SQLOLEDB;Data Source=Your_Server_Name;Initial Catalog= Your_Database_Name;UserId=Your_Username;Password=Your_Password;"

Trusted connection:
"Provider=SQLOLEDB;Data Source=Your_Server_Name;Initial Catalog=Your_Database_Name;Integrated Security=SSPI;"
SQL OleDbConnection .NET strings
Standard Security:
"Provider=SQLOLEDB;Data Source=Your_Server_Name;Initial Catalog= Your_Database_Name;UserId=Your_Username;Password=Your_Password;"

Trusted connection:
"Provider=SQLOLEDB;Data Source=Your_Server_Name;Initial Catalog=Your_Database_Name;Integrated Security=SSPI;"
SQL SqlConnection .NET strings
Standard Security:
1. "Data Source=Your_Server_Name;Initial Catalog= Your_Database_Name;UserId=Your_Username;Password=Your_Password;" < br>2. "Server=Your_Server_Name;Database=Your_Database_Name;UserID=Your_Username;Password=Your_Password;Trusted_Connection=False"

Trusted connection:
1. "Data Source=Your_Server_Name;Initial Catalog=Your_Database_Name;Integrated Security=SSPI;"
2."Server=Your_Server_Name;Database=Your_Database_Name;Trusted_Connection=True;"

MS Access connection strings

MS Access ODBC connection strings
Standard Security:
"Driver= {MicrosoftAccessDriver(*.mdb)};DBQ=C:\App1\Your_Database_Name.mdb;Uid=Your_Username;Pwd=Your_Password;"

Workgroup:
"Driver={Microsoft Access Driver (*.mdb)}; Dbq=C:\App1\Your_Database_Name.mdb; SystemDB=C:\App1\Your_Database_Name.mdw;"

Exclusive "Driver={Microsoft Access Driver (*.mdb)}; DBQ=C:\App1\Your_Database_Name.mdb; Exclusive=1; Uid=Your_Username; Pwd=Your_Password;"
MS Access OLE DB & OleDbConnection (.NET framework) connection strings
Open connection to Access database:
"Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\App1\Your_Database_Name.mdb; User Id=admin; Password="

Open connection to Access database using Workgroup (System database):
"Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\App1\Your_Database_Name.mdb; Jet OLEDB:System Database=c:\App1\Your_System_Database_Name.mdw"

Open connection to password protected Access database:
"Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\App1\Your_Database_Name.mdb; Jet OLEDB:Database Password=Your_Password"

Open connection to Access database located on a network share:
"Provider=Microsoft.Jet.OLEDB.4.0; Data Source=\\Server_Name\Share_Name\Share_Path\Your_Database_Name.mdb"

Open connection to Access database located on a remote server:
"Provider=MS Remote; Remote Server=http://Your-Remote-Server-IP; Remote Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\App1\Your_Database_Name.mdb"

MySQL connection strings

MySQL ODBC connection strings
Open connection to local MySQL database using MySQL ODBC 3.51 Driver
"Provider=MSDASQL; DRIVER={MySQL ODBC 3.51Driver}; SERVER= localhost; DATABASE=Your_MySQL_Database; UID= Your_Username; PASSWORD=Your_Password; OPTION=3"
MySQL OLE DB & OleDbConnection (.NET framework) connection strings
Open connection to MySQL database:
"Provider=MySQLProv;Data Source=Your_MySQL_Database;User Id=Your_Username; Password=Your_Password;"

Oracle connection strings

Oracle ODBC connection strings
Open connection to Oracle database using ODBC
"Driver= {Microsoft ODBCforOracle};Server=Your_Oracle_Server.world;Uid=Your_Username;Pwd=Your_Password;"
Oracle OLE DB & OleDbConnection (.NET framework) connection strings
Open connection to Oracle database with standard security:
1. "Provider=MSDAORA;Data Source= Your_Oracle_Database;UserId=Your_Username;Password=Your_Password;"
2. "Provider= OraOLEDB.Oracle;Your_Oracle_Database;UserId=Your_Username;Password=Your_Password;"

Open trusted connection to Oracle database
"Provider= OraOLEDB.Oracle;DataSource=Your_Oracle_Database;OSAuthent=1;"

Automation Object Model

2011-12-24T09:21:00.003-08:00

AOM Scripting (Automation Object Model)

Object Model:

An object model is a structural representation of software objects (classes) that comprise the implementation of a system or application. An object model defines a set of classes and interfaces, together with their properties, methods and events, and their relationships.

We can use QTP Automation object Model to write scripts, that automate our QTP operations.

QTP Automation object model provides objects, methods and properties that enable us to control QTP from another application.

We can use Scripting languages or programming languages such as VBscript, Java script or VC++, .Net for automating QTP operations.

Example:

1) Write an AOM Script to launch QTP Tool, Execute Tests and to close the QTP Tool

option explicit

Dim qtApp

Set qtApp=createobject ("Quicktest.Application")

qtApp.Launch

qtApp.visible=True

qtApp.open "C:\Documents and Settings\admin\My Documents\login"

qtApp.Test.Run

qtApp.Test.Close

qtApp.open "C:\Documents and Settings\admin\My Documents\open order"

qtApp.Test.Run

qtApp.Test.Close

qtApp.quit
Set qtApp=Nothing

Note: AOM Script can be used in Automation framework as an Initialization script.
'------------------------------------------------------------------
2) Write an AOM script to execute series of tests

Dim objFso,objQtp,myFile,i,gcreddy

Set objQtp = CreateObject("Quicktest.Application")
objQtp.Visible = True
objQtp.Launch

Set objFso =CreateObject("Scripting.FileSystemObject")
Set myFile = objFso.OpenTextFile("C:\Users\Chinni\Desktop\Test\gcreddy.txt")
i =1
Do Until myFile.AtEndOfStream =True
testurl = myFile.ReadLine

objQtp.Open gcreddy
objQtp.Test.Run
objQtp.Test.Close
i = i+1
Loop

objQtp.Quit
Set objQtp = Nothing
'******************************************

Dynamic Handling of Object Repositories

2011-12-24T09:21:00.001-08:00

Dynamic handling of object Repositories

Loading repositories during running, finding path of the repositories and removing repositories is called Dynamic Handling of Object Repositories.

Using this feature we can increase QTP performance. To do this, QTP is providing an object called “RepositoriesCollection”.

Syntax for Loading a Repository:

RepositoriesCollection.Add “Path of the Repository File”

Syntax for finding Position of the Repository:

Variable=RepositoriesCollection.Find(“Path of the Repository”)

Syntax for Removing the Repository:

RepositoriesCollection.Remove(position)

Syntax for Removing All Repositories:

RepositoriesCollection.RemoveAll

Example:

RepPath="C:\Documents and Settings\Administrator\My Documents\Login.tsr"

RepositoriesCollection.Add (RepPath)

systemutil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe"

Dialog("Login").Activate

Dialog("Login").WinEdit("Agent Name:").Set "sudhakar"

Dialog("Login").WinEdit("Password:").Set "mercury"

Dialog("Login").WinButton("OK").Click

pos=RepositoriesCollection.Find(RepPath)

RepositoriesCollection.Remove(pos)

RepositoriesCollection.RemoveAll
***********************************
Go to home page for QTP Guide, Script examples, Interview questions and Framework etc.

QTP Certification Questions-1

2011-12-24T09:15:00.000-08:00

1) Text (or text area) checkpoints may behave differently in different run sessions depending on the APIs used in your application

A) True

B) False

2) Using the Windows API, you can extend testing abilities and add usability and flexibility to your...... .

A) tests

B) function libraries

C) applications

D) Both A & B

3) API functions are located inside Windows DLLs

A) True

B) False

4) Integrating QuickTest with Quality Center enables you to store and access files in a Quality Center project, as well as use the....... object to access the wide range of functionality provided in the Quality Center Open Test Architecture API.

A) QCUtil

B) QCUtility

C) QCUtill

D) QCUntil

5) QuickTest works directly with the SAP Gui Scripting API to record your operations. Therefore, QuickTest adds steps to your test or component only when ........ are sent to the server.

A) API catches

B) API events

C) API starts

D) API stops

6) QuickTest communicates directly with the SAP Gui Scripting API to record and run your operations on SAP Windows objects.

A) True

B) False

7)........... declares references to external procedures in a dynamic-link library

A) Declare

B) Extern

C) Intern

D) None

8) The QuickTest automation object model supplies a type library file named ........... This file is stored in \bin.

A) QTObjectModel.dll

B) QTObjectModell.dll

C) QTObjecModel.dll

D) Both A & B

9) If you want to call a QuickTest test containing Stingray objects from WinRunner or vice versa, you must first ensure that WinRunner and QuickTest are both using the latest version of the Stingray agent. To do this, search for the .......... file in \bin and in \arch. Then replace the earlier file with the later one.

A) Stagent.dll

B) Stagerent.dll

C) Staent.dll

D) Stagents.dll

10) In the General tab of Options dialog box, Use text recognition mechanisms in this order: (Please select valid options from below)

A) First Windows API then OCR

B) First Windows API then LCR

C) First Windows API then MCR

D) First Windows API then NCR

Answers:

1) A, 2) D, 3) A, 4) A, 5) B, 6) A, 7) A, 8) A, 9)A, 10) A

QTP Certification Questions-2

2011-12-24T09:14:00.000-08:00

1) In the Expert View, you can use the Object property to activate the method for a Web object.

A) True
B) False

2) The test object property set for each test object is created and maintained by....... The run-time object property set for each run-time object is created and maintained by the object creator

A) Microsoft
B) Adobe
C) HP
D) QuickTest

3) You can view or modify the test object property values that are stored with your component in the Object Properties or Object Repository dialog box.

A) True
B) False

4) It is possible that you can use the Object property to access the native properties of any run-time object.

A) True
B) False

5) You cannot retrieve the values of test object properties from a run-time object.

A) True
B) False

6) You can use the GetTOProperty, GetTOProperties, and SetTOProperty methods in your ........ to set and retrieve the test object property values of the test object.

A) Test
B) Function Library
C) Applciation area
D) Both A & B

7) Because QuickTest refers to the temporary version of the test object during the run session, any changes you make using the SetTOProperty method apply only during the course of the run session, and do not affect the values stored in the test object repository.

A) True
B) False

8) You can use the Object Spy at any time to view .....properties and values of the objects in the application you are testing.

A) run-time
B) test object
C) Both A & B
D) None
9) You cannot add to the list of properties that QuickTest uses to identify an object.
A) True
B) False

10) The default properties for a Link object (hypertext link) are...

A) Name
B) text
C) HTML tag
D) Tag

Answers:
1) A, 2) D, 3) A, 4) A, 5) B, 6) D, 7) A, 8) C, 9)B, 10) B,C

QTP Certification Questions-3

2011-12-24T09:13:00.002-08:00

QTP Certification Questions-3

1) If an object with the same name and description is located in both the local object repository and in a shared object repository that is associated with the same action, the action uses the ...... object definition.

A) shared
B) local
C) Can use any
D) None of above.

2) You cannot use the same shared object repository with multiple actions.

A) True
B) False

3) If one or more of the property values of an object in your application differ from the property values QuickTest uses to identify the object, your test ..... fail.

A) may
B) must
C) should
D) will certainly

4) You can open as many shared object repositories as you want.

A) True
B) False

5) You can also open an object repository from the.......... in the File menu.

A) Recent Folders list
B) Current Files list
C) Recent Files list
D) Both A & c

6)QuickTest saves the object repository with a .....extension in the specified location

A) .vsr
B) .tsr
C) .lsr
D) .qsr

7) If you opened the object repository in ...... mode, you must enable editing for the object repository before you can modify it.

A) read-write mode
B) read-execute mode
C) read-write-execute mode
D) read-only mode

8) You can also modify a shared object repository bymerging it with another shared object repository.

A) True
B) False

9) You can also add objects to a shared object repository using the ....... option.

A) Navigate and Learn
B) Navigate and earn
C) Navigate
D) Navigate and Click

10) While Finding Objects in an Object Repository, You can use the Find and Replace dialog box to replace property or object names.

A) True
B) False

Answers

1) B, 2) B, 3) A, 4) A, 5) C, 6) B, 7) D, 8) A, 9) A, 10) B

QTP Certification Questions-4

2011-12-24T09:13:00.001-08:00

1) The ...... enables you to view either the entire test flow (the calls to the actions in the test) or you can view the steps for a selected reusable or external action.

A) Action Menu
B) Action List
C) Action Toolbar
D) Action View

2) You can view the ....... of the original action in the General tab of the Action Properties dialog box.

A) Parameters
B) Location
C) Associated Repositories
D) Type

3) You can create an additional call to any reusable or external action in your test by pressing ...... while you drag and drop the action to another location at a parallel (sibling) level within your test.

A) F3
B) alt
C) shift
D) ctrl

4) You can use action parameters in any step in your action (including function calls).

A) True
B) False

5) Input values for an action parameter can be retrieved

A) from the test (for a top-level action)
B) from the parameters of the parent action that calls
it (for a nested action)
C) from the output of a previous action call (for a
sibling action)
D) All of above

6) The Action Call Properties dialog box enables you to set options that apply only to a ...... action call.

A) following
B) preceeding
C) specific
D) internal

7) Specifying input and output parameter values in action calls is .......

A) required
B) optional
C) required only for internal action
D) both A & B

8) You can share a value that is generated in one action with other actions in your test by storing the value in the ..... Data Table.

A) Internal
B) External
C) Local
D) Global

9) ExitAction:

A) Exits the current action, regardless of its iteration attributes.
B) Exits the current iteration of the action.
C) Exits the test, regardless of its iteration attributes.
D) Exits the current global iteration.

10) If the action called by the RunAction statement includes an ExitAction statement, the RunAction statement can return the value of the ExitAction's RetVal argument.

A) True
B) False

Answers:

1) B, 2) B, 3) D, 4) A, 5) D, 6) C, 7) b, 8) d, 9) A, 10) A