QTP Guide

QTP Step by Step Guide
An overview on Test Automation QTP Basic features Add-in Manager Key elements of QTP Test Pane QTP Commands QTP Test Process Recording Tests Keyword Driven Methodology Test Object Model Object Repository Object Identification Configuration QTP Test Methods

Data Table Methods
Descriptive Programming Enhancing Tests Inserting Checkpoints Inserting Output values

Parameterization Synchronization Inserting Transaction Points Step Generator Adding Comments Inserting Flow Control Statements Debugging Tests Running/Executing Tests Analyzing Test Results & Reporting Reporting Defects Actions Functions Environment Variables Regular Expressions Virtual Object Configuration Batching Testing Recovery Scenarios File System Operations Database connections Automation Object Model

Dynamic Handling of Object Repositories

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:

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. 3)Lack of expertisation.U.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.I. Attributes) Load and Stress Testing Which Software Testing should not be automated? Usability Testing One time testing .

Japanese. statements etc. QTP is an Object Based Testing Tool. etc languages with respect to license. (Keyword Driven Approach means. where as LoadRunner depends on server side Operations.S.) • It has adapted Microsoft Visual Basic Scripting edition for programming and Excel like spread sheet for Data driven testing. (Object based means. QTP Follows Test Object Model for Performing Testing operations. Adodb etc. example: Commands. Object models from QTP. • It has multilingual support. Based on either Test Objects or Automation Objects or Utility Objects only. (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. Tools support for QTP: -----------------------------• VB Script for Scripting (for implementing programming logic) • VB Script engine integrated in QTP. Korean. Excel. (QTP basically depends on User Interface to automate test operations and it is not depends on server side interactions. in 2007. we can automate test operations) (LoadRunner is a Protocol based Test Tool) • QTP is for Functional and Regression Testing. are used for creating Test scripts) • It supports Windows Operating Environment only. does not support CUI (Command user interface) Applications. Keywords. so apart from scripting features we can use File system.A. QTP Basic Features • • QTP Launched in 2002 (Nov).Quick look Tests or A. methods. Chinese. word. functions.. . so HP developed LoadRunner for Windows as well as UNIX versions) • It supports GUI based (Graphical user interface) and Web based Applications Automation. Later taken over by HP. By Mercury Interactive. (It supports English.P (As soon as possible) Testing Ad-hoc testing / Random Testing Customers requirement are frequently changing.

Version History of QuickTest Professional • Astra QuickTest (Mother tool of QTP) 1. 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.• SQL (Structured query language) engine integrated in QTP. • • Seat or Node locked License. QTP developed in . • • QTP is a Desktop Application (I-Tier/Stand alone). If we want multiple concurrent licenses we can purchase. • It was derived from Astra QuickTest (mother tool of QTP).0 Quick Test Professional • 5. • QTP has UNI code support. 8.9.2007 Mercury Interactive . • QTP uses XML format for Test results. we can use for any system but one user at any time. • Seat license for one system and Concurrent License. • It supports IE (Internet Explorer) only for recording tests. • 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.2. QTP has two types of License. ------------------------------------------------------• QTP can be integrated with other Tools like WinRunner and Quality Center.5 – 2003 • 8.0 – 2004 • 8.0. opera Etc apart from IE.2.1-2006 • 9. for execution it supports other browsers like Mozilla and AOL. Environment variables and for exporting object repositories.0 to 5. Concurrent or float license.3 –2005 • 9.6 – Nov 2002 • 6.NET Technology.

• 9....0) .00 –2009 January Overview ---------------------------------------------------------------a) Disadvantages of Manual Testing 1) Huge Amount of Human Resources as well as Environment (Test lab) 2) Time taking process 3) Less Accuracy 4) Tideness b) Advantages of Test Automation 1) 2) 3) 4) 5) 6) Fast Reliable Accurated Reusable Repeatable Comprehensive c) Draback of Test Automation 1) Expensive 2) Technical expertise 3) 100% Automation not Posible d) Types of Test Tool Business cla Technical cla -------------------------------------Vendor Tools Functional & Regression Test tools Opensource Performance/Load/stress Test tools In-House Test Management Tools Defect Management Tools Security Unit Test tools Etc... -----------------------------------------------------------------------I) Basic Features of QTP ------------------------------------------------------------------------a) QTP Supporting Environments 1) UI (GUI/Windows and Web) 2) Only Windows (Clien side and Server side) b) Version History QTP derived from Astra QuickTest(1.5 –2008 H.P • 10.5.0.

2 2005 9.0 2004 8.0 2009 (Jan) c) QTP License(Seat/Node Locked and Concurent/Float) c) QTP IDE 1) QTP Features Ex: Recording. 3) Integrated Tools (Others) Ex: Spread sheet. VB Script Engine.. 2) Integrated Tools (HP) Ex: Password Encoder.5 2008--------HP 10.1 2006 9.5 2003 8. Object Repository etc. Checkpoints.. 9.5.2 2007 9. Test Batch Runner.0. MS Script Debugger d) Key elements of QTP 1) Test Pane 2) Active Screen 3) Data Table 4) Debug Viewer 5) Information Pane 6) Missing Resources 7) QTP Commands --------------------------------------------------------------------------II) QTP Test Process --------------------------------------------------------------------------Manual Test Process (STLC) Vs QTP Test Process ----------------------------------------------------------------I) Planning I) Planning a) Analyzing Requirements a) Analyzing the AUT b) Test Strategy Implentation b) selecting/Creating Test case for Automation c) Test estimations c) Test Estimations & Approvals d) team formation d) Automation framework Implementation e) Risk Analysys e) QTP Tool Settings Configuration f) Configuration management g) Defining Test Environment h) Test Plan Documentation -------------------------------------------------------------------------------II) Test Design IIA) Creating the Basic Tests a) Repository based Test creation 1) Recording (Local Repository) 2) Keyword driven methodology (Shared a) Understanding & Analyzing Reqs b) Generating Test Scenarios c) Test case Documentation .6 2002 (Nov) 6. SQL Engine. Test Result Dletion Tool etc..

Repository) b) Descriptive Programming 1) Static Programming 2) Descriptive Programming IIB) Enhancing Tests a) Adding Comments b) Inserting Checkpoints c) Inserting Output values d) Inserting Transaction points e) Generating steps thru Step Generator f) Inserting Flow Control Statements g) Synchronization h) Parameterization i) Calling Functions / Actions j) Using Regular expressions k) Using Environment Variables l) Using Automation Objects (using Object Models) --------------------------------------------------------------------------------------------------------III) Test Execution ------------------IIIA) Debugging Tests (Optional) a) Forming Test Batches/suites a) Step by step execution b) Test Environment setup b) Watching Variables c) Test Execution c) Locating & Isolating Errors d) Analyzing Test Results d) Defect Reporting e) Defect Tracking III B) Running Tests f) Re & Regression Testing a) Single Test Run g) Test status Reporing b) Batch Testing h) Test Logs c) Executing Tests thru Framework i) Final Regression d) Scheduled execution e) Analyzing Results f) Result Reporing g) Defect Reporing h) Regression Testing ------------------------------------------------------------------------------------------IV) Test Closure IV) Test Closure ----------------a) evaluating Exit Criteria a) Sending Test scripts & Resources to Customer b) Collecting all facts from Test Activities b) Maintaning Tests & Resouce files c) sending Test Delivarables to Customer c) Improvement Suggessions d) Improvement Suggessions for QA Process --------------------------------------------------------------------------------------------III) Creating Tests / Test Scripts -----------------------------------------------------------------------------------------1) Repository based Test Design a) Recording (Local repository) .

b) Keyword Driven methodology (Shared repository) 2) Descriptive Programming a) Static Programming b) Dynamic programming Recording Tests ---------------a) Recording Process b) Recording Modes i) Normal Recording ii) Analog Recording iii) Low Level Recording c) Running Process Object Repository: -----------------a) Object and Types of Object i) Run-time Objects ii) Test Object Model iii) Utility Objects iv) Automation Objects b) Types of Object Repository i) Local Repository ii) Shared Repository c) Operations on Object Repository i) Adding Objects ii) Renaming Objects iii) Deleting Objects iv) Exporting Local Objects v) Merging Repositories vi) Associating Repositories to an Action vii) View Options viii) Exporting Objects to XML/Importing Objects from XML iX) Defining New Test Objects X) Spying Objects d) Object Identification Configuration i) Normal identification 1) Mandatory properties 2) Assistive properties ii) Smart Identification (Optional) .

generating Tests b) Dynamic Programming i) Creating Collection Objects ii) Entering Properties Information into Collection Objects iii) Using Collection Objects. generating tests c) Handling Dynamic Objects using Regular expressions d) Handling Duplicate/Similar Objects using Index property ---------------------------------------------------------------------------------- .1) Base Filter properties 2) Optional Filter properties iii) Ordinal Identifier 1) Location 2) Index 3) Creation Time (Only for web Application) Keyword driven methodoly: ------------------------a) Creating Shared Object Repositories b) Associating Repositories to an Action c) Creating tests manually i) Thru Expert View ii) Keyword View iii) generate steps thru Step Generator Descriptive programming: -----------------------a) Static programming i) identifying Unique Properties for Objects ii) Creating Constants iii)Creating Library file for constants iv) associating Library files / loading Library files during run-time v) Using Constants.

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.

NET Windows Forms status bar control. WpfEdit A document.NET Windows Forms library. WpfList A list control in a Windows Presentation Foundation application. WpfGrid A grid control in a Windows Presentation Foundation application.NET Windows Forms edit box. WpfCheckBox A check box control in a Windows Presentation Foundation application.NET Windows Forms list.NET Windows Forms TreeView control. VI) Windows Presentation Foundation Environment Object Description WpfButton A button control in a Windows Presentation Foundation application. rich text box. SwfSpin A . SwfTable A grid control based on the .NET Windows Forms multi-line edit box.NET Windows Forms toolbar. . or text control in a Windows Presentation Foundation application. SwfTab A . SwfToolBar A .NET Windows Forms ListView control. SwfListView A . SwfWindow A . SwfObject A standard . SwfScrollBar A .NET Windows Forms spin object. WpfImage An image control in a Windows Presentation Foundation application.NET Windows Forms scroll bar. SwfList A . SwfLabel A . SwfPropertyGrid A property grid control based on the . SwfEditor A . SwfStatusBar A . WpfLink A hyperlink control in a Windows Presentation Foundation application.NET Windows Forms static text object. SwfRadioButton A .NET Windows Forms library.NET Windows Forms radio button.SwfEdit A .NET Windows Forms tab control.NET Windows Forms window. WpfComboBox A combo box control in a Windows Presentation Foundation application. SwfTreeView A .NET Windows Forms object.

OracleStatusLine . WpfStatusBar A status bar control in a Windows Presentation Foundation application. OracleList An Oracle poplist (combo box) or list. OracleCalendar An Oracle calendar. OracleNotification An Oracle error or message window. OracleButton An Oracle button. WpfScrollBar A scroll bar control in a Windows Presentation Foundation application. OracleFlexWindow An Oracle flexfield window. WpfToolbar A toolbar control in a Windows Presentation Foundation application. OracleLogon An Oracle Applications sign-on window. WpfProgressBar A progress bar control in a Windows Presentation Foundation application. OracleNavigator An Oracle Navigator window. WpfSlider A slider control in a Windows Presentation Foundation application. WpfWindow A window control in a Windows Presentation Foundation application. OracleListOfValues An Oracle window containing a list of values for selection. OracleRadioGroup An Oracle option (radio button) group. WpfTreeView A tree control in a Windows Presentation Foundation application.WpfMenu A menu control in a Windows Presentation Foundation application. WpfTabStrip A tab control in a Windows Presentation Foundation application. OracleFormWindow An Oracle Form window. VII) Oracle Environment Object Description OracleApplications An Oracle Applications session window. WpfObject An object control in a Windows Presentation Foundation application. OracleCheckbox A check box Oracle field. WpfRadioButton A radio button control in a Windows Presentation Foundation application.

PbScrollBar A PowerBuilder scroll bar. toolbar buttons. PbCheckBox A PowerBuilder check box. PbWindow A PowerBuilder window. buttons with text. OracleTable An Oracle block of records. PbEdit A PowerBuilder edit box. PbRadioButton A PowerBuilder radio button. PbList A PowerBuilder list. PbComboBox A PowerBuilder combo box. regular buttons. OracleTextField An Oracle text field. OracleTabbedRegion An Oracle tabbed region. and buttons with text and image. PbDataWindow A PowerBuilder DataWindow control. PbListView A PowerBuilder listview control. IX) PowerBuilder Environment Object Description PbButton A PowerBuilder button. SAPCalendar . PbObject A standard PowerBuilder object. X) SAP Web Environment Object Description SAPButton An SAP Gui for HTML application button. VIII) PeopleSoft Environment Object Description PSFrame A frame object within a PeopleSoft application.The status line and message line at the bottom of an Oracle Applications window. PbTabStrip A PowerBuilder tab strip control PbTreeView A PowerBuilder tree-view control. including icons. OracleTree An Oracle tree.

SAPGuiGrid A grid control in an SAP GUI for Windows application. SAPGuiEdit An edit box in an SAP GUI for Windows application. SAPRadioGroup An SAP Gui for HTML application radio button group. SAPEdit An SAP Gui for HTML application edit box. XI) SAP GUI for Windows Environment Object Description SAPGuiAPOGrid An APO grid control in an SAP GUI for Windows application. including single-line edit boxes and multi-line edit boxes (text area). . SAPTreeView An SAP Gui for HTML application tree object. SAPFrame An SAP Gui for HTML application frame. SAPStatusBar An SAP Gui for HTML application status bar.A calendar in a Web-based SAP application. SAPGuiCheckBox A check box in an SAP GUI for Windows application. SAPTabStrip An SAP Gui for HTML application tab strip object (an object that enables switching between multiple tabs). 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. SAPDropDownMenu A menu that is opened by clicking a menu icon within an SAP Gui for HTML application. SAPTable An SAP Gui for HTML application table or grid. SAPGuiComboBox A combo box in an SAP GUI for Windows application. SAPPortal An SAP Enterprise Portal desktop. SAPiView An SAP Enterprise Portal application iView frame. SAPOKCode An OK Code box in an SAP Gui for HTML application. SAPGuiElement Any object in an SAP GUI for Windows application. SAPGuiButton A button in an SAP GUI for Windows application. SAPCheckBox An SAP Gui for HTML application toggle button. SAPNavigationBar A navigation bar in a Web-based SAP application. including check boxes and toggle images. SAPGuiCalendar A calendar object in an SAP GUI for Windows application.

SAPGuiRadioButton A radio button in an SAP GUI for Windows application. SblPickList A drop-down pick list.SAPGuiLabel A static text label in an SAP GUI for Windows application. SAPGuiTabStrip A tab strip in an SAP GUI for Windows application. SblTable A Siebel table containing a variable number of rows and columns. SAPGuiMenubar A menu bar in an SAP GUI for Windows application. SblTabStrip A number of tabs and four arrows that move its visible range to the left and to the right. SAPGuiStatusBar A status bar 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. SAPGuiSession Represents the SAP GUI for Windows session on which an operation is performed. SAPGuiUtil A utility object in an SAP GUI for Windows application. or simple tree control in an SAP GUI for Windows application. list tree. SAPGuiWindow A window or dialog box containing objects in an SAP GUI for Windows application. SblEdit An edit box. SiebApplication An application in a Siebel test automation environment. SiebButton A button control in a Siebel test automation environment. SblTreeView A tree view of specific screen data. SAPGuiTable A table control in an SAP GUI for Windows application. . SAPGuiTextArea A text area in an SAP GUI for Windows application. SblCheckBox A check box with an ON and OFF state. SAPGuiTree A column tree. SAPGuiToolbar A toolbar in an SAP GUI for Windows application. SAPGuiOKCode An OK Code box in an SAP GUI for Windows application. SiebApplet An applet 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. SiebRichText A rich text control 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. SiebThreadbar A threadbar in a Siebel test automation environment. SiebToolbar A toolbar in a Siebel test automation environment. SiebMenu A menu or menu item in a Siebel test automation environment. SiebList A list object in a Siebel test automation environment. SiebView A view object in a Siebel test automation environment. SiebTaskAssistant The Task Assistant in a Siebel test automation environment. Static . SiebPicklist A pick list in a Siebel test automation environment. SiebViewApplets A view applet in a Siebel test automation environment. SiebText A text box in a Siebel test automation environment. SiebScreen A screen object in a Siebel test automation environment. SiebTaskUIPane The task UI pane in a Siebel test automation environment. SiebTree A tree view object in a Siebel test automation environment.SiebCalculator A calculator control 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. SiebScreenViews A screen view in a Siebel test automation environment. SiebTextArea A text area in a Siebel test automation environment. Dialog A Windows dialog box.

WinEdit A Windows edit box. WinToolbar A Windows toolbar.A static text object. WinRadioButton A Windows radio button. WinList A Windows list. WinSpin A Windows spin box. WinObject A standard (Windows) object. WinScrollBar A Windows scroll bar. WinToolbar A Windows toolbar. WinTable A Stingray grid. WinTreeView A Windows tree-view control. WinTreeView A Stingray tree control. WinComboBox A Windows combo box. WinListView A Windows list-view control. WinTab A Windows tab strip in a dialog box. WinStatusBar A Windows status bar. XIV) Stingray Environment Object Description WinTab A Windows tab strip in a dialog box. WinEditor A Windows multi-line editor. WinMenu A Windows menu. Window A standard window. WinButton A Windows button. SystemUtil An object used to control applications and processes during a run session. WinCheckBox A Windows check box. . WinCalendar A Windows calendar.

. VbEditor A Visual Basic multi-line editor. XVI) Visual Basic Environment Object Description VbButton A Visual Basic button. VbScrollBar A Visual Basic scroll bar.XV) Terminal Emulators Environment Object Description TeField A terminal emulator field that fully supports HLLAPI. VbCheckBox A Visual Basic check box. VbLabel A static text object. TeTextScreen A terminal emulator screen that uses text-only HLLAPI or does not support HLLAPI. WinList A list in the VisualAge Smalltalk application. VbList A Visual Basic list. VbFrame A Visual Basic frame. VbEdit A Visual Basic edit box. VbComboBox A Visual Basic combo box. VbRadioButton A Visual Basic radio button. VbToolbar A Visual Basic toolbar. WinEdit An edit box in the VisualAge Smalltalk application. VbListView A Visual Basic list-view control. TeScreen A terminal emulator screen that fully supports HLLAPI. VbWindow A Visual Basic window. XVII) VisualAge Smalltalk Environment Object Description WinButton A button in the VisualAge Smalltalk application. TeWindow A terminal emulator window. VbTreeView A Visual Basic tree-view control.

WebButton An HTML button. WebFile An edit box with a browse button attached. WinTable A table in the VisualAge Smalltalk application. WebXML An XML document contained in a Web page. WebTable A table containing a variable number of rows and columns. WebEdit An edit box. ViewLink A Viewlink object. WebRadioGroup A set of radio buttons belonging to the same group. WinTab A tab strip in the VisualAge Smalltalk application. WinTreeView A tree-view control in the VisualAge Smalltalk application. Image An image with or without a target URL link. WebArea A section of an image (usually a section of a client-side image map). Page An HTML page. usually contained inside a form. WebElement A general Web object that can represent any Web object. XIX) Web Services Environment Object Description Attachments An object that supports attachment-related operations ----------------------------------------------------------------------------------------Configuration An object that supports configuration-related operations ----------------------------------------------------------------------------------------headers . Frame An HTML frame. used to select a file from the File dialog box. XVIII) Web Environment Object Description Browser A Web browser (or browser tab).WinObject An object in the VisualAge Smalltalk application. WebCheckBox A check box with an ON and OFF state. WebList A drop-down box or multiple selection list. Link A hypertext link.

WebService A test object representing a Web service. used for creating. Test: It is a set of statements or set of one or more actions.An object that supports header-related test object operations. It is a global concept. viewing and deleting test scripts. Security An object that supports security-related test object operations. Statements may have keywords. QTP Tool Window Key Elements of QTP Tool Window 1) Test Pane: It is programming interface of QTP. editing. (It is a local concept) Action: It is a set of Statements. statement etc). (Keyword such as function. . WSUtil A utility object used to check WSDL files. (It is a local concept) Statement: A minimal executable unit. method.

Test in Icon based GUI format. it takes snap shots of every statement that user performed action or operation on AUT.Test pane has 2 views. Navigation: Tools Menu> view options> we can use font size and colors etc. It can be used for understanding and editing the test easily. Expert view. 2) Active Screen It has an optional element of QTP. Note 3: User can customize Test pane view options. Key word view. Note 2: Technical users use expert view and business user use key word view. Navigation: View menu>active screen (for launching and closing) . if you perform any modifications in one view those automatically reflects in another view.Test in VB script format. Note1: Here in test pane Test is same but views are different.

used for Data driven testing.Configuring Active Screen: view>options>active screen tab>increase /Decrease capture level. apply and okay. 3) Data Table It has an integrated spread sheet (Excel like). Navigation: View menu>Data table (for launching and closing) . Note 1: Generally novice testers use this feature but it occupies lot of memory space on QTP.

It can be used in two ways. 4) Debug Viewer It is used for locating and rectifying or fixing errors. 1). Design time data table. (Attached with every test) 2). Action Sheets.for specific Action only. oracle. excel sheets.Data driven Testing: Testing the same task(S) or same operation with multiple sets of test data. Sql Server. Enter test data directly into Data Table and use. It can be used for debugging the tests by step-by-step execution. Run time data table. (debug commands) Navigation: View menu>debug viewer (for launching and closing) . QTP has Data table methods for performing operations on data table. etc. 2. We use Step into. Global Sheet. Importing data from external files (Flat files. (Available in result window) Run time is a carbon copy of design time data table.) It has two types of sheets. 2). Step over and Step out commands for debugging.for entire Test /used for all actions in the Test. etc) and Data bases (MS access. 1. Data table available in 2 ways: 1).

Through Debug viewer user can watch variables and change values of variables temporarily. Library files etc). Navigation: view menu> information . 5) Missing Resources It can be used for showing missing resources that attached to current test such as (Recovery Scenarios. Navigation: View menu >missing resources (for launching and closing) 6) Information This pane shows syntax errors automatically during saving the test.

save tests. Tool Bar options 3).7) QTP Commands QTP Commands are available in 3 ways. Menu options 2). export tests in zip format. Short cut keys (for Some important operations only) QTP Tool Window Menus File menu: Through file menu user can create. . open existing tests. 1).

In this menu object spy option available. out put values. Debug viewer. Debug Menu: This menu provides debug commands for step by step execution. . missing resources etc. information. Tools Menu: This menu provides Tools settings option. call existing actions and copy existing actions. synchronizing points. Resources Menu: This menu provides object repository and recovery scenarios options. Help Menu: This menu provides QTP help as well as VB Script help. using this user can generate recordable and nonrecordable scripts. Automation Menu: This menu provides Record. Data Table. (Properties and values) In this menu Virtual object option available. modify and delete recovery scenarios. running and also we run tests. through this option we can create virtual objects. Through this menu we can insert/remove/break points. Insert Menu: Through this menu user can inserting check points. Through this menu we can set tool options as well as test pane view options. View menu: Through this menu we can launch and close. Through this menu we can create /modify/delete objects information and we can associate repositories. deleting and splitting actions. active screen. Through insert menu user can insert VB Script conditional and loop statements and transaction points (Start and End).Edit Menu: It provides editing options and renaming. Run options and Run setting options Through this menu we can start normal recording. Through insert menu user can create new actions. view options and object identification configuration. Window Menu: This menu provides QTP tool window style settings. In this menu step generator available. through this we can get object’s information. analog recording and Low level recording. Through this menu we can stop recoding. Through this menu we can create.

. Through this menu we can check for updates and download or install directly.Through this menu we can contact technical support people and we can send feedback.

Short cut keys (for Some important operations only) File menu: Through file menu user can create.QTP Commands QTP Commands QTP Commands are available in 3 ways. open existing tests. Opens an existing business or scripted component. Command New > Test New > Business Component New > Scripted Component New > Application Area New > Function Library Open > Test Open > Business/Scripted Component Function Creates a new test. Opens an existing test. . Creates a new scripted component. Creates a new function library. Creates a new business component. 1. export tests in zip format.Tool Bar options 3. save tests.Menu options 2. Creates a new application area.

Quality Center Version Provides a sub-menu of options for Control managing versions of QuickTest assets in Quality Center. Opens an existing function library. Import Test from Zip File Imports a document from a zip file. Closes all open function libraries.Open > Application Area Open > Function Library Close Close All Function Libraries Quality Center Connection Opens an existing application area. Makes read-only function libraries editable. . The sub-menu is available only when you are connected to version-control enabled Quality Center project. Saves a standalone copy of the current test together with its resource files. enabling you to connect to a Quality Center project. Save Save As Saves the active document. Closes the active function library. Opens the Quality Center Connection dialog box. Saves all open documents. Opens the relevant Save dialog box so you can save the open document. Save Test with Resources Save All Enable Editing Export Test to Zip File Creates a zip file of the active document.

Edit Menu: It provides editing options and renaming. . Closes the QuickTest session. deleting and splitting actions. Command Undo Function Reverses the last command or deletes the last entry you typed. (Not relevant for function libraries) Opens the Process Guidance Management dialog box. Prints the active document. enabling you to define settings for the open document. (Available only from function libraries) Settings Process Guidance Management Associate Library '<Function Library Name>' with '<Document Name>' Recent Files Exit Lists the recently viewed files. Displays the Keyword View as it will look when printed and enables you to modify the page setup. Opens the Settings dialog box. Associates the active function library with the open document.Convert to Scripted Component Print Print Preview Converts a business component to a scripted component. enabling you to manage the list of processes that are available in QuickTest.

enabling you to paste it in an external application. Available only when the selected step is a comment. Copies the content of the Documentation column of the Keyword View. and to define the values of input parameters and the storage location of output parameters. Copies the selection from your document. Changes the name of an action. Pastes the selection to your document. Deletes the selection from your document. Cut Copy Paste Delete Copy Documentation to Clipboard Action > Split Action Action > Rename Action Action > Delete Action Enables you to remove the selected call to the action. parameters. Opens the Comment Properties dialog box for a comment step. and associated object repositories for a stored action. Separates an action into two sibling actions or into parent-child nested actions. Opens the Object Properties dialog box for a Action > Action Call Properties Step Properties > Comment Properties Step Properties > .Redo Reverses the most recent operation of the Undo command. Enables you to specify the number of run iterations according to the number of rows in the Data Table. Removes the selection from your document. or delete the action and its calls from the active test. Action > Action Properties Enables you to specify options.

Searches for a specified string.ReportEvent step. Advanced > Uncomment Block Advanced > Indent Removes the comment formatting from the current or selected rows. or selected Block rows. Step Properties > Output Value Properties Opens the relevant Output Value Properties dialog box for a selected object. Step Properties > Report Properties Find Replace Go To Bookmarks Advanced > Comment Comments out the current row. Available only when the selected step is a Reporter. Outdents the step (reduces the indentation) according to the tab spacing defined in the Editor Options dialog box. Displays the Report Properties dialog box for a report step. Advanced > Outdent .Object Properties selected object. Available only when the selected step contains a test object. Step Properties > Opens the relevant Checkpoint Properties Checkpoint Properties dialog box for a selected object. Creates bookmarks in your script for easy navigation. Available only when the selected step is a checkpoint step. Moves the cursor to a particular line in the test. Searches and replaces a specified string. Indents the step according to the tab spacing defined in the Editor Options dialog box. Available only when the selected step is an output value step.

Advanced > Go to Function Definition

Navigates to the definition of the selected function.

Advanced > Complete Completes the word when you type the Word beginning of a VBScript method or object. Advanced > Argument Displays the syntax of a method. Info Advanced > Apply "With" to Script Generates With statements for the action displayed in the Expert View, and enables IntelliSense within With statements. Converts any With statements in the action displayed in the Expert View to regular (single-line) VBScript statements. Inserts an optional step (a step that is not required to successfully complete a run session).

Advanced > Remove "With" Statements

Optional Step

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 nonrecordable 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
Record Run

Function
Starts a recording session. Starts a run session from the beginning or from the line at which the session was paused. Stops the recording or run session. Runs only the active action.

Stop Run Current Action Run from Step

Starts a run session from the selected step.

Maintenance Run Starts a run session during which the Mode 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 Record and Run Settings

Starts recording in Low Level Recording mode. Opens the Record and Run Settings dialog box, enabling you to define browser preferences for recording and running your test.

Process Guidance Lists the processes that are available for List 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
Object Repository

Function
Opens the Object Repository window, which displays a tree containing all objects in the current test or component. Opens the Object Repository Manager dialog box, enabling you to open and modify multiple shared object repositories. Opens the Associate Repositories dialog box, enabling you to manage the object repository associations for the test.

Object Repository Manager

Associate Repositories

Lists the function libraries associated with the active document.Map Repository Parameters Opens the Map Repository Parameters dialog box. Command Options Function Opens the Options dialog box. through this option we can create virtual objects. Checks the syntax of the active document. Through this menu we can insert/remove/break points. In this menu object spy option available. Tools Menu: This menu provides Tools settings option. enabling you to map repository parameters. Recovery Scenario Manager Associated Function Libraries Debug Menu: This menu provides debug commands for step by step execution. Opens the Recovery Scenario Manager dialog box. through this we can get object’s information. as needed. view options and object identification configuration. enabling you to open them. Through this menu we can set tool options as well as test pane view options. enabling you to customize how tests and function libraries are displayed in the Expert View and Function Library windows. Opens the Editor Options dialog box. View Options Check Syntax . enabling you to modify global testing options. (Properties and values) In this menu Virtual object option available.

(Relevant for tests only) Opens the Data Driver dialog box. Object Spy Opens the Object Spy dialog box. identification properties. enabling you to manage all of the virtual object collections defined on your computer. enabling you to view the native properties and operations of any object in an open application. enabling you to specify how QuickTest identifies a particular test object. Opens the Web Event Recording Configuration dialog box. enabling you to specify a recording configuration level. Opens the Customize dialog box. enabling you to teach QuickTest to recognize an area of your application as a standard test object. Opens the Virtual object Manager. and create new menus. as well as the test object hierarchy. (Relevant for tests only) Replaces the previously recorded Active Screen with the selected Active Screen. and operations of the test object that QuickTest uses to represent that object.Object Identification Opens the Object Identification dialog box. Web Event Recording Configuration Data Driver Change Active Screen Virtual Objects > New Virtual Object Virtual Objects > Virtual Object Manager Customize Window Menu: This menu provides QTP tool window style settings. which displays the default Constants list for the action. . which enables you to customize toolbars and menus. (Relevant for tests only) Opens the Virtual Object Wizard.

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 7 Stages of QTP Testing Process 1) Planning o o o o Analyzing the AUT Automation Test Plan Generation Automation Framework Implementation Generating/Selecting Test cases for Automation .Help Menu: This menu provides QTP help as well as VB Script help.

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 o o o o o o o o o Inserting Checkpoints Inserting Output values Adding Comments Synchronization Parameterization Inserting Flow Control Statements Calling User defined functions and/or Reusable Actions Generating Steps though Step Generator Inserting Transaction Points Regular Expressions 4) Debugging Tests o o o o Debug Commands & Break Points Step by step execution Watching Variables Changing values of variables 5) Running Tests o o o o o Normal Execution Batch Execution Through AOM Scripting Tests Running through framework Scheduled Execution 6) Analyzing Results o o o o QTP Result window Defining our own Results Exporting Results 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) .

com/" vii) VB script other statements Examples: Option Explicit Wait (14) Recording Tests Recording and Running a) Test Recording Process It is a Process of Recording user operations on AUT (Application Under Test).Set "gcreddy" Ex2: Browser("Google"). Price ii) Object calls Ex1: Dialog("Login"). During Recording QTP Creates steps in Keyword view.EXE".icicibank."http://www.Dim x. y.Page("Google"). Simultaneously it adds Objects information into Object Repository. .Run "C:\Program Files\Internet Explorer\IEXPLORE.exe" **It launche the Application Ex2: SystemUtil."mercury") vi) Utility Statements Ex1: SystemUtil.Link("Gmail"). z Const City.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". and generates them in a script in the Expert view.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.WinEdit("Agent Name:").

Put AUT in base state 2. If we select Second option.It shows Record and Run Settings. generates total user actions in a Track File.Save the Test ii) Analog Recording: It records the exact mouse and keyboard operations.Perform actions on AUT 7.Select Record Option (It shows two Options : 1.Record and Run Test on any open window based applications 2. based on that Information performs operations on AUT. The Track file is not editable. Simultaneously it stores objects information into object repository. After Providing the path it records only on that particular application. Navigation: 1. but unable to record continuous mouse operations like Digital Signatures. 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. graphs. 8. Navigation: Automation>Record Or Select Record option on automation toolbar Or Use short cut key (F3) Steps for preparing a Test (through Recording): 1.Record and Run only on) If we select first option it records on any opened application on Desktop.Click OK 6. it asks for the path of the AUT.Keep tool under recording mode .Stop recording. It is not useful for recording normal operations why because it does not generate steps for each operation. Select type of Environment (Windows or Web) 4. During recording QTP generates VbScript statements in Test Pane.Select Record Option 3.) 5.b) Running /Execution Process During Running QTP reads statements one by one and gets Object Information from the Object Repository. paints etc. We can use this mode for recording continuous mouse operations.

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 Modifications are very difficult . So QTP reduced performance will be • No Centralized Maintenance mechanism .Select any one option in the dialog box and click Start Analog record.Record relative to the following window) (If we select first option QTP records User operations with respect to Desktop co-ordinates. This mode records at the object level and records all run time objects as window or winobject Test objects.Automation>Analog Recording 4.Launch AUT (or we can launch AUT through QTP) 2.Automation >Analog Recording OR Use Short cut Key (Shift + ALT+F3) Steps for preparing a Test (through Analog Recording): 1. Use Low Level Recording for recording in an environment not recognized by QTP.2.) 5.Record relative to the screen 2. 1. Navigation: 1.It records User actions 7.Keep tool under recording mode 2. 6.Select Record option 3.Analog Recording Settings Dialog box opens (In this Dialog box two options available.Stop Recording iii) Low Level Recording It records some operations on Non-supported environments apart from Normal operations. If we select Second option. after showing the Window it records with respect to that window co-ordinates. we have to show the window (AUT).

So locating errors is difficult • Recorded scripts are QTP internal files. 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 Keyword Driven Methodology Keyword-Driven Methodology By creating our tests with a keyword-driven methodology in mind.• User may not have command on the Recorded script. Additionally. they may corrupt. focusing on the operations to test using both QuickTest built-in keywords and your own user-defined keywords. because it is possible to add objects to the object repository before they exist in an application. it is possible to begin preparing our . our tests become more modular.

We can create object repositories using QuickTest functionality to recognize and learn the objects in your application. we need to configure QuickTest to use this infrastructure: Define your global testing preferences. Setting up Object Repositories In this step. we build one or more object repositories and ensure that all objects have clear names that follow any predetermined naming conventions defined by our organization. it is best to create tests and actions that check just one or a few simple functions or complete a transaction rather than creating long tests and actions that perform several complex tasks or that perform many tasks. We need to specify configuration settings that affect how we create and run tests in general—these settings are not test-specific. or we can manually define objects. This helps make both test creation and maintenance easier over time. we can use the same object repository in multiple tests. By creating and populating shared object repositories that can be associated with multiple actions.automated keyword-driven tests even before a software build containing the new objects is available. Add (learn) objects from our application. Building our Tests We can create tests that are as simple or complex as needed. We may perform the following tasks when creating tests and test steps: . Configuring QuickTest According to our Testing Needs After we set up the test automation infrastructure. Ensure that objects in the object repository have names that are easy for application testers to recognize and that follow any established object naming guidelines. We instruct QuickTest to learn the objects in our application according to filters that we define. In general.

select File > New > Test. . Associate our function libraries with the relevant tests. Associate our object repositories with the relevant actions This enables us to insert steps that perform operations on those objects. Create the required actions. if needed. and a set of relevant operations that QuickTest can perform on the object. To do so. Each test object class has a list of identification properties that QuickTest can learn about the object. a sub-set of these properties that can uniquely identify objects of that class. This enables us to use our special keywords in any of the associated tests Test Object Model Test Object Model The test object model is a large set of object types or classes that QuickTest uses to represent the objects in your application.Create new tests.

a test object operation is a method or property that QuickTest recognizes as applicable to a particular test object class. For more information on modifying object properties. QuickTest performs the specified test object operation on the run-time object. or use SetTOProperty statements during a run session. Microsoft for Microsoft Internet Explorer objects. Netscape for Netscape Browser objects. As you add steps to your test. When you add an object to an object repository. We can view the current identification property values of any object on your desktop using the Properties tab of the Object Spy. or based on certain conditions. You may need to modify the identification property values to match the native property values. • Chooses a unique name for the test object. Understanding and Using Regular Expressions.A test object is an object that QuickTest creates in the test to represent the actual object in your application. Native operations are the methods of the object in your application as defined by the object creator. If you record steps. QuickTest: • Identifies the QuickTest test object class that represents the learned object and creates the appropriate test object. and so on). • Reads the current value of the object's properties in your application and stores the list of identification properties and values with the test object. During a run session. A run-time object is the actual object in your application on which methods are performed during the run session. The native property set for each run-time object is created and maintained by the object creator (for example. QuickTest stores information on the object that will help it identify and check the object during the run session. see Specifying or Modifying Property Values. see Viewing Object Properties and Operations Using the Object Spy. it adds the corresponding test object to an object repository. . For example. For more information. Property values of objects in your application may change dynamically each time your application opens. QuickTest records the relevant operation as it is performed on an object. Similarly. You can view or modify the identification property values that are stored with your test in the Object Properties or Object Repository dialog box. You can also use regular expressions to identify property values based on conditions or patterns you define. generally using the value of one of its prominent properties. we can add test objects to an object repository in several ways. see Managing Test Objects in Object Repositories. the product developer for ActiveX objects. or you can parameterize property values with Data Table parameters so that a different value is used during each iteration of the test. For more information. Test Object and Native Properties and Operations The identification property set for each test object is created and maintained by QuickTest. you specify which operation to perform on each test object. which is a storehouse for objects. the Click method is applicable to a WebButton test object. When QuickTest learns an object in our application. You can modify identification properties manually while designing your test.

the action uses the local object definition. you may want to use local object repositories. For more information. A local object repository stores objects in a file that is associated with one specific action. For each action. If an object with the same name is located in both the local object repository and in a shared object repository associated with the same action. If the available test object operations and identification properties for a test object do not provide the functionality you need. In this way. see Deciding Whether to Use Local or Shared Object Repositories. or you can store the objects in your tests in one or more shared object repositories. according to your needs. so that only that action can access the stored objects. see Associating Object Repositories with Actions. you can use the same shared object repository for multiple actions—if the actions include the same objects. see Viewing Object Properties and Operations Using the Object Spy. By storing objects in shared object repositories and associating these repositories with your actions. When you plan and create tests. When the objects in your application change. You can store the objects for each action in its corresponding local object repository. If you are familiar with testing. For more information. the object definition is used from the first occurrence of the object. you can use a combination of objects from your local and shared object repositories. your changes do not have any effect on any other action or any other test (except tests that call the action. you can record and run tests without creating. You can also transfer local objects to a shared object repository. This reduces maintenance and enhances the reusability of your tests because it enables you to maintain the objects in a single. For information. you must consider how you want to store the objects in your tests. or modifying shared object repositories because all objects are automatically saved in a local object repository that can be accessed by its corresponding action. it is probably most efficient to save objects in a shared object repository. see Accessing Native Properties and Operations. A shared object repository stores objects in a file that can be accessed by multiple tests (in read-only mode). In this way.We can view the syntax of the test object operations as well as the native operations of any object on your desktop using the Operations tab of the Object Spy. Object information that applies to many actions is kept in one central location. We can retrieve or modify property values of the test object during the run session by adding GetTOProperty and SetTOProperty statements in the Keyword View or Expert View. as described in Inserting Calls to Existing Actions). For more information. you enable multiple actions to use the objects. You can also use the attribute object property to identify Web objects in your application according to user-defined properties. you can update them in one location for all the actions that use this shared object repository. If an object with the same name is located in more than one shared object repository associated with the same action. If you modify an object in the local object repository. . according to the order in which the shared object repositories are associated with the action. you can access the internal operations and properties of the run-time object using the Object property. if required. choosing. If you are new to using QuickTest. Understanding Object Repository Types Objects can be stored in two types of object repositories—a shared object repository and a local object repository. shared location instead of multiple locations. We can retrieve property values from the run-time object during the run session by adding GetROProperty statements. For more information on associating shared object repositories. see Retrieving and Setting Identification Property Values.

you edit them using the Object Repository Manager. Software objects: . When you open and work with an existing test. Shared object repositories are read-only when accessed from tests.Local objects are saved locally with the action. When using a shared object repository. which has structure and properties. Object: Object is something. and can be accessed only from that action. you can use the same object repository for multiple actions. You can also use multiple object repositories for each action. Object Repository 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. it always uses the object repositories that are specified in the Associated Repositories tab of the Action Properties dialog box or in the Associate Repositories dialog box.

Ex: Buttons. WebButton. SystemUtil for launching/closing the application. Environment for using environment variables Automation objects/User defined objects User can create objects. Link. Excel. 3. 4. dictionary object class. Buttons. Ex: Creating objects in filesystemobject class. WinButton. Run time objects Test objects Utility objects Automation objects/User defined objects. Web Pages. Edit boxes. Ex: WinEdit.We call Windows. .TSR extension) Local Repository: QTP creates a Local Repository for every Action automatically during Recording. Ex: 1. User can add some more objects to Local repository User can perform rename. That cannot be shared among tests. As it is QTP internal file user no need to save modifications. Utility objects They are QTP reserved objects used for Testing and Result reporting. those can be used for performing specific operations. Local repository (. adodb. as software objects. delete operations on local repository. Services for inserting transaction points 4. There are two types of repository available in QTP. Run time objects: The objects present in the AUT. 1. Links. Check boxes etc. 2.connection class. Types of Object in QTP: There are four types of object available in QTP. 1. etc… Test Objects: References of Run time objects. Reporter for defining results. Shared repository(.. etc… Note: Test objects names vary from one environment to another. 2. 3. Application class etc.MTR extension) 2.

Local Repository: . if we select third option it stores All objects including static objects. we can select more than one class also. 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. if we select fourth option. Shared Repository: Navigation: Resource menu>object repository manager>object>Add objects>show the window/object>click ok o o o o Selected object only Default object types All objects types Selected object types (If we select first option it stores Selected objects only. That can be shared among number of tests. Using this method user can perform modifications on objects easily. if we select second option it stores all default objects.Shared Repository: User (Test Engineer) creates the Shared Repository by adding objects. Operations on Object Repository Adding objects a.) Renaming Objects a. we have to select object classes then it stores that class objects. it saves automatically) B.

if we do not want source files we can delete. Note: After merging also.Resources > object repository >select object and right click >choose rename option >modify the name>release the mouse. using this we can get objects information. >close repository b. property & Values) QTP is providing a feature called Object Spy. (Test objects names.>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. source repository files will be available. 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. Spying Objects For getting objects information. 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. Navigation>Tools>object spy>take hand icon & Show the object>get information (Object Spy shows the specific objects all available properties with their values) . Deleting Objects a. 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. Local Repository: Resources > object repository >select object and right click >choose delete option >confirm deletion>.

Importing Repository from XML file. Exporting Repository to an XML file We can export our repository file to an xml file. We can import XML file to our repository. Navigation: View>Locate in repository >show the object>click Ok>it locates specified object in the repository. In Repository manager) View Options Locate in Repository This feature can be used for identifying objects from application to repository. it can be available in 3 Areas. Navigation: Select object in the repository >view>highlight in application>it highlights specified objects in the application.(1. Highlight in Application This feature can be used for identifying objects from repository to application. 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 Object Identification Configuration Overview: . Navigation: File>import from XML >browse path of the XML file >it loads objects. In local repository 3. In tools Menu 2. Navigation: File >export Test objects to XML Enter the file name and Save with xml extension.Note: As Object spy is an important feature.

After normal identification if qtp feels not satisfied then it goes to smart . and then we configure Smart Identification for that object.Generally for every object 20-25 properties information available. if we feel normal identification is not sufficient for any object. in order to avoid Ordinal Identifier. At the end of assistive properties list also if it feels not satisfied and it finally goes to Ordinal Identifier. It learns first assistive property and once again stops and thinks. if it feels sufficient then it stops learning otherwise. QTP learns information in the following in case of Smart Identification: Smart identification is an optional feature. we can configure some more Object Identification Types a) 1) 2) b) 1) 2) c) 1) 2) 3) Normal identification Mandatory properties Assistive properties Smart identification base filter properties optional filter properties Ordinal identifier location index 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 we feel that config is not sufficient for recognizing objects in our application. qtp recognizes object using 2 0r 3 important properties. Qtp has default object identification configuration for every environment. like this qtp learns one by one.

location starts from zero. 2) index: it is based on sequence of the programs. NOTE: After executing these scripts all team members can get same settings. index starts from zero 3) Creation time: it is based on loading time of the web objects.identification. 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. For making tool settings global. QTP is providing a special feature called "Generate Script". in smart identification 2 types of properties available. If it feels sufficient.making Tool settings globally is not possible. Tool Settings Globalization: As QTP is a I-tier(Stand-alone) application. Ordinal identifiers: There are 3 types of ordinal identifiers available 1) Location: is based on object location in the AUT . STEPS: 1) Settings available in 3 areas.1. qtp generates 0. then it stops learning otherwise it goes Optional Filter Properties and learns one by one.2 like numbers. first qtp learns all base filter properties at a time and thinks whether these properties are sufficient for identifying the object uniquely. Still it feels not satisfied finally it goes to Ordinal Identifier. .

QTP Methods .

Activate: It activates dialog boxes/Windows Syntax: Object hierarchy. Activate Ex: Dialog(“Login”).Activate Window(“Flight Reservation”).Activate Click Method: It clicks on an object (Buttons) Syntax: Object hierarchy. Click Ex: Dialog(“Login”).Winbutton(“ok”).click Close Method: It closes the window,Dialog box, Browser window etc. Syntax: Object hierarchy. Close Ex: Window(“Flight Reservation”).Close Browser(“Browser”).Close Dblclick: It Double clicks the object. 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" 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 GetVisibletext: It returns Text from the specified area. Syntax: Variable =object hierarchy.getvisibletext Ex: x=Window("Flight Reservation").WinComboBox("Fly From:").GetVisibleText msgbox x 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 Navigate Method: It opens a specified URL in the Browser. Syntax: object hierarchy.navigate “URL” Ex: Browser("Yahoo!").Navigate http://www.google.co.in/

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 Getcontent: It returns all items from a combobox. Syntax: variable=object hierarchy.GetContent Ex: x=Window("Flight Reservation").WinComboBox("Fly From:").GetContent msgbox x 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

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

Value (1. Sheet_Name) Or Variable = datatable(Parameter_Name. Syntax: datatable. Sheet_Name) = Value / variable To get data Syntax: Variable = datatable.SetNextRow datatable.SetCurrentRow(Row_Number) g="gcreddy" datatable. To set data Syntax: datatable.Value (2.Value(Parameter_Name.Value (3.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.1) b=datatable. c a=datatable.SetCurrentRow (3) datatable. Sheet_Name) = Value / variable Or datatable(Parameter_Name.Value (1. b.1) c=cint(a)+cint(b) 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.SetCurrentRow (3) datatable.Value(Parameter_Name.1) = g .SetNextRow Ex: g="gcreddy" datatable.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. Sheet_Name) Ex: Option explicit Dim a.

SetPrevRow datatable. Syntax: datatable.3.SetCurrentRow (3) datatable.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.Import “Path of File” Ex: datatable.Value (1.Export “F:\gcreddy. Syntax: datatable. “Source Sheet”.ImportSheet “E:\gcreddy.Export “Path of File” Ex: datatable.ImportSheet “Path of File”.Import “F:\Inputdata.1) = s (10) Import We can use this method to import Microsoft Excel File to the Runtime Data Table (Including all sheets) Syntax: datatable. “Destination Sheet” Ex: datatable.xls” 13) ExportSheet We can use this method to export a copy specified sheet of Run Time Data table to the .(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.SetPrevRow Ex: g="gcreddy" datatable.xls” 11) ImportSheet We can use this method to import a specified sheet of Microsoft Excel Sheet to the Runtime Data table.xls”.

Close End if Next .Set Datatable("Pwd".Click End If If Window("Flight Reservation").WinEdit("Agent Name:").GetRowCount For i= 1 to Rows_count Datatable.WinButton("Cancel").WinButton("OK").ExportSheet “F:\gcreddy.GetSheet(3).Click Dialog("Login").ReportEvent micPass."res".1.3)=Login Reporter.ExportSheet “Path of File”.WinEdit("Password:").xls”. Syntax: datatable.ImportSheet "C:\Documents and Settings\gcr\Desktop\gcreddy.Exist(3)Then Window("Flight Reservation")."Passed" else Reporter.3)=Login Dialog("Login").AddSheet "Login" Datatable. “Sheet Name / Source Sheet” Ex: datatable.existing or new Excel File.xls".exist(10) Then Login="Login Operation Successful" Datatable("Result".Activate Dialog("Login")."C:\Program Files\HP\QuickTest Professional\samples\flight\app\"."Failed" Login="Login Operation Failed" Datatable("Result".3) Dialog("Login").SetCurrentRow(i) SystemUtil.3) Dialog("Login").Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.Click If window("Flight Reservation").Set Datatable("Agent"."res".exe".ReportEvent micFail."".Dialog("Flight Reservations"). 2 ********************** Data Driven Testing for Login Operation using Data Table methods Datatable.WinButton("OK")."open" Dialog("Login").3 Rows_count=Datatable.

then we can provide more properties information by separating with commas. 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. In this method of script creation. Agent Name:. Advantages: a) Descriptive Programming based Test scripts are faster in execution than Repository based Test scripts. Login."width:=60"). attached text . Setsecure. 1.Activate 3) dialog("text:=Login").Winbutton("text:=OK".Click Note: 1. text. Dynamic Programming Static Programming In this style of script generation. we provide objects information directly into the script. Dialog. OK .exe" 2) dialog("text:=Login").Descriptive Programming Descriptive Programming Entering / Providing objects information directly into the test script is called Descriptive Programming. Note 3: . Set. Password:. Click .Property values or Logical Names of the Object 4. WinEdit and WinButton – Test Objects 2. Static Programming 2. we no need to have Object Repositories.Property names 3.Winedit("attached text:=Agent Name:"). Descriptive programming is basically 2 types.Set "mercury" 5) dialog("text:=Login").Methods Note2: If we feel one property information is not sufficient for recognizing the object uniquely.Winedit("attached text:=Password:"). Activate. Example: 1) Invokeapplication "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.Set "gcreddy" 4) dialog("text:=Login").

com/" ------------------------------------------------------------------If we want maintain ‘Objects information’ in centralized location then we can use Constants.Click Advantages: If we maintain Object Information in the centralized location.Set "asdf" Dialog(Login). then we can handle ."C:\Program Files\Internet Explorer".Winedit(Pwd").icicibank. we can load the library file during run-time Syntax: ExecuteFile “Path of the Library file(.exe" Dialog(Login). if we take other line then we have to use Const Statement again. This feature is available in Tools Menu.If we want to get objects information (Test objects.Set "mercury" Dialog(Login). Agent="attached text:=Agent Name:" Const Pwd ="attached text:=Password:".Page("title:=Google").EXE". Steps: Creating Constants: Const Login="text:=Login".). Ok="text:=OK" Note: we can declare no of Constants in a line by separating with Camas (."". properties and values)."open" Browser("title:=Google"). Example 2: SystemUtil.Navigate "http://www.Winedit(Agent).Run "C:\Program Files\Internet Explorer\IEXPLORE. we can use object spy feature.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. Creating a Library file Place Constants in Notepad and save as . in local repository and in repository manager.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.Sync Browser("title:=Google").Winbutton(Ok).Activate Dialog(Login).

Create oAgent=description.Set "mercury" Dialog(oLogin).Click Note1: Create Description objects and put into one library file.Sync Browser("name:=Google").jjperfumes.value="OK" Generating Tests using Properties collection Objects Invokeapplication "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a. provide properties information and use description objects in the test script.exe" Dialog(oLogin).Run "C:\Program Files\Internet Explorer\IEXPLORE.value="Password:" oOk("text").Create Entering Properties Information into Objects oLogin("text").value="Agent Name:" oPassword("attached text"). first we create description objects. 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.Winbutton(oOK).Create oOk=description.Page("title:=Google").Navigate http://www.Winedit(oAgent). ------------------------------------------------------------------- Dynamic Programming In this style of script generation.EXE" Browser("name:=Google"). Creating Properties Collection Objects Set Set Set Set oLogin=description.value=320 oLogin("height"). we can generate tests.com/ .value=204 oAgent("attached text").Winedit(oPassword).Create oPassword=description.Set "gcreddy" Dialog(oLogin). by associating that library file.value="Login" oLogin("width").Activate Dialog(oLogin).modifications easily.

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

it takes expected result from the user and compares with actual results during execution and provides test results. . 8. 5. 9. Image checkpoint 11. we can insert these checkpoints through standard checkpoint. 4.Inserting Checkpoints Inserting Checkpoints Check point is a verification point. 6. 7. There are 11 Checkpoints available in QTP: 1. Table checkpoint Note 1: From 6 to 11 checkpoints are only for Web. 3. 2. Standard check point Text check point Text area check point Bit map check point Data base check point Accessibility check point XML Check point (from Application) XML Check point (from Resource) Page check point 10. Note 2: From 9 to 11 checkpoints are hidden checkpoints.

Navigation for Deleting standard checkpoint: Select Checkpoint statements and right click > choose delete option.1. Standard Checkpoint: It checks object property values. We can use this checkpoint for checking any property value. Navigation for Editing standard checkpoint Select Checkpoint statement and right click > choose checkpoint properties option > modify the value > click Ok. 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. . 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.

Through expert view. exact match. exact match.) . b. c. ignore spaces. Navigation: Keep tool under Recording mode > Insert menu> Checkpoint > Text area checkpoint > Mark the area of text > select one or more options (Match case.Note: We can insert standard checkpoints in 3 ways.) We can select one or more options > click ok & stop Recording. a. Through keyword view. Through Active screen. text not displayed. text not displayed. 3) Text Area Checkpoint: It checks the text area present in the application. ignore spaces. 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.

Note: here we do not need to put tool under Recording mode and we do not need AUT since data is from backend. 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. we can compare complete bitmaps as well as part of the bitmaps. 6.Click ok and stop recording. Database checkpoint: It checks Content of the back end Database. 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. 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. Bitmap checkpoint: It compares bitmaps. . 5. 4.

If an item is available. Navigation: Keep tool under Recording mode in web environment > insert menu > checkpoint (from application)> show the xml pages >click ok > stop Recording. according to our requirements. XML Check point (from Application) It checks content of the XML file. . XML Check point (from Resource) It checks content of the XML file.It is a configurable checkpoint. according to W3C rules then Pass. 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. If an item is not available then result would be pass 7. Result Criteria: a) b) c) If item is available but not according to W3C rules then fail. 8. we can customize.

Navigation: Keep tool under Recording mode with web environment > Insert menu > checkpoint > Standard checkpoint >show the web page > click ok > click ok > stop recording. Note: 2.Navigation: Insert menu > checkpoint >xml checkpoint (from resource) > browse path of the XML File > click ok > click ok. and then we can go for inserting xml checkpoint from resource. 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. It is a hidden checkpoint. Note: 1. separate path is not available then we can choose inserting XML checkpoints from application. 9. Images and Loading time in a web page. . Page checkpoint: It checks number of Links. we can insert this through standard checkpoint. If XML file is part of web application. If XML file is an individual and path available. 10.

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

5. Types of Output Values: 1. Standard output value Text output value Text area output value Database output value XML output value (From Application) XML output value (From Resource) 1) Standard output value: . 3.Inserting Output values Inserting Output Values It is a step in which one or more values are captured during test execution. it is located in QTP result window and can be retrieved later. 2. 6. 4. It is stored in run time data table. 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.

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. 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.> 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. 2) Text output value: We can use Text output values to output text strings displayed in an application.We can use standard output values to output the properties values of most objects.. 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. .

4) Database output value: We can use Database output values to output the value of the contents of database cells. 5) XML output value (from application): we can use XML output values to output the values of XML elements in XML documents. 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. . 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. Navigation: Insert menu >output value> XML output value from resource > browse path of the XML file > click ok > select elements >click ok. 6) XML output Value (From Resource): We can use XML output values to output the values of XML elements in XML documents.

Dynamic Test Data Submission 3. 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.WinButton("Button"). Types of Parameterization: We can parameterize tests in several ways in QTP 1.WinButton("OK"). Through Loop Statements: We can use loop statements for passing sequential numbers & Logical Numbers.Click Next 2.WinEdit("Edit").Dialog("Open Order"). For orderno=1 to 10 step 1 ' for one increment step keyword is not mandatory Window("Flight Reservation"). we can use Data Table for Data Driven Testing. .WinEdit("Agent Name:"). Note: We can’t generate Strings. Oracle etc). 1. Through Loop Statements 2. Fetching Test Data directly from External files (Flat files & Spreadsheets) 5. Fetching Test Data directly from Databases (MSAcess.Set "ON" Window("Flight Reservation").Dynamic Test Data Submission: Through Loop Statements we can give strings also but every time user has to enter data. Through Data Table: QTP adds one data table (Spreadsheet) for every test. Through Data Table 4.Activate Dialog("Login").Close Next 3.Set Agent Dialog("Login").Parameterization Passing parameters.Type micTab Dialog("Login").Dialog("Open Order").exe" Dialog("Login").Click Window("Flight Reservation"). 6.WinEdit("Password:").WinEdit("Agent Name:"). Data Driven Testing: Testing the Same operation with multiple sets of test data.WinButton("OK").WinCheckBox("Order No.Set orderno Window("Flight Reservation").Click Window("Flight Reservation"). It has 3 types of usage .Activate Window("Flight Reservation").SetSecure password Dialog("Login")."). Getting Test Data from front end objects. We use parameterization in Data Driven Testing.Dialog("Open Order"). through this we can pass multiple values.

Sheet id) Example: agent=datatable(“agent”. Steps: Generate the basic test>open data table(View>Data Table) 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”.WinEdit("Password:").Close .Activate Dialog("Login"). A.Type micTab Dialog("Login").1) invokeapplication "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a. Entering test data directly into data table and use.Set Agent Dialog("Login").1) Pass parameters.WinEdit("Agent Name:").) Run the test.1) pwd=Datatable ("Password".Click Window("Flight Reservation").WinButton("OK"). Entering test data directly into data table and use b.exe" Dialog("Login"). Importing test data from external Spread sheets d. Agent = Datatable("Agent". Importing test data from Data bases.SetSecure pwd Dialog("Login").WinEdit("Agent Name:").a. Importing test data from external Flat files c.

but first we have to create /get the DSN(Data source Name)& we have to use SQL Commands. Entering Data into Tables: Select table>enter the data. 1. 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. Start programs>MS Office>MS Access>file >new>Select blank Database>enter name of the database>Save with mdb extension. Creating a Test Database: open MS Access (or we can use any other database). Importing test data from Data bases: Through Data table we can import Test Data from Data bases. c. 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. D.b. 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. .

con do until rs. by using the DSN we can get data for number of tests.WinEdit("Password:").WinEdit("Agent Name:").Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.WinEdit("Password:").skipline While myfile.4.fields("password") Dialog("Login").WinEdit("Agent Name:").eof=true SystemUtil.movenext loop .provider=("microsoft.Type micTab Dialog("Login").exe".mdb" rs.Activate Dialog("Login")."@") SystemUtil.open "select * from login".Type micReturn Window("Flight Reservation").Set rs.WinEdit("Agent Name:").Type micTab Dialog("Login").opentextfile("d:\trigun.Close Wend Fetching Test Data directly from Excel Sheets Fetching Test Data directly from Databases Option explicit Dim con.WinEdit("Password:"). myfile Set fso=createobject("scripting.1) myfile.Type micReturn Window("Flight Reservation").recordset") con.Set s(0) Dialog("Login"). 4.Activate Dialog("Login").SetSecure S(1) Dialog("Login")."". Fetching Test Data directly from Flat files Dim fso.SetSecure rs.open "C:\Documents and Settings\pooja\My Documents\trigun.0") con."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\". Note: DSN Creation is one time activity.filesystemobject") Set myfile=fso.rs Set con=createobject("adodb.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.jet.fields ("agent") Dialog("Login").txt".exe".Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.connection") Set rs=createobject("adodb.Close rs.oledb."open" Dialog("Login").atendofline <> true x=myfile.readline S=split(x."open" Dialog("Login").WinEdit("Agent Name:")."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\"."".WinEdit("Password:").

waitproperty “property name”.value. Syntax: Object Hirearchy.Sync Selecting an appropriate Method: . In order to get proper results in between QTP & AUT synchronization is required. Syntax: object hierarchy. but QTP does not wait up to maximum time unnecessarily. There are several methods available in QTP for synchronization. 1. Inserting Synchronization points. Increasing Tool default synchronization time. 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. 3. 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.Synchronization It is a process of matching the speeds of both QTP and AUT in order to get proper execution and results. After completion of one statement execution it goes to next statement immediately.Page("Yahoo! Toolbar"). Inserting Wait statements. that time we may not get proper execution and results. Sync Method: (only for WEB) Waits for the browser to complete current navigation. Note: if we insert Synchronization points. it does not wait up to maximum time. Syntax: Wait(time in seconds) Note: If we insert wait statements QTP waits up to maximum time even though operation is completed.time in milli seconds. 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. 2. 4. after completion of the current operations.Sync Ex: Browser("Yahoo! Toolbar"). it goes to next step immediately. Sync Method (Only for WEB) 5. but AUT takes less time for some operations execution and more time for some operations execution. Where Synchronization is required: During test execution QTP gives instructions one by one with same speed.

it is better to use wait statement in functions. 3. .1. Suppose in our test one or more statements only are taking more time for execution then selecting “Inserting synchronization method” is better. even though some drawbacks are there in using wait statement. 2. Above two are local features but wait statement is Vbscript feature. Suppose in our test more statements are taking more time for execution then selecting “increasing tool time out” .

EndTransaction "Login" Note: We can insert number of transaction points in a test Using Timer Function ‘Timer’ is a VB Script Built-in function.StartTransaction “Transaction Name” Statements -----------Services. ST=Timer’ It returns elapsed time since 12:00 AM Mid night in seconds Example: .StartTransaction "Login" SystemUtil.Inserting Transaction Points Inserting Transaction Points QTP is providing a Utility object called Services for measuring transaction time Suppose. that can be used for measuring transaction time.SetSecure "4baf50f18b0ae0d5f5425fe760653e96da50bde7" Dialog("Login").WinButton("OK"). we want to measure how much time that one test or part of the test is taking for execution/running.WinEdit("Agent Name:")."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\"."open" Dialog("Login")."".Set "naga" Dialog("Login"). we can measure using these transaction point (Start and End) Syntax: Services.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.WinEdit("Password:").EndTransaction “Transaction Name” Note: these options (Start and End Transactions) available in QTP tool Insert menu Example: services.Activate Dialog("Login").exe".Click Window("Flight Reservation").Activate services.

SetSecure "4baf50f18b0ae0d5f5425fe760653e96da50bde7" Dialog("Login"). you can take any variable.Click Window("Flight Reservation").Set "naga" Dialog("Login")."open" Dialog("Login").Activate ET=Timer TT=ET-ST msgbox TT Note: here ST.exe".WinEdit("Agent Name:").SystemUtil.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.Activate Dialog("Login"). I used: ST for Start Transaction ET for End transaction TT for Transaction Time .WinButton("OK"). ET and TT are variables."".WinEdit("Password:")."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".

or Active Screen. We can parameterize any of the values in our step. We can continue to add further steps at the same location without closing the Step Generator. in function libraries. Navigation: Insert menu->Step Generator Or Use Shortcut key F7 The Step Generator enables us to add steps by selecting from a range of context-sensitive options and entering the required values. We can open the Step Generator from the Keyword View. In the Step Generator dialog box we can define steps that use: Test object operations (tests only) Utility object operations Calls to library functions (tests only).Step Generator Step Generator (F7) Step Generator is a feature of QTP. Expert View. or function) and define the arguments and return values. Before we open the Step Generator to define a new step. The Step Generator then inserts a step with the correct syntax into y test. we cannot use the Step Generator to access test object names or collections. or that stores the returned value of a method as an output value or as part of a conditional statement. property. VBScript functions. Utility object or function) and the required object or the function library. used for generating the Recordable and Non-Recordable steps. After we open the Step Generator. Library of Functions. or to access the list of library functions. Note: we can use the Step Generator to insert steps in tests and function libraries. Hover. and internal script functions For example. We can then select the appropriate operation (method. . we can add a step that checks that an object exists. we first select the category for the step operation (test object. parameterizing them if required. we first select where in our test the new step should be inserted.

the single quotation mark is a valid VBScript character that has uses beyond delimiting comments. Because we are less likely to use '* anywhere else in our script. Although most script writers use the single quotation mark. REM This is a comment using the REM statement as a delimiter. To ensure that the script host does not attempt to interpret a comment as a command. you might consider following the single quotation mark with an asterisk when commenting your code: '* This is another comment. such a procedure might also retrieve items that are not comments.Adding Comments Adding Comments to Scripts Comments are statements that are ignored by the script host when the script runs. both of the following lines of code are valid comments: ' This is a comment using a single quote delimiter. VBScript allows two delimiters: the single quotation mark (') and the REM statement. First. . This approach has two advantages over the single quotation mark alone. it makes the comment stand out from the rest of the text. we must preface each comment with a comment delimiter. Second. a single quotation mark by itself can be difficult to see at times. For example. This can be a problem if we use an automated procedure to extract comments from a script. it makes a good delimiter.

MapNetworkDrive "Z:"." End If . ----------------------------------------------On Error Resume Next Set WshNetwork = WScript. "\\RemoteServer\Public" '* Check to make sure the operation succeeded. Most people find it easier to quickly identify the comments used in the second half of the script. Err. Comments included on the same line as a VBScript statement (end-of-the-line comments) are valid but can be difficult to read. comments are placed on the same line as a VBScript statement. If Err. in the first half of the script. WshNetwork. If Err.Network") WshNetwork. For example.Always include comments on separate lines except for comments that accompany the declaration of a variable." End If '* Map drive Z.Echo "The drive could not be mapped. while in the second half of the script.MapNetworkDrive "Z:". "\\RemoteServer\Public" '* Map drive Z. compare the two commenting styles in the following script snippet.CreateObject("WScript.Clear Wscript.Number <> 0 Then '* Check to make sure the operation succeeded. the comments are placed on separate lines.Number <> 0 Then Err.Clear Wscript.Echo "The drive could not be mapped.

Procedure header comments should include the following section headings. Return values for functions and variables that are changed by a procedure. dialog boxes. The code itself and any necessary inline comments describe the implementation. Variables. procedures. enumerating objects. erroneous comments. controls. algorithms. and procedures should be named clearly to ensure that inline comments are only needed for complex implementation details. or worse. This description should not describe the implementation details (how it does it) because these often change over time. resulting in unnecessary comment maintenance work. you should include an overview that describes the script. and other system dependencies. especially through reference arguments. At the beginning of your script. Sometimes a piece of pseudocode describing the algorithm can be helpful.----------------------------------------------Code Commenting Conventions All procedures should begin with a brief comment describing what they do. should also be described at the beginning of each procedure. . Arguments passed to a procedure should be described when their purpose is not obvious and when the procedure expects the arguments to be in a specific range. Section Heading: Comment Contents: Purpose: Assumptions: Remember the following points: Every important variable declaration should include an inline comment describing the use of the variable being declared.

QTP is providing debug commands and breakpoints. c. If it is function call. Debug Commands: 1) Step Into (short cut key F11): a. 2) Step Over (Short cut key F10): a) It executes one statement at a time after execution starts b) It executes all functions statements at a time Note: After opening the function. For debugging.Debugging Tests Debugging Tests Debugging is a process of executing the script or a program in a User designed fashion with some temporary break points in order to identify the errors. it opens the function. It executes one statement at a time. It starts execution b. if we use step over it executes one statement at a time only. . after that it executes one statement at a time.

Ex: Dim a. Navigation: Place cursor in desired location >Debug menu>Insert/Remove break point Or Use short cut key (F9) .c a=100 b=200 c=a+b msgbox c msgbox "hello" Call hyderabad msgbox "bye bye" Note: Create a script and work on it Break Point: This feature is used for breaking the execution temporarily.b.3) Step Out (shift +F11): It executes all remaining statements in a function at a time.

Note: If we want to execute Some part of the Test Script at a time and some other part of the test script step by step. Watch 2. there we can use breakpoints. We can watch variables whether the variables are taking correct values or not at a specific point of time.z x=10 y=20 z=x+y msgbox z msgbox "Hello" x=35 . 1. We can change Values of Variables temporarily. modifying or setting the value of the variables during the execution break with the help of 3 Tabs.Or Place mouse pointer before the statement and click. Command Note: Through Debug Viewer Pane. Debug viewer Pane: It is used for viewing. Variables 3. Ex : Dim x.y.

y=67 z=x*y msgbox z msgbox "bye bye" Navigation: View menu > Debug Viewer > Use step into feature. .

For defining our own results. Status of the Result: QTP has 4 types of result status a) Pass b) Fail c) Done d) Warning Defining our own Result: Generally QTP provides. Syntax: Reporter.ReportEvent micPass. It provides test wise result only. QTP Result Window: After Running/Executing a test. Note: QTP doen't provide batch wise test result. suppose if we use flow control statements (conditional and Loop statements). if we execute test batches. After Running Tests.Message . HTML. User (Test Engineer) has to analyze the test result. then we have to define our own result. and send defect reports. Res-Result step "Login operation Successful". QTP is providing an utility object called "Reporter" by using reporter.Doc).Analyzing Test Results & Reporting Analyzing the Test Result is not a responsibility of QTP. test results."message" Example" Reporter. we export test result from result window in Document (. then QTP Provide result window. if we use qtp tool features like checkpoints."Res". we can define our own results.ReportEvent status of the Result."Result Step". XML and PDF formats."Login operation Successful" exaplanation: Reporter.Utility object ReportEvent-Method micPass-Status of the Result.

Status of the Result: 1) Pass -micPass or 0 2) Fail -micPass or 1 3) Done.micDone or 2 4) Warning.micDone or 3 .

we can report defects in various methods. In between QTP and Quality Center back to back integration is available. If we are using Bugzilla or Zera or PR-Tracker like Bug Tracking tool. Result Exporting facility also available in QTP Result window. After Running Tests. QTP provides result in Result window and also provides a facility to define our own Results. . If we are using QTP for Functional Test Automation and Defect management manual. then entering defect details in company prescribed format and sending. After analyzing results. then after analyzing results. We can create and execute tests using QTP. then we can send defects directly from QTP result window. QTP Provides. if we find any mismatches sending defects through the Bug tracking tool (Every Bug Tracking tool has its own defect report template) If we are using Quality center for Test management.Reporting Defects QTP is an Object based Test tool. Any how Analyzing Results is the Responsibility of Test Engineer after running tests. various methods for crating and enhancing Tests.

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. Prepare Scripts for those actions.Actions Action: Set of Statements for perfoming a Task(s) We divide our test into actions to streamline the process of testing. insert. .delte) 2. Splitting an action: Navigation: Place cursor in desired location>Edit menu>action>split action>Enter Action 1 name & action 2 name. Create required actions(ex login.

Deleting Actions: Select desired action in action drop down box>edit menu>action>delete action>confirm deletion. Making an action reusable: Select Non Reusable action >edit >action>action properties>check reusable action check box >click ok. . Generate total test in the default action 2. Note: we can edit this action. Renaming actions: Select desired action in action drop down box> edit menu>action>rename action>modify the name>click ok. Calling an action: Insert>call to existing action>browse path of the test>select desired action>click ok. Split into meaningful actions.Steps: 1. 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: At a time we can split one actions into 2 actions.

Lengh) Example: Dim val.3) msgbox x ' Output: Hyd val="9247837478" x=Left(val.3) msgbox x ' Output: 10/ .5) msgbox x ' Output: 92478 val=#10-10-10# x=Left(val.VB Script String Functions String Functions 1) Left Function Returns a specified number of charectors of a given string from left side Syntax: variable=Left(string.1) msgbox x ' Output: 9 val="H92yderabad" x=Left(val.x val="Hyderabad" x=Left(val.3) msgbox x ' Output: H92 x=Left(9247837478.

5) msgbox x ' Output: 37478 val=#10-10-10# x=Right(val.x val="Hyderabad" x=Right(val.5.2) Right Function Returns a specified number of charectors of a given string from Right side Example: Dim val.3) msgbox x ' Output: bad val="9247837478" x=Right(val.5) msgbox x ' Output: /2010 3) Mid function Returns a specified number of charectors of a given string Example: Dim val.3) msgbox x ' Output: rab val="Hyderabad" x=Mid(Val.x val="Hyderabad" x=Mid(Val.3) msgbox x ' Output: bad x=Right(9247837478.5) msgbox x ' Output: rabad .1) msgbox x ' Output: 8 val="H92yderabad" x=Right(val.

5) msgbox x ' Output: 0/2010 4) StrReverse retuns reverse value of a string Example: Dim val.6.5) msgbox x ' Output: 837478 val=#10-10-10# x=Mid(val.5) msgbox x ' Output: 37478 val="H92yderabad" x=Mid(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) .1) msgbox x ' Output: H92yderabad x=Mid(9247837478.val="9247837478" x=Mid(val.

str2.x str1="India" str2="India" x=StrComp(str1.1) msgbox x 'Output -1 str1="Indian" str2="Ndia" x=StrComp(str1.1) msgbox x 'Output 0 str1="india" str2="INDIA" x=StrComp(str1.1) msgbox x 'Output 1 str1=100 str2=100 .str2.1) msgbox x 'Output 0 str1="India" str2="Indian" x=StrComp(str1. returns 1(one) b) String 2 greater than string 1.1) msgbox x 'Output -1 str1="Indian" str2="India" x=StrComp(str1. returns -1 Example: Dim str1.msgbox x 'Output: 001 5) StrComp Function It compares two string (Binary and textual) if a) Both are equal.str2.str2. returns 0(zero) b) String 1 greater than string 2.str2.str2.

x val="HYDERABAD" x=Ucase(val) msgbox x 'Output HYDERABAD .1) msgbox x 'Output -1 6) Lcase function Coverts Upper case values into Lower case Dim val.x=StrComp(str1.str2.1) msgbox x 'Output 0 str1=100 str2=101 x=StrComp(str1.str2.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.

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 .

We can create as many files as we want and we can change values of variables.Set "kajal" Dialog("Login"). If we declare as local variables in number of tests. Built in variables: These are system defined variables.Click Creating user defined environment variables: Navigation: .WinButton("OK").SetSecure "4b3c86f2107ff565cc195ba6c24739091b656407" Dialog("Login").Run ProductDir & app Dialog("Login").Environment Variables Environment Variables in QTP These are global variables. Types of Environment variables: 1. User defined variables: Variables that we predefine in the active external environment variables file.WinEdit("Agent Name:"). 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. if you want to use some variables globally (From number of tests) declaring as global variables is better. modifications are difficult.Activate Dialog("Login").WinEdit("Password:").exe" Systemutil. we can access from all tests but these are designed as read only. 2.

save with xml extension > click ok. .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.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. 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. Or We can load environment file directly Environment.

Regular Expressions Regular Expressions in QTP What is Regular Expression? It is a way of representing data using symbols. We can define the text string as a regular expression. Ways of Regular Expressions: . 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. 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. searching or replacing algorithms. They are often used within matching. For XML checkpoints we can set attribute or element values as regular expressions. We can define a regular expression in standard checkpoint to verify the property values of an object. when creating a text checkpoint to check that a varying text string is displayed on our application. a Data Table parameter value. Regular Expressions in QTP: Regular expressions can be used in QTP for identifying objects and text strings with varying values. an Environment parameter value. or a property value in Descriptive programming.

1868. such as the letters n. Example: [^ab] Matches any character except a or b. 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. if the backslash (\) is used in conjunction with some characters that would otherwise be treated as literal characters. e) Matching Any Single Character within a Range: To match a single character within a range. welcomed. caaaaaar. t. For example: ca*r Matches car.) instructs QTP to search for any single character (except for \n). enter: 186[789] d) Matching Any Single Character Not in a List: When a caret (^) is the first character inside square brackets. Example: For matching any year in the 2010s. Alternatively. the combination indicates a special character. w. it instructs QTP to match any character in the list except for the ones specified in the string. Ex: To search for the date 1867. Matches welcomes. Ex: welcome. or welcome followed by a space or any other single character. and cr g) Matching One or More Specific Characters: . or 1869. we can use square brackets ([ ]) with the hyphen (-) character. c) Matching Any Single Character in a List: Square brackets instruct QTP to search for any single character within a list of characters. b) Matching Any Single Character: A period (. It can be used in conjunction with a special character to indicate that the next character be treated as a literal character. or d.a) Backslash Character: A backslash (\) can serve two purposes.

but not cr. starting. we can use a combination of brackets and an asterisk to limit the search to a combination of non-numeric characters. k) Matching the Beginning of a Line: A caret (^) instructs QTP to match the expression only at the start of a line. .* Matches start. j) Matching One of Several Regular Expressions: A vertical line (|) instructs QTP to match one of a choice of expressions. h) Matching Zero or One Specific Character: A question mark (?) instructs QTP to match zero or one occurrences of the preceding character. + .A plus sign (+) instructs QTP to match one or more occurrences of the preceding character. _). For example: ca?r Matches car and cr. and so forth. For example. 0-9. 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. n) Matching Any Non-AlphaNumeric Character: \W instructs QTP to match any character other than alphanumeric characters and underscores. a-z. m) Matching Any AlphaNumeric Character Including the Underscore: \w instructs QTP to match any alphanumeric character and the underscore (A-Z. or after a newline character. { } ). starter. just as in mathematics and programming languages. ? . For example: ca+r Matches car and caaaaaar. Using groups is especially useful for delimiting the argument(s) to an alternation operator ( | ) or a repetition operator ( * . start. started. but nothing else. o) Combining Regular Expression Operators: We can combine regular expression operators in a single expression to achieve the exact search criteria we need. i) Grouping Regular Expressions: Parentheses (()) instruct QTP to treat the contained sequence as a unit.

FileSystemObject") Set objShell = CreateObject("WScript.Test(objFile. 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.Global = True objRE.Name) If bMatch Then WScript.Files Set objRE = New RegExp objRE. It provides simple support for defining regular expressions.IgnoreCase = False objRE. ([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.Shell") strCurrentDirectory = objShell. 3 digits. we need to match numbers with 1 digit. The regular expression below matches any number between 0 and 1200.Arguments(0) For Each objFile In colFiles bMatch = objRE.GetFolder(strCurrentDirectory) Set colFiles = objFolder. 2 digits.Pattern = WScript.For example: [a-zA-Z]* To match any number between 0 and 1200.Echo objFile.CurrentDirectory Set objFolder = objFS.Name End If Next . or 4 digits between 1000-1200.

2) Match Content in a File against a Regular Expression strFileName = "E:\gcreddy.Echo strFileContents objTS.txt" Set objFS = CreateObject("Scripting.IgnoreCase = False objRE.Close Set objRE = New RegExp objRE.Value Next .FileSystemObject") Set objTS = objFS.Echo "At position " & objMatch.Arguments(0) Set colMatches = objRE.OpenTextFile(strFileName) strFileContents = objTS.Pattern = WScript.Echo "Searching Within: " WScript.Global = True objRE.FirstIndex & " matched " & objMatch.Execute(strFileContents) WScript.Echo vbNewLine & "Resulting Matches:" For Each objMatch In colMatches WScript.ReadAll WScript.

We can manage the virtual objects defined on our computer using the Virtual Object Manager.Virtual Object Configuration Virtual Object Configuration Virtual Object Configuration: Virtual Object Configuration is a process of making the QTP to treat a specified area or a user defined object as Virtual Object. Navigation:  Select Tools Menu . Virtual objects enable us to create and run tests on objects that are not normally recognized by QTP.

      o o     Go to Virtual objects Select ‘New Virtual Object’ option Click Next Mark the area in the Application with help of mark object button Click next Select one of the following options Entire Parent hierarchy Parent only Click on Next Specify the Desired object name Specify the Desired collection name Click finish Virtual Object Manager: Virtual object Manager feature enable us to create and manage Virtual Objects .

QTP is providing a separate Tool called Test Batch Runner. Navigation: Start>program>quicktest professional>Tools>Test Batch Runner>File>new>batch>add>browse path of the test (like this add number of tests)>save with MTB extension (Module test batche)>close test batch runner. Open 'Test batch Runner' Tool and Form Batches. 5) View Test wise Result in 'Test Result Viewer'. Note: QTP doesn’t provide Batch wise result. Forming a Test Batch: Launch Test Batch Runner. 3) Provide permission to 'Test batch Runner' to run tests 4).Batch Testing Batch Testing or Batch Execution Executing a group of Tests or series of tests at a time is known as Batch Testing or Batch Execution. Steps for Batch Testing: 1). . Create Individual Tests and Run once. For performing Batch Testing. Run or Execute Test Batches from Test Batch Runner. 2).

>Select selected executable application->Next ->Select Recovery Operation [Keyboard.qrs” (qrs stands for QuickTest Recovery Scenario.>Next . To handle unwanted popups. Recovery Scenarios Recovery Scenario Manager To recover from unexpected events and errors that are occurred in the test environment during run session. Close Application Process.> Select Application Crash as Trigger event->Next .>Close .>Save the scenario in specified location with “.>Select Option . Mouse Operation.) (ii) Popup Window. Restart. Navigation: Resources Menu -> Recovery Scenario Manager-> Click New. Navigation: Tools>Options>Run>check allow other mercury products>apply & Ok Executing partial Test Batch Open Test Batch Runner >open Test Batch>Select or deselect tests>run test batch. Note: Allowing other products to Run Tests.>Next . function Call. For good recovery. error must be known the occurrence is unknown. Navigation: Resources Menu ->Recovery Scenario Manager ->New .>Enter Scenario Name ->Next.>Select “Popup .Running or Executing a Test Batch Open Test Batch Runner Tool Navigation: File>open>browse path of the test batch>batch>run Note: Test Batch Runner launches QTP Tool. Microsoft Windows] ->Next . There are (4) Types of events such as: (i) Application Crash An open application fails during Test Run. we can use Recovery Scenario Manager.> Click Next .>Finish . QTP runs Tests one by one.>If you want to check Add another operation else uncheck->Next .

Proceed to next test iteration. Proceed to next test iteration.qrs” -> Record required Recovery Operation [Click ok. Proceed to Next step.>Next .vbs fie path ->Next ->Uncheck Add another Recovery Operation .vbs extension] ->Browse the .> Select Post-Recovery Test Run Option [Repeat current step and continue.false)->click next -> Select function call as Recovery Operation -> Next [Open Notepad -> Save empty file with . Restart current test run. Proceed to Next Action.>Select “Testrunerror Window” as Trigger event ->Next ->select any error o .qrs” ->Record required Recovery Operation [Click ok. Click Cancel] take the script into function ->Save the library file ->Click Run (iii) Test Run Error. Proceed to Next Action.>Next . Stop the Test Run] -> Next-> Enter Scenario Name -> Next -> Select Option -> Finish -> Save the scenario with “. The property values of an object in your application match specified values.>Next . Navigation : Resources Menu ->Recovery Scenario Manager ->New . Stop the Test Run] ->Next ->Enter Scenario Name ->Next . Click Cancel] take the script Click Run Save the library file �� into function �� (iv) Object State.>Next -> Select Post-Recovery Test Run Option [Repeat current step and continue. Stop the Test Run] �� Select Option �� Next �� Enter Scenario Name �� �� Save the scenario with Finish �� Record required Recovery Operation [Click “.> Finish ->Save the scenario with “.>Select function call as Recovery Operation ->Next [Open Notepad ->Save empty file with . Proceed to Next Action.Window” as Trigger event ->Next ->Click on Hand Icon . A step in your test does not run successfully then Test Run Error can be raised. Restart current test Next run.>Select Option .>Show unwanted window with Hand icon ->Next ->Next . 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 .vbs fie path -> Next -> Uncheck Add another Recovery Operation -> Next -> Select Post-Recovery Test Run Option [Repeat current step and continue.>Next .vbs extension] . You can specify property values for each object in the hierarchy. Proceed to Next step.>Browse the . Proceed to Next step. Click Cancel] take the script into function -> Save the library file -> Click Run .vbs extension] -> Browse the .vbs fie path ->Next ->Uncheck Add another Recovery Operation . Restart current test run.qrs” �� ok.>Select function call as Recovery Operation ->Next [Open Notepad ->Save empty file with . Proceed to next test iteration.

methods. it allows users to create. drives. and events to process folders and files.method syntax with a rich set of properties. It allows us to use the familiar object.File System Operations File System Operations File System: Its an operating system feature. view and delete.folders and files VB Script is providing an object called scripting. We can also employ the traditional Visual Basic statements and commands.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. modify. .

alter. such as their names and the date they were created or last modified. In this case.filesystemobject") fso.FolderExists(strFolder) Then . contained in the Scripting type library (Scrrun. We may not want to have such overhead. doing so adds a significant amount of overhead to our application. and delete folders.dll). storing our data in a text file or binary file is the most efficient solution. When processing files. our primary goal is to store data in an efficient. or our data access requirements may not call for the extra functionality associated with a full-featured database. supports the creation and manipulation of text files through the TextStream object. and output (read) the data. insert and change the data. strFolder strFolder="D:\Documents and Settings\gcreddy\Desktop\Dibyalok" Set fso=createobject("scripting.The FSO model gives our application the ability to create. move. It also enables us to get information about folders. use the FileOpen Function with the Binary keyword. however. or to determine if and where particular folders exist. strFolder strFolder="D:\Documents and Settings\gcreddy\Desktop\Dibyalok" Set fso=createobject("scripting. The FSO model makes processing files much easier as well. easy-to-access format.filesystemobject") If fso. To manipulate binary files. Although we can store data in a database.CreateFolder(strFolder) 2) Create a folder Dim fso. Examples: 1) Create a folder Dim fso. We need to be able to create files. the FSO model does not support binary files. The FSO model.

OpenTextFile("C:\Documents and Settings\gcr.WinEdit("attached text:=Agent Name:").WinEdit("attached text:=Password:"). 2-Write & 8-Append myFile.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.AtEndOfStream myLine=myFile. myField Set objFso=CreateObject("Scripting.exe" Dialog("text:=Login").Click Window("text:=Flight Reservation").1) '1 for Read.FileSystemObject") Set myFile=objFso. '********************************************************* 'Test Requirement: Data Driven Testing by Fetching Test data directly from a Text file.msgbox "Folder already exists" else fso.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.") SystemUtil. 'Author: G C Reddy 'Date of Creation: 13-08-2010 'Pre-requisites: 'vinod.".WinButton("text:=OK").Close .SkipLine Do Until myFile.Activate Dialog("text:=Login").Set myField(0) Dialog("text:=Login"). myFile.Set myField(1) wait 2 Dialog("text:=Login").CreateFolder(strFolder) End If 3) Data Driven Testing by fetching Test data directly from a Text file. myLine.txt".GCRC9A12FBD3D9\Desktop\vindod.ReadLine myField=Split(myLine.

Close Set objFso=Nothing for more Examples visit: File System Scripts File System Scripts 1) Create a Folder Option Explicit Dim objFSO.CreateFolder(strDirectory) 2) Delete a Folder Set oFSO = CreateObject("Scripting.CopyFolder "E:\gcr".DriveLetter Next .FileSystemObject") If objFSO. strDirectory strDirectory = "D:\Gcreddy" Set objFSO = CreateObject("Scripting.FolderExists(strDirectory) Then Set objFolder = objFSO. "C:\jvr". objFolder.Loop myFile. strDirectory strDirectory = "D:\Gcreddy" Set objFSO = CreateObject("Scripting.DeleteFolder("E:\Gcreddy") 3) Copying Folders Set oFSO=createobject("Scripting.Drives For Each oDrive in colDrives MsgBox "Drive letter: " & oDrive. objFolder.CreateFolder(strDirectory) end if 5) Returning a collection of Disk Drives Set oFSO = CreateObject("Scripting.GetFolder(strDirectory) msgbox strDirectory & " already created " else Set objFolder = objFSO.Filesystemobject") oFSO.FileSystemObject") Set colDrives = oFSO.FileSystemObject") Set objFolder = objFSO. True 4) Checking weather the folder available or not. if not creating the folder Option Explicit Dim objFSO.FileSystemObject") oFSO.

1) Do Until objFile.FileSystemObject") Set oDrive = oFSO.GetFolder(strDirectory) Else Set objFile = objFSO.CreateTextFile("E:\Gcreddy.OpenTextFile("E:\Gcreddy.FileSystemObject") Set objFile = objFSO.txt". 1) Do Until objFile.Read(1) msgbox strCharacters Loop 4) Reading Data line by line from a Flat File Set objFSO = CreateObject("Scripting.Readline msgbox strCharacters Loop 5) Reading data from a flat file and using in data driven testing .OpenTextFile("E:\Gcreddy.FileExists(strDirectory & strFile) Then Set objFolder = objFSO.FileSystemObject") Set objFile = objFSO.FileSystemObject") If objFSO.GetDrive("C:") MsgBox "Available space: " & oDrive.FileSystemObject") Set objFile = objFSO.txt" Set objFSO = CreateObject("Scripting.AvailableSpace Flat File Scripts Flat File Scripts 1) Creating a Flat File Set objFSO = CreateObject("Scripting.txt") End if 3) Reading Data character by character from a Flat File Set objFSO = CreateObject("Scripting.txt") 2) Checking weather the File is available or not.6) Getting available space on a Disk Drive Set oFSO = CreateObject("Scripting.AtEndOfStream strCharacters = objFile.CreateTextFile("E:\Gcreddy. if not creating the File strDirectory="E:\" strFile="Gcreddy.txt".AtEndOfStream strCharacters = objFile.

readline s=split (x.Close SET WriteStuff = NOTHING SET myFSO = NOTHING 7) Delete a text file Set objFSO=createobject("Scripting. FilePath2) .filesystemobject") Set myfile= fso. if available delete the File strDirectory="E:\" strFile="gcr.exe".Delete() 8) Checking weather the File is available or not.Close Wend 6) Writing data to a text file Dim Stuff."open" Dialog("Login").txt") txtFilepath.FileExists(strDirectory & strFile) Then Set objFile = objFSO.txt".txt" Set objFSO = CreateObject("Scripting.skipline While myfile.myfile Set fso=createobject("scripting. 8.Getfile(strDirectory & strFile) objFile.Set s(0) Dialog("Login"). myFSO.Click Window("Flight Reservation").1) myfile. True) WriteStuff.FileSystemObject") Set WriteStuff = myFSO.Activate Dialog("Login").txt".WinEdit("Agent Name:").Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a. WriteStuff.WinButton("OK"). f2 f1="e:\Gcreddy1.txt" f2="e:\Gcreddy2.GetFile("E:\gcr.WinEdit("Password:").SetSecure s(1) Dialog("Login").delete () End if 9) Comparing two text files Dim f1.Dim fso.opentextfile ("F:\Gcreddy.OpenTextFile("e:\Gcreddy. ".filesystemobject") Set txtFilepath = objFSO.") SystemUtil.txt" Public Function CompareFiles (FilePath1. dateStamp dateStamp = Date() Stuff = "I am Preparing this script: " &dateStamp Set myFSO = CreateObject("Scripting."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".atendofline <> True x=myfile.FileSystemObject") If objFSO."".WriteLine(Stuff) WriteStuff.

oTxtFile. File1.FileSystemObject") If FS.Close() File2.Size Then CompareFiles = True Exit Function End If Set File1 = FS. oMatches Set oFso = CreateObject("Scripting.Count Set oTxtFile = Nothing : Set oFso = Nothing : Set oRegEx = Nothing msgbox MatchesFound 11) Read a CSV File Using Database Techniques On Error Resume Next Const adOpenStatic = 3 Const adLockOptimistic = 3 Const adCmdText = &H0001 . oRegEx.GetFile(FilePath1). Str2.GetFile(FilePath2). sReadTxt.Execute(sReadTxt) MatchesFound = oMatches.AtEndOfStream = False Str1 = File1.OpenAsTextStream(1.Size <> FS.OpenTextFile(sFileName.GetFile(FilePath1).txt" sString="gcreddy" Const FOR_READING = 1 Dim oFso.GetFile(FilePath2).Pattern = sString oRegEx.Read Str2 = File2. 0) CompareFiles = False Do While File1. FOR_READING) sReadTxt = oTxtFile.Read CompareFiles = StrComp(Str1. 0) If CompareFiles <> 0 Then CompareFiles = True Exit Do End If Loop File1.IgnoreCase = bIgnoreCase oRegEx. 0) Set File2 = FS.ReadAll Set oRegEx = New RegExp oRegEx." End If 10) Counting the number of times a word appears in a file sFileName="E:\gcr.Close() End Function Call Comparefiles(f1.Global = True Set oMatches = oRegEx.OpenAsTextStream(1." Else MsgBox "Files are different. File2 Set FS = CreateObject("Scripting. f2) = False Then MsgBox "Files are identical.f2) If CompareFiles(f1.Dim FS.FileSystemObject") Set oTxtFile = oFso.

FileSystemObject") Set objTextFile = objFSO.4.AtEndOfStream strNextLine = objTextFile.0.OpenTextFile _ ("e:\gcreddy.MoveNext Loop 12) Read a Text File into an Array Const ForReading = 1 Set objFSO = CreateObject("Scripting.Item("Name") Wscript." & _ "Extended Properties=""text. ".Connection") Set objRecordSet = CreateObject("ADODB." & _ "Data Source=" & strPathtoTextFile & ".FileSystemObject") x= objFso.GetFile(File1).Open "SELECT * FROM PhoneList.FMT=Delimited""" objRecordset.Echo "Server name: " & arrServiceList(0) For i = 1 to Ubound(arrServiceList) Wscript.Fields. File1.Set objConnection = CreateObject("ADODB. adLockOptimistic.Open "Provider=Microsoft.Echo "Department: " & _ objRecordset.txt".Size Msgbox x& " Bytes" 14) 'Test Requirement: Open 1 to 10 orders in Flight Reservation .File2 File1="C:\Documents and Settings\1 RIGHATWAY\Desktop\xyz.Echo "Service: " & arrServiceList(i) Next Loop 13) 'Calculate size of a Text file Dim objFso.csv".Item("Extension") objRecordset.EOF Wscript.txt" Set objFso=CreateObject(" Scripting.Echo "Extension: " & objRecordset. ForReading) Do Until objTextFile.Jet.Echo "Name: " & objRecordset. _ objConnection.OLEDB. Capture Customer names and Export into a Text file 'Test Flow: 'Login Operation 'Open Order Operation and form the Loop to open 1 to 10 Orders .HDR=YES. adOpenStatic.") Wscript.Fields.Item("Department") Wscript.Fields.Readline arrServiceList = Split(strNextLine .Recordset") strPathtoTextFile = "C:\Databases\" objConnection. adCmdText Do Until objRecordset.

Click Customer_Name = Window("Flight Reservation").CreateTextFile ("C:\Documents and Settings\1 RIGHATWAY\Desktop\abcNew.WriteLine Customer_Name Next myFile.Dialog("Open Order"). Customer_Name.FileSystemObject") Set myFile= objFso. objFso.WinEdit("Agent Name:").Dialog("Open Order")."open" Dialog("Login").Click Window("Flight Reservation").WinEdit("Name:").WinButton("OK").WinCheckBox("Order No.WinButton("Button").WinEdit("Password:").SetSecure "4c48590870466b8dc050bbd24e816890c747ccf8" Dialog("Login").'Capture Cusomer names using GetROProperty Method 'Create File system Object and Open the Text file using the Object and Export Cusomer names '---------------------------------------------------------------------------Option Explicit Dim Order_Number.Activate Window("Flight Reservation").Close Set objFso=Nothing .WriteLine "--------------------" If Not Window("Flight Reservation").Exist(3) Then SystemUtil."". myFile Set objFso=CreateObject("Scripting.txt".Set Order_Number Window("Flight Reservation").Dialog("Open Order").GetROProperty("text") wait (2) myFile.Set "asdf" Dialog("Login").Click End If For Order_Number= 1 to 10 step 1 Window("Flight Reservation").Set "ON" Window("Flight Reservation").").exe".Activate Dialog("Login").WinEdit("Edit").2) myFile.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a."C:\Program Files\HP\QuickTest Professional\samples\flight\app\".WinButton("OK").WriteLine "Cusomer Names" myFile.

Server=Your_Server_Name.Initial Catalog= Your_Database_Name.Data Source=Your_Server_Name." Trusted connection: "Driver={SQLServer}.Database=Your_Database_Name.UserId=Your_Username.Initial .Pwd=Your_Password. whether on the same machine or not.Server=Your_Server_Name.Trusted_Connection =yes." Trusted connection: "Provider=SQLOLEDB.Data Source=Your_Server_Name.Password=Your_Password.Uid=Your_Usernam e. SQL Server connection strings SQL ODBC connection strings Standard Security: "Driver={SQLServer}.Database connections Database connections Database connection is a facility in computer science that allows client software to communicate with database server software." SQL OLE DB connection strings Standard Security: "Provider=SQLOLEDB.Database=Your_Database_Name.

mdb)}.Integrated Security=SSPI.mdw.Database=Your_Database_Name. Uid=Your_Username." < br>2.4." MS Access OLE DB & OleDbConnection (.mdb.mdb)}.Initial Catalog=Your_Database_Name.0.Password=Your_Password.mdw" Open connection to password protected Access database: "Provider=Microsoft." Exclusive "Driver={Microsoft Access Driver (*. Password=" Open connection to Access database using Workgroup (System database): "Provider=Microsoft." Trusted connection: "Provider=SQLOLEDB. Remote Provider=Microsoft.0.NET framework) connection strings Open connection to Access database: "Provider=Microsoft.Jet.UserId=Your_Username.4.Password=Your _Password.4.mdb.mdb" .0.Jet.OLEDB. Data Source=c:\App1\Your_Database_Name.Jet.OLEDB." MS Access connection strings MS Access ODBC connection strings Standard Security: "Driver= {MicrosoftAccessDriver(*." 2. Data Source=c:\App1\Your_Database_Name.Jet.Trusted_Connection=False" Trusted connection: 1.Integrated Security=SSPI.mdb.OLEDB.Data Source=Your_Server_Name. "Data Source=Your_Server_Name.Integrated Security=SSPI.OLEDB.UserId=Your_Username.0.Initial Catalog= Your_Database_Name. SystemDB=C:\App1\Your_Database_Name.mdb)}.UserID=Your_Username.0.OLEDB.mdb" Open connection to Access database located on a remote server: "Provider=MS Remote." SQL SqlConnection .Uid=Your_Username." SQL OleDbConnection ."Server=Your_Server_Name.DBQ=C:\App1\Your_Database_Name.mdb.Trusted_Connection=True.Jet.Data Source=Your_Server_Name.Initial Catalog=Your_Database_Name. Jet OLEDB:System Database=c:\App1\Your_System_Database_Name.Password=Your_Password.Initial Catalog= Your_Database_Name. Data Source=\\Server_Name\Share_Name\Share_Path\Your_Database_Name." Workgroup: "Driver={Microsoft Access Driver (*.Database=Your_Database_Name.mdb.mdb. Remote Server=http://Your-Remote-Server-IP. "Data Source=Your_Server_Name. Dbq=C:\App1\Your_Database_Name. User Id=admin. Jet OLEDB:Database Password=Your_Password" Open connection to Access database located on a network share: "Provider=Microsoft. Data Source=c:\App1\Your_Database_Name. Data Source=c:\App1\Your_Database_Name.Catalog=Your_Database_Name. Pwd=Your_Password.4.4. DBQ=C:\App1\Your_Database_Name. "Server=Your_Server_Name. Exclusive=1.Pwd=Y our_Password.NET strings Standard Security: "Provider=SQLOLEDB.NET strings Standard Security: 1.

UserId=Your_Username. DRIVER={MySQL ODBC 3. Password=Your_Password.Password=Your_Password.User Id=Your_Username." Open trusted connection to Oracle database "Provider= OraOLEDB.NET framework) connection strings Open connection to MySQL database: "Provider=MySQLProv.Your_Oracle_Database. OPTION=3" MySQL OLE DB & OleDbConnection (.UserId=Your_Username.Password=Your_Password.NET framework) connection strings Open connection to Oracle database with standard security: 1. PASSWORD=Your_Password. "Provider= OraOLEDB.world. SERVER= localhost. DATABASE=Your_MySQL_Database.51Driver}.Server=Your_Oracle_Server.Data Source= Your_Oracle_Database.Oracle.MySQL connection strings MySQL ODBC connection strings Open connection to local MySQL database using MySQL ODBC 3.DataSource=Your_Oracle_Database.OSAuthent=1.Pwd=Your_Password." ." 2." Oracle connection strings Oracle ODBC connection strings Open connection to Oracle database using ODBC "Driver= {Microsoft ODBCforOracle}.Uid=Your_Username.Oracle. "Provider=MSDAORA." Oracle OLE DB & OleDbConnection (.Data Source=Your_MySQL_Database.51 Driver "Provider=MSDASQL. UID= Your_Username.

Automation Object Model 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. We can use Scripting languages or programming languages such as VBscript. that automate our QTP operations. Java script or VC++. . and their relationships. An object model defines a set of classes and interfaces. QTP Automation object model provides objects. together with their properties. methods and events. Example: .Net for automating QTP operations. We can use QTP Automation object Model to write scripts. methods and properties that enable us to control QTP from another application.

To do this.Remove(position) Syntax for Removing All Repositories: RepositoriesCollection. Using this feature we can increase QTP performance.open "C:\Documents and Settings\admin\My Documents\login" Set qtTest=qtApp.Test qtTest. Syntax for Loading a Repository: RepositoriesCollection.Add “Path of the Repository File” Syntax for finding Position of the Repository: Variable=RepositoriesCollection.Launch qtApp.close qtApp. Dynamic Handling of Object Repositories Dynamic handling of object Repositories Loading repositories during running.Find(“Path of the Repository”) Syntax for Removing the Repository: RepositoriesCollection.qtTest Set qtApp=createobject ("Quicktest.close qtApp.visible=True qtApp.RemoveAll .Application") qtApp. finding path of the repositories and removing repositories is called Dynamic Handling of Object Repositories. QTP is providing an object called “RepositoriesCollection”.open "C:\Documents and Settings\admin\My Documents\open order" Set qtTest=qtApp.option explicit Dim qtApp.Test qtTest.run qtTest.quit Note: AOM Script can be used in Automation framework as an Initialization script.run qtTest.

exe" Dialog("Login").Set "mercury" Dialog("Login").Activate Dialog("Login").Click pos=RepositoriesCollection.WinEdit("Password:").Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a. .Find(RepPath) RepositoriesCollection.Set "sudhakar" Dialog("Login").RemoveAll *********************************** Go to home page for QTP Guide.Add (RepPath) systemutil.Remove(pos) RepositoriesCollection.WinButton("OK").tsr" RepositoriesCollection.Example: RepPath="C:\Documents and Settings\Administrator\My Documents\Login. Script examples. Interview questions and Framework etc.WinEdit("Agent Name:").

Sign up to vote on this title
UsefulNot useful