QTP Guide

QTP GuideQTP 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: 3)Lack of expertisation.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. 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. Attributes) Load and Stress Testing Which Software Testing should not be automated? Usability Testing One time testing .U. Object models from QTP.S. Excel. (Keyword Driven Approach means. (Object based means.. (QTP basically depends on User Interface to automate test operations and it is not depends on server side interactions. Later taken over by HP.Quick look Tests or A. By Mercury Interactive. does not support CUI (Command user interface) Applications. Keywords. functions. where as LoadRunner depends on server side Operations. QTP Basic Features • • QTP Launched in 2002 (Nov). Japanese. (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. example: Commands. (It supports English. QTP is an Object Based Testing Tool. in 2007. statements etc.) • It has adapted Microsoft Visual Basic Scripting edition for programming and Excel like spread sheet for Data driven testing. . QTP Follows Test Object Model for Performing Testing operations. • It has multilingual support. are used for creating Test scripts) • It supports Windows Operating Environment only.A. methods. Chinese. so HP developed LoadRunner for Windows as well as UNIX versions) • It supports GUI based (Graphical user interface) and Web based Applications Automation. Based on either Test Objects or Automation Objects or Utility Objects only. Tools support for QTP: -----------------------------• VB Script for Scripting (for implementing programming logic) • VB Script engine integrated in QTP.P (As soon as possible) Testing Ad-hoc testing / Random Testing Customers requirement are frequently changing. we can automate test operations) (LoadRunner is a Protocol based Test Tool) • QTP is for Functional and Regression Testing. so apart from scripting features we can use File system. Adodb etc. word. Korean. etc languages with respect to license. for execution it supports other browsers like Mozilla and AOL.5 – 2003 • 8. • QTP has UNI code support.0 – 2004 • 8. If we want multiple concurrent licenses we can purchase.3 –2005 • 9.1-2006 • 9. Version History of QuickTest Professional • Astra QuickTest (Mother tool of QTP) 1. Environment variables and for exporting object repositories. 8.• SQL (Structured query language) engine integrated in QTP.0.2. • 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. Concurrent or float license. • It supports IE (Internet Explorer) only for recording tests.NET Technology. QTP has two types of License. • • QTP is a Desktop Application (I-Tier/Stand alone).6 – Nov 2002 • 6. • QTP uses XML format for Test results. we can use for any system but one user at any time. ------------------------------------------------------• QTP can be integrated with other Tools like WinRunner and Quality Center. • Seat license for one system and Concurrent License.2. 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.0 to 5.9. • It was derived from Astra QuickTest (mother tool of QTP).0 Quick Test Professional • 5. • • Seat or Node locked License. opera Etc apart from IE.2007 Mercury Interactive . QTP developed in . P • 10...5...• 9.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.5 –2008 H.0) .. -----------------------------------------------------------------------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.0. Test Batch Runner.0.. SQL Engine. 9..0 2004 8.6 2002 (Nov) 6.5. 3) Integrated Tools (Others) Ex: Spread sheet. Test Result Dletion Tool etc.5 2003 8. VB Script Engine.. Object Repository etc.0 2009 (Jan) c) QTP License(Seat/Node Locked and Concurent/Float) c) QTP IDE 1) QTP Features Ex: Recording.2 2005 9. 2) Integrated Tools (HP) Ex: Password Encoder.1 2006 9.2 2007 9. Checkpoints.5 2008--------HP 10. 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 . 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 toolbar.NET Windows Forms list.NET Windows Forms TreeView control.NET Windows Forms static text object. SwfScrollBar A . SwfTab A . SwfList A . WpfComboBox A combo box control in a Windows Presentation Foundation application.NET Windows Forms multi-line edit box. WpfImage An image control in a Windows Presentation Foundation application.NET Windows Forms edit box. WpfCheckBox A check box control in a Windows Presentation Foundation application. WpfEdit A document.NET Windows Forms radio button. SwfStatusBar A .NET Windows Forms ListView control.NET Windows Forms object. SwfRadioButton A . SwfTable A grid control based on the . SwfListView A . SwfObject A standard . SwfSpin A . or text control in a Windows Presentation Foundation application.NET Windows Forms status bar control. SwfToolBar A . SwfPropertyGrid A property grid control based on the .NET Windows Forms library. WpfLink A hyperlink control in a Windows Presentation Foundation application. SwfTreeView A .NET Windows Forms tab control. SwfWindow A .SwfEdit A .NET Windows Forms library.NET Windows Forms window. SwfLabel A . SwfEditor A . WpfList A list control in a Windows Presentation Foundation application. WpfGrid A grid control in a Windows Presentation Foundation application.NET Windows Forms spin object. rich text box. VI) Windows Presentation Foundation Environment Object Description WpfButton A button control in a Windows Presentation Foundation application. .NET Windows Forms scroll bar. WpfProgressBar A progress bar control in a Windows Presentation Foundation application. WpfScrollBar A scroll bar control in a Windows Presentation Foundation application. WpfWindow A window control in a Windows Presentation Foundation application. WpfStatusBar A status bar control in a Windows Presentation Foundation application. WpfObject An object control in a Windows Presentation Foundation application. OracleStatusLine .WpfMenu A menu control in a Windows Presentation Foundation application. WpfRadioButton A radio button control in a Windows Presentation Foundation application. WpfSlider A slider control in a Windows Presentation Foundation application. OracleLogon An Oracle Applications sign-on window. OracleList An Oracle poplist (combo box) or list. OracleRadioGroup An Oracle option (radio button) group. OracleCalendar An Oracle calendar. WpfToolbar A toolbar control in a Windows Presentation Foundation application. OracleNotification An Oracle error or message window. WpfTreeView A tree control in a Windows Presentation Foundation application. OracleCheckbox A check box Oracle field. WpfTabStrip A tab control in a Windows Presentation Foundation application. OracleButton An Oracle button. OracleFlexWindow An Oracle flexfield window. OracleListOfValues An Oracle window containing a list of values for selection. OracleNavigator An Oracle Navigator window. OracleFormWindow An Oracle Form window. VII) Oracle Environment Object Description OracleApplications An Oracle Applications session window. OracleTable An Oracle block of records. VIII) PeopleSoft Environment Object Description PSFrame A frame object within a PeopleSoft application. PbEdit A PowerBuilder edit box. X) SAP Web Environment Object Description SAPButton An SAP Gui for HTML application button. buttons with text. toolbar buttons. PbDataWindow A PowerBuilder DataWindow control. regular buttons. OracleTabbedRegion An Oracle tabbed region. PbObject A standard PowerBuilder object. PbListView A PowerBuilder listview control. including icons. OracleTree An Oracle tree. PbTabStrip A PowerBuilder tab strip control PbTreeView A PowerBuilder tree-view control. PbComboBox A PowerBuilder combo box.The status line and message line at the bottom of an Oracle Applications window. OracleTextField An Oracle text field. PbCheckBox A PowerBuilder check box. PbRadioButton A PowerBuilder radio button. and buttons with text and image. IX) PowerBuilder Environment Object Description PbButton A PowerBuilder button. PbList A PowerBuilder list. SAPCalendar . PbScrollBar A PowerBuilder scroll bar. PbWindow A PowerBuilder window. SAPRadioGroup An SAP Gui for HTML application radio button group. SAPStatusBar An SAP Gui for HTML application status bar. SAPPortal An SAP Enterprise Portal desktop. including single-line edit boxes and multi-line edit boxes (text area). SAPiView An SAP Enterprise Portal application iView frame. SAPDropDownMenu A menu that is opened by clicking a menu icon within an SAP Gui for HTML application. SAPEdit An SAP Gui for HTML application edit box. SAPTreeView An SAP Gui for HTML application tree object. SAPOKCode An OK Code box in an SAP Gui for HTML application. SAPGuiGrid A grid control in an SAP GUI for Windows application. SAPGuiElement Any object in an SAP GUI for Windows application. including check boxes and toggle images. SAPGuiCheckBox A check box in an SAP GUI for Windows application. SAPFrame An SAP Gui for HTML application frame. SAPMenu An SAP Gui for HTML application top-level menu. SAPTable An SAP Gui for HTML application table or grid. XI) SAP GUI for Windows Environment Object Description SAPGuiAPOGrid An APO grid control in an SAP GUI for Windows application. SAPGuiComboBox A combo box in an SAP GUI for Windows application. SAPGuiEdit An edit box in an SAP GUI for Windows application. SAPGuiCalendar A calendar object in an SAP GUI for Windows application. . SAPGuiButton A button 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). SAPNavigationBar A navigation bar in a Web-based SAP application. SAPList A drop-down or single/multiple selection list in an SAP Gui for HTML application.A calendar in a Web-based SAP application. SAPCheckBox An SAP Gui for HTML application toggle button. SAPGuiRadioButton A radio button in an SAP GUI for Windows application. SiebApplet An applet in a Siebel test automation environment.SAPGuiLabel A static text label in an SAP GUI for Windows application. SAPGuiTable A table control in an SAP GUI for Windows application. SblTable A Siebel table containing a variable number of rows and columns. SAPGuiOKCode An OK Code box in an SAP GUI for Windows application. SAPGuiTabStrip A tab strip in an SAP GUI for Windows application. SAPGuiToolbar A toolbar in an SAP GUI for Windows application. SAPGuiSession Represents the SAP GUI for Windows session on which an operation is performed. SblTreeView A tree view of specific screen data. . list tree. SAPGuiMenubar A menu bar in an SAP GUI for Windows application. SblPickList A drop-down pick list. SblEdit An edit box. XII) Siebel Environment Object Description SblAdvancedEdit An edit box whose value can be set by a dynamic object that opens after clicking on a button inside the edit box SblButton A Siebel button. SblCheckBox A check box with an ON and OFF state. or simple tree control in an SAP GUI for Windows application. SAPGuiTree A column tree. SiebApplication An application in a Siebel test automation environment. SiebButton A button control in a Siebel test automation environment. SAPGuiWindow A window or dialog box containing objects 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. SAPGuiUtil A utility object in an SAP GUI for Windows application. SAPGuiTextArea A text area in an SAP GUI for Windows application. SAPGuiStatusBar A status bar in an SAP GUI for Windows application. SiebScreen A screen object in a Siebel test automation environment. SiebMenu A menu or menu item in a Siebel test automation environment. SiebTaskAssistant The Task Assistant in a Siebel test automation environment. SiebCurrency A currency calculator in a Siebel test automation environment. SiebTextArea A text area in a Siebel test automation environment. SiebRichText A rich text control in a Siebel test automation environment. SiebPDQ A predefined query in a Siebel test automation environment. SiebTaskUIPane The task UI pane in a Siebel test automation environment. SiebCommunicationsToolbar The communications toolbar in a Siebel test automation environment. Dialog A Windows dialog box. SiebToolbar A toolbar in a Siebel test automation environment. SiebList A list object in a Siebel test automation environment. SiebPageTabs A page tab in a Siebel test automation environment. SiebText A text box in a Siebel test automation environment. SiebScreenViews A screen view in a Siebel test automation environment. SiebCalendar A calendar control in a Siebel test automation environment. SiebViewApplets A view applet in a Siebel test automation environment. XIII) Standard Windows Environment Object Description Desktop An object that enables you to access top-level items on your desktop. SiebCheckbox A checkbox in a Siebel test automation environment. SiebThreadbar A threadbar in a Siebel test automation environment. SiebPicklist A pick list in a Siebel test automation environment. SiebView A view object in a Siebel test automation environment. Static . SiebTree A tree view object in a Siebel test automation environment.SiebCalculator A calculator control in a Siebel test automation environment. WinSpin A Windows spin box. . WinToolbar A Windows toolbar. WinStatusBar A Windows status bar. WinEdit A Windows edit box. WinObject A standard (Windows) object. WinEditor A Windows multi-line editor. WinComboBox A Windows combo box. WinList A Windows list. WinTreeView A Stingray tree control. WinTable A Stingray grid. WinButton A Windows button. WinMenu A Windows menu. XIV) Stingray Environment Object Description WinTab A Windows tab strip in a dialog box. Window A standard window. WinRadioButton A Windows radio button. WinScrollBar A Windows scroll bar. WinListView A Windows list-view control. WinTreeView A Windows tree-view control. WinCalendar A Windows calendar. WinCheckBox A Windows check box.A static text object. WinTab A Windows tab strip in a dialog box. WinToolbar A Windows toolbar. SystemUtil An object used to control applications and processes during a run session. TeScreen A terminal emulator screen that fully supports HLLAPI.XV) Terminal Emulators Environment Object Description TeField A terminal emulator field that fully supports HLLAPI. WinEdit An edit box in the VisualAge Smalltalk application. VbList A Visual Basic list. VbWindow A Visual Basic window. VbListView A Visual Basic list-view control. . VbToolbar A Visual Basic toolbar. XVII) VisualAge Smalltalk Environment Object Description WinButton A button in the VisualAge Smalltalk application. VbEditor A Visual Basic multi-line editor. VbLabel A static text object. XVI) Visual Basic Environment Object Description VbButton A Visual Basic button. VbFrame A Visual Basic frame. VbTreeView A Visual Basic tree-view control. WinList A list in the VisualAge Smalltalk application. VbEdit A Visual Basic edit box. VbRadioButton A Visual Basic radio button. VbScrollBar A Visual Basic scroll bar. VbCheckBox A Visual Basic check box. TeWindow A terminal emulator window. TeTextScreen A terminal emulator screen that uses text-only HLLAPI or does not support HLLAPI. VbComboBox A Visual Basic combo box. XIX) Web Services Environment Object Description Attachments An object that supports attachment-related operations ----------------------------------------------------------------------------------------Configuration An object that supports configuration-related operations ----------------------------------------------------------------------------------------headers . usually contained inside a form. WebElement A general Web object that can represent any Web object. WebXML An XML document contained in a Web page. Page An HTML page. Frame An HTML frame. used to select a file from the File dialog box. WebFile An edit box with a browse button attached. WebList A drop-down box or multiple selection list. WebButton An HTML button. WinTreeView A tree-view control in the VisualAge Smalltalk application. XVIII) Web Environment Object Description Browser A Web browser (or browser tab). WebEdit An edit box. WinTab A tab strip in the VisualAge Smalltalk application. WebRadioGroup A set of radio buttons belonging to the same group. WebCheckBox A check box with an ON and OFF state. Link A hypertext link.WinObject An object in the VisualAge Smalltalk application. WebArea A section of an image (usually a section of a client-side image map). ViewLink A Viewlink object. WebTable A table containing a variable number of rows and columns. Image An image with or without a target URL link. WinTable A table in the VisualAge Smalltalk application. WebService A test object representing a Web service. WSUtil A utility object used to check WSDL files. Test: It is a set of statements or set of one or more actions. statement etc). QTP Tool Window Key Elements of QTP Tool Window 1) Test Pane: It is programming interface of QTP.An object that supports header-related test object operations. Statements may have keywords. (It is a local concept) Action: It is a set of Statements. (Keyword such as function. Security An object that supports security-related test object operations. . editing. used for creating. (It is a local concept) Statement: A minimal executable unit. viewing and deleting test scripts. It is a global concept. method. Note 3: User can customize Test pane view options. Expert view.Test in VB script format. Note1: Here in test pane Test is same but views are different.Test pane has 2 views. Navigation: View menu>active screen (for launching and closing) . 2) Active Screen It has an optional element of QTP.Test in Icon based GUI format. Key word view. It can be used for understanding and editing the test easily. it takes snap shots of every statement that user performed action or operation on AUT. if you perform any modifications in one view those automatically reflects in another view. Note 2: Technical users use expert view and business user use key word view. Navigation: Tools Menu> view options> we can use font size and colors etc. apply and okay. used for Data driven testing. 3) Data Table It has an integrated spread sheet (Excel like).Configuring Active Screen: view>options>active screen tab>increase /Decrease capture level. Note 1: Generally novice testers use this feature but it occupies lot of memory space on QTP. Navigation: View menu>Data table (for launching and closing) . etc) and Data bases (MS access. Sql Server. 2). Run time data table.for entire Test /used for all actions in the Test. 1). oracle.) It has two types of sheets. Step over and Step out commands for debugging. It can be used for debugging the tests by step-by-step execution. Design time data table. (Attached with every test) 2). excel sheets. We use Step into. QTP has Data table methods for performing operations on data table. Data table available in 2 ways: 1). It can be used in two ways. (debug commands) Navigation: View menu>debug viewer (for launching and closing) . Importing data from external files (Flat files. 2. Enter test data directly into Data Table and use. Global Sheet. 4) Debug Viewer It is used for locating and rectifying or fixing errors. Action Sheets. etc. 1.for specific Action only. (Available in result window) Run time is a carbon copy of design time data table.Data driven Testing: Testing the same task(S) or same operation with multiple sets of test data. Library files etc).Through Debug viewer user can watch variables and change values of variables temporarily. Navigation: view menu> information . Navigation: View menu >missing resources (for launching and closing) 6) Information This pane shows syntax errors automatically during saving the test. 5) Missing Resources It can be used for showing missing resources that attached to current test such as (Recovery Scenarios. open existing tests. save tests. export tests in zip format. Tool Bar options 3). . Short cut keys (for Some important operations only) QTP Tool Window Menus File menu: Through file menu user can create. 1). Menu options 2).7) QTP Commands QTP Commands are available in 3 ways. call existing actions and copy existing actions.Edit Menu: It provides editing options and renaming. Tools Menu: This menu provides Tools settings option. Debug Menu: This menu provides debug commands for step by step execution. 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 this menu we can set tool options as well as test pane view options. modify and delete recovery scenarios. Through this menu we can stop recoding. Through this menu we can create /modify/delete objects information and we can associate repositories. through this option we can create virtual objects. information. missing resources etc. Through this menu we can create. Automation Menu: This menu provides Record. Window Menu: This menu provides QTP tool window style settings. . Run options and Run setting options Through this menu we can start normal recording. active screen. running and also we run tests. In this menu object spy option available. Data Table. Through insert menu user can create new actions. Help Menu: This menu provides QTP help as well as VB Script help. In this menu step generator available. (Properties and values) In this menu Virtual object option available. View menu: Through this menu we can launch and close. Resources Menu: This menu provides object repository and recovery scenarios options. synchronizing points. analog recording and Low level recording. out put values. Through this menu we can insert/remove/break points. view options and object identification configuration. deleting and splitting actions. through this we can get object’s information. Debug viewer. Insert Menu: Through this menu user can inserting check points. .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. 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. open existing tests. export tests in zip format. Opens an existing business or scripted component. Creates a new application area. Creates a new business component. Opens an existing test.QTP Commands QTP Commands QTP Commands are available in 3 ways. 1.Short cut keys (for Some important operations only) File menu: Through file menu user can create. save tests.Tool Bar options 3. . Creates a new function library. Creates a new scripted component.Menu options 2. Saves all open documents. Makes read-only function libraries editable. Opens an existing function library. . Opens the relevant Save dialog box so you can save the open document.Open > Application Area Open > Function Library Close Close All Function Libraries Quality Center Connection Opens an existing application area. Save Save As Saves the active document. Opens the Quality Center Connection dialog box. Saves a standalone copy of the current test together with its resource files. Quality Center Version Provides a sub-menu of options for Control managing versions of QuickTest assets in Quality Center. enabling you to connect to a Quality Center project. The sub-menu is available only when you are connected to version-control enabled Quality Center project. Save Test with Resources Save All Enable Editing Export Test to Zip File Creates a zip file of the active document. Import Test from Zip File Imports a document from a zip file. Closes all open function libraries. Closes the active function library. . 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. deleting and splitting actions. Closes the QuickTest session. 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. Prints the active document. Edit Menu: It provides editing options and renaming. enabling you to manage the list of processes that are available in QuickTest. (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. enabling you to define settings for the open document. or delete the action and its calls from the active test. Pastes the selection to your document. parameters. enabling you to paste it in an external application. Changes the name of an action. and to define the values of input parameters and the storage location of output parameters. Copies the content of the Documentation column of the Keyword View. Copies the selection from your document. Removes the selection from your document. Deletes the selection from your document. Available only when the selected step is a comment. Enables you to specify the number of run iterations according to the number of rows in the Data Table. Opens the Object Properties dialog box for a Action > Action Call Properties Step Properties > Comment Properties Step Properties > . Opens the Comment Properties dialog box for a comment step. 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.Redo Reverses the most recent operation of the Undo command. and associated object repositories for a stored action. Separates an action into two sibling actions or into parent-child nested actions. Action > Action Properties Enables you to specify options. Indents the step according to the tab spacing defined in the Editor Options dialog box. Available only when the selected step is a Reporter. Searches and replaces a specified string. Advanced > Uncomment Block Advanced > Indent Removes the comment formatting from the current or selected rows. Searches for a specified string. Moves the cursor to a particular line in the test.ReportEvent step. Available only when the selected step is an output value step. 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. Displays the Report Properties dialog box for a report step. Advanced > Outdent . Available only when the selected step contains a test object.Object Properties selected object. Available only when the selected step is a checkpoint step. or selected Block rows. Creates bookmarks in your script for easy navigation. Step Properties > Opens the relevant Checkpoint Properties Checkpoint Properties dialog box for a selected object. Outdents the step (reduces the indentation) according to the tab spacing defined in the Editor Options dialog box. Advanced > Go to Function Definition Navigates to the definition of the selected function. Advanced > Complete 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 Command Options Function Opens the Options dialog box. In this menu object spy option available. through this we can get object’s information. Tools Menu: This menu provides Tools settings option. Lists the function libraries associated with the active document. through this option we can create virtual objects. Opens the Recovery Scenario Manager dialog box. enabling you to modify global testing options. View Options Check Syntax . enabling you to map repository parameters. enabling you to customize how tests and function libraries are displayed in the Expert View and Function Library windows. Through this menu we can insert/remove/break points. Opens the Editor Options dialog box. (Properties and values) In this menu Virtual object option available.Map Repository Parameters Opens the Map Repository Parameters dialog box. Recovery Scenario Manager Associated Function Libraries Debug Menu: This menu provides debug commands for step by step execution. view options and object identification configuration. Through this menu we can set tool options as well as test pane view options. as needed. enabling you to open them. Checks the syntax of the active document. as well as the test object hierarchy. Opens the Virtual object Manager.Object Identification Opens the Object Identification dialog box. which displays the default Constants list for the action. (Relevant for tests only) Opens the Data Driver dialog box. and create new menus. 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. 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. Object Spy Opens the Object Spy dialog box. (Relevant for tests only) Replaces the previously recorded Active Screen with the selected Active Screen. enabling you to specify a recording configuration level. enabling you to manage all of the virtual object collections defined on your computer. identification properties. . and operations of the test object that QuickTest uses to represent that object. Opens the Customize dialog box. (Relevant for tests only) Opens the Virtual Object Wizard. Opens the Web Event Recording Configuration dialog box. which enables you to customize toolbars and menus. enabling you to teach QuickTest to recognize an area of your application as a standard test object. Through this menu we can check for updates and download or install directly.Help Menu: This menu provides QTP help as well as VB Script help. Through this menu we can contact technical support people and we can send feedback. 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 . 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)."http://www. Simultaneously it adds Objects information into Object Repository.Link("Gmail"). y.icicibank.Set "gcreddy" Ex2: Browser("Google"). .Run "C:\Program Files\Internet Explorer\IEXPLORE. and generates them in a script in the Expert view.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.Page("Google"). Price ii) Object calls Ex1: Dialog("Login"). z Const City.EXE". During Recording QTP Creates steps in Keyword view.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".Dim x.exe" **It launche the Application Ex2: SystemUtil."mercury") vi) Utility Statements Ex1: SystemUtil.WinEdit("Agent Name:"). Record and Run only on) If we select first option it records on any opened application on Desktop. paints etc.Stop recording. 8.Perform actions on AUT 7. graphs. based on that Information performs operations on AUT. Navigation: 1.It shows Record and Run Settings. Navigation: Automation>Record Or Select Record option on automation toolbar Or Use short cut key (F3) Steps for preparing a Test (through Recording): 1. 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. The Track file is not editable. After Providing the path it records only on that particular application. Simultaneously it stores objects information into object repository.) 5.Record and Run Test on any open window based applications 2. 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.Put AUT in base state 2.Select Record Option (It shows two Options : 1. generates total user actions in a Track File.Click OK 6.Save the Test ii) Analog Recording: It records the exact mouse and keyboard operations.Select Record Option 3.Keep tool under recording mode . We can use this mode for recording continuous mouse operations. If we select Second option.b) Running /Execution Process During Running QTP reads statements one by one and gets Object Information from the Object Repository. it asks for the path of the AUT. During recording QTP generates VbScript statements in Test Pane. but unable to record continuous mouse operations like Digital Signatures. Automation>Analog Recording 4. we have to show the window (AUT).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).Stop Recording iii) Low Level Recording It records some operations on Non-supported environments apart from Normal operations. Navigation: 1.) 5. Use Low Level Recording for recording in an environment not recognized by QTP.2. after showing the Window it records with respect to that window co-ordinates.Record relative to the following window) (If we select first option QTP records User operations with respect to Desktop co-ordinates.Analog Recording Settings Dialog box opens (In this Dialog box two options available.Automation >Analog Recording OR Use Short cut Key (Shift + ALT+F3) Steps for preparing a Test (through Analog Recording): 1. If we select Second option.It records User actions 7. 1. This mode records at the object level and records all run time objects as window or winobject Test objects. 6.Keep tool under recording mode 2.Launch AUT (or we can launch AUT through QTP) 2.Select any one option in the dialog box and click Start Analog record.Record relative to the screen 2. So QTP reduced performance will be • No Centralized Maintenance mechanism . So Modifications are very difficult .Select Record option 3. • User may not have command on the Recorded script. Additionally. our tests become more modular. it is possible to begin preparing our . So locating errors is difficult • Recorded scripts are QTP internal files. because it is possible to add objects to the object repository before they exist in an application. focusing on the operations to test using both QuickTest built-in keywords and your own user-defined keywords. they may corrupt. e) Advantages of Recording/ Where Applicable • It is used for Analyzing the AUT in the initial stage to find out weather the QTP tool is Recognizing all of our Application Objects or not • It is easy to create Tests / Test Scripts •It is used for frequently changing UI (User Interface) • It takes less time to create Tests Keyword Driven Methodology Keyword-Driven Methodology By creating our tests with a keyword-driven methodology in mind. We can create object repositories using QuickTest functionality to recognize and learn the objects in your application. Configuring QuickTest According to our Testing Needs After we set up the test automation infrastructure. This helps make both test creation and maintenance easier over time. We instruct QuickTest to learn the objects in our application according to filters that we define. Building our Tests We can create tests that are as simple or complex as needed. we can use the same object repository in multiple tests. Add (learn) objects from our application. 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. Setting up Object Repositories In this step. 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. By creating and populating shared object repositories that can be associated with multiple actions. In general. We may perform the following tasks when creating tests and test steps: .automated keyword-driven tests even before a software build containing the new objects is available. or we can manually define objects. we need to configure QuickTest to use this infrastructure: Define your global testing preferences. We need to specify configuration settings that affect how we create and run tests in general—these settings are not test-specific. 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. 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. 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. Associate our function libraries with the relevant tests. if needed. Create the required actions. select File > New > Test. and a set of relevant operations that QuickTest can perform on the object.Create new tests. Associate our object repositories with the relevant actions This enables us to insert steps that perform operations on those objects. . . A run-time object is the actual object in your application on which methods are performed during the run session. we can add test objects to an object repository in several ways. and so on). The native property set for each run-time object is created and maintained by the object creator (for example. Native operations are the methods of the object in your application as defined by the object creator. QuickTest performs the specified test object operation on the run-time object. You can also use regular expressions to identify property values based on conditions or patterns you define. You may need to modify the identification property values to match the native property values. or you can parameterize property values with Data Table parameters so that a different value is used during each iteration of the test. Similarly. • 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. a test object operation is a method or property that QuickTest recognizes as applicable to a particular test object class. QuickTest stores information on the object that will help it identify and check the object during the run session. For more information. • Chooses a unique name for the test object. You can view or modify the identification property values that are stored with your test in the Object Properties or Object Repository dialog box. As you add steps to your test. it adds the corresponding test object to an object repository.A test object is an object that QuickTest creates in the test to represent the actual object in your application. We can view the current identification property values of any object on your desktop using the Properties tab of the Object Spy. During a run session. which is a storehouse for objects. For example. You can modify identification properties manually while designing your test. When you add an object to an object repository. see Managing Test Objects in Object Repositories. the Click method is applicable to a WebButton test object. QuickTest: • Identifies the QuickTest test object class that represents the learned object and creates the appropriate test object. see Viewing Object Properties and Operations Using the Object Spy. For more information. QuickTest records the relevant operation as it is performed on an object. you specify which operation to perform on each test object. Netscape for Netscape Browser objects. If you record steps. When QuickTest learns an object in our application. Test Object and Native Properties and Operations The identification property set for each test object is created and maintained by QuickTest. the product developer for ActiveX objects. Property values of objects in your application may change dynamically each time your application opens. or use SetTOProperty statements during a run session. see Specifying or Modifying Property Values. Microsoft for Microsoft Internet Explorer objects. or based on certain conditions. For more information on modifying object properties. Understanding and Using Regular Expressions. generally using the value of one of its prominent properties. you can access the internal operations and properties of the run-time object using the Object property. you may want to use local object repositories. This reduces maintenance and enhances the reusability of your tests because it enables you to maintain the objects in a single. For more information. choosing. see Retrieving and Setting Identification Property Values. so that only that action can access the stored objects. If the available test object operations and identification properties for a test object do not provide the functionality you need. your changes do not have any effect on any other action or any other test (except tests that call the action. see Deciding Whether to Use Local or Shared Object Repositories. according to your needs. 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. We can retrieve property values from the run-time object during the run session by adding GetROProperty statements. A shared object repository stores objects in a file that can be accessed by multiple tests (in read-only mode). If an object with the same name is located in more than one shared object repository associated with the same action. you enable multiple actions to use the objects. 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. Object information that applies to many actions is kept in one central location. For more information. see Accessing Native Properties and Operations. When the objects in your application change. or modifying shared object repositories because all objects are automatically saved in a local object repository that can be accessed by its corresponding action. you can record and run tests without creating. the object definition is used from the first occurrence of the object. In this way. A local object repository stores objects in a file that is associated with one specific action. you can use a combination of objects from your local and shared object repositories. If you are familiar with testing. For more information. shared location instead of multiple locations. see Viewing Object Properties and Operations Using the Object Spy. For more information on associating shared object repositories. If you are new to using QuickTest. it is probably most efficient to save objects in a shared object repository. the action uses the local object definition. In this way. you can update them in one location for all the actions that use this shared object repository. or you can store the objects in your tests in one or more shared object repositories. You can also use the attribute object property to identify Web objects in your application according to user-defined properties. according to the order in which the shared object repositories are associated with the action. By storing objects in shared object repositories and associating these repositories with your actions. For information. Understanding Object Repository Types Objects can be stored in two types of object repositories—a shared object repository and a local object repository. you can use the same shared object repository for multiple actions—if the actions include the same objects. For each action. as described in Inserting Calls to Existing Actions). . see Associating Object Repositories with Actions. When you plan and create tests. you must consider how you want to store the objects in your tests.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. If you modify an object in the local object repository. if required. You can also transfer local objects to a shared object repository. You can store the objects for each action in its corresponding local object repository. you edit them using the Object Repository Manager.Local objects are saved locally with the 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. Object: Object is something. 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. Shared object repositories are read-only when accessed from tests. you can use the same object repository for multiple actions. You can also use multiple object repositories for each action. and can be accessed only from that action. When you open and work with an existing test. Software objects: . When using a shared object repository. which has structure and properties. Links. WebButton. 2. those can be used for performing specific operations. 3. WinButton. etc… Note: Test objects names vary from one environment to another. dictionary object class. Check boxes etc. Environment for using environment variables Automation objects/User defined objects User can create objects. delete operations on local repository. 4.TSR extension) Local Repository: QTP creates a Local Repository for every Action automatically during Recording. User can add some more objects to Local repository User can perform rename. Ex: 1. There are two types of repository available in QTP. Edit boxes. Services for inserting transaction points 4. Reporter for defining results. 2. Application class etc. Shared repository(. Types of Object in QTP: There are four types of object available in QTP.We call Windows. adodb. Web Pages. Ex: Creating objects in filesystemobject class.MTR extension) 2. as software objects. Utility objects They are QTP reserved objects used for Testing and Result reporting. . Ex: Buttons. Run time objects Test objects Utility objects Automation objects/User defined objects. Local repository (. Ex: WinEdit. SystemUtil for launching/closing the application. Buttons. That cannot be shared among tests. 1.connection class. 1. As it is QTP internal file user no need to save modifications. Run time objects: The objects present in the AUT.. Excel. Link. etc… Test Objects: References of Run time objects. 3. if we select fourth option. 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. Operations on Object Repository Adding objects a.Shared Repository: User (Test Engineer) creates the Shared Repository by adding objects. Using this method user can perform modifications on objects easily. if we select third option it stores All objects including static objects. it saves automatically) B. we have to select object classes then it stores that class objects.) Renaming Objects a. we can select more than one class also. Local Repository: . That can be shared among number of tests. if we select second option it stores all default objects. 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. 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. >close repository b. if we do not want source files we can delete. Spying Objects For getting objects information. property & Values) QTP is providing a feature called Object Spy. (Test objects names. source repository files will be available. Navigation>Tools>object spy>take hand icon & Show the object>get information (Object Spy shows the specific objects all available properties with their values) . 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.Resources > object repository >select object and right click >choose rename option >modify the name>release the mouse. 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. Shared Repository: Resources >object repository manager>file>open>browse path of the repository file >file>enable editing>select object &Right click>choose rename option>modify the name > release mouse>save the file & close repository manager. Deleting Objects a. Note: After merging also. using this we can get objects information. Local Repository: Resources > object repository >select object and right click >choose delete option >confirm deletion>.>close repository b. Navigation: Select object in the repository >view>highlight in application>it highlights specified objects in the application. Highlight in Application This feature can be used for identifying objects from repository to application. Importing Repository from XML file.Note: As Object spy is an important feature. We can import XML file to our repository. it can be available in 3 Areas. Exporting Repository to an XML file We can export our repository file to an xml file. 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: . In local repository 3. In tools Menu 2.(1. Navigation: File>import from XML >browse path of the XML file >it loads objects. Navigation: File >export Test objects to XML Enter the file name and Save with xml extension. 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. Generally for every object 20-25 properties information available. like this qtp learns one by one. Qtp has default object identification configuration for every environment. in order to avoid Ordinal Identifier. qtp recognizes object using 2 0r 3 important properties. 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. QTP learns information in the following in case of Smart Identification: Smart identification is an optional feature. if it feels sufficient then it stops learning otherwise. After normal identification if qtp feels not satisfied then it goes to smart . At the end of assistive properties list also if it feels not satisfied and it finally goes to Ordinal Identifier. if we feel that config is not sufficient for recognizing objects in our application. if we feel normal identification is not sufficient for any object. and then we configure Smart Identification for that object. It learns first assistive property and once again stops and thinks. qtp generates 0. If it feels sufficient.1.location starts from zero.2 like numbers.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.making Tool settings globally is not possible. QTP is providing a special feature called "Generate Script". STEPS: 1) Settings available in 3 areas. For making tool settings global. Tool Settings Globalization: As QTP is a I-tier(Stand-alone) application. index starts from zero 3) Creation time: it is based on loading time of the web objects. then it stops learning otherwise it goes Optional Filter Properties and learns one by one. NOTE: After executing these scripts all team members can get same settings. 2) index: it is based on sequence of the programs. Ordinal identifiers: There are 3 types of ordinal identifiers available 1) Location: is based on object location in the AUT . . 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. in smart identification 2 types of properties available. 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 SetNextRow Ex: g="gcreddy" datatable.1) = g .Value (1. Sheet_Name) = Value / variable Or datatable(Parameter_Name.Value (1.1) c=cint(a)+cint(b) datatable.Value(Parameter_Name. Sheet_Name) Ex: Option explicit Dim a.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. Sheet_Name) = Value / variable To get data Syntax: Variable = datatable. Sheet_Name) Or Variable = datatable(Parameter_Name.Value(Parameter_Name.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.Value (2. Syntax: datatable. To set data Syntax: datatable.SetCurrentRow (3) datatable.Value (1.SetCurrentRow(Row_Number) g="gcreddy" datatable. b.SetNextRow 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.1) b=datatable.SetCurrentRow (3) datatable. c a=datatable.Value (3. Import “F:\Inputdata.Export “Path of File” Ex: datatable.Export “F:\gcreddy. “Destination Sheet” Ex: datatable.SetCurrentRow (3) datatable.xls” 11) ImportSheet We can use this method to import a specified sheet of Microsoft Excel Sheet to the Runtime Data table.SetPrevRow Ex: g="gcreddy" datatable.ImportSheet “Path of File”.(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.ImportSheet “E:\gcreddy.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.xls” 13) ExportSheet We can use this method to export a copy specified sheet of Run Time Data table to the . Syntax: datatable.Import “Path of File” Ex: datatable. “Source Sheet”.SetPrevRow datatable.Value (1.1) = s (10) Import We can use this method to import Microsoft Excel File to the Runtime Data Table (Including all sheets) Syntax: datatable.xls”.3. Syntax: datatable. ExportSheet “F:\gcreddy. 2 ********************** Data Driven Testing for Login Operation using Data Table methods Datatable.GetRowCount For i= 1 to Rows_count Datatable. Syntax: datatable."Failed" Login="Login Operation Failed" Datatable("Result"."res".3) Dialog("Login").Set Datatable("Agent".GetSheet(3).WinEdit("Agent Name:").Activate Dialog("Login").WinButton("Cancel").Set Datatable("Pwd".existing or new Excel File.ReportEvent micFail.xls”.SetCurrentRow(i) SystemUtil."Passed" else Reporter.ExportSheet “Path of File”."res".3)=Login Reporter.WinButton("OK").3 Rows_count=Datatable.Dialog("Flight Reservations").Click End If If Window("Flight Reservation").WinEdit("Password:").ReportEvent micPass.3) Dialog("Login")."C:\Program Files\HP\QuickTest Professional\samples\flight\app\".WinButton("OK").exe".1.xls".Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.Click If window("Flight Reservation").AddSheet "Login" Datatable."".3)=Login Dialog("Login").Exist(3)Then Window("Flight Reservation").exist(10) Then Login="Login Operation Successful" Datatable("Result". “Sheet Name / Source Sheet” Ex: datatable.Close End if Next .Click Dialog("Login")."open" Dialog("Login").ImportSheet "C:\Documents and Settings\gcr\Desktop\gcreddy. Dynamic Programming Static Programming In this style of script generation."width:=60"). then we can provide more properties information by separating with commas. Password:.Winedit("attached text:=Password:"). Login. WinEdit and WinButton – Test Objects 2. Dialog.Set "gcreddy" 4) dialog("text:=Login").Descriptive Programming Descriptive Programming Entering / Providing objects information directly into the test script is called Descriptive Programming.exe" 2) dialog("text:=Login"). Set. attached text . Example: 1) Invokeapplication "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a. 1.Property names 3.Activate 3) dialog("text:=Login"). Note 3: . OK .Property values or Logical Names of the Object 4. Click .Winbutton("text:=OK". Activate. In this method of script creation.Set "mercury" 5) dialog("text:=Login"). Agent Name:.Winedit("attached text:=Agent Name:"). Descriptive programming is basically 2 types. we provide objects information directly into the script. Setsecure. 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. we no need to have Object Repositories.Click Note: 1.Methods Note2: If we feel one property information is not sufficient for recognizing the object uniquely. Static Programming 2. Advantages: a) Descriptive Programming based Test scripts are faster in execution than Repository based Test scripts. text. then we can handle .Set "mercury" Dialog(Login).EXE". Example 2: SystemUtil.Winedit(Agent). if we take other line then we have to use Const Statement again.Click Advantages: If we maintain Object Information in the centralized location.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.Set "asdf" Dialog(Login).Activate Dialog(Login).).Run "C:\Program Files\Internet Explorer\IEXPLORE.com/" ------------------------------------------------------------------If we want maintain ‘Objects information’ in centralized location then we can use Constants.Winbutton(Ok)."open" Browser("title:=Google").If we want to get objects information (Test objects.Sync Browser("title:=Google").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.Navigate "http://www.Page("title:=Google"). This feature is available in Tools Menu.Winedit(Pwd").exe" Dialog(Login).icicibank. we can load the library file during run-time Syntax: ExecuteFile “Path of the Library file(."C:\Program Files\Internet Explorer". Ok="text:=OK" Note: we can declare no of Constants in a line by separating with Camas (. Steps: Creating Constants: Const Login="text:=Login". Creating a Library file Place Constants in Notepad and save as . Agent="attached text:=Agent Name:" Const Pwd ="attached text:=Password:". we can use object spy feature. in local repository and in repository manager."". properties and values). value="OK" Generating Tests using Properties collection Objects Invokeapplication "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a. we can generate tests. provide properties information and use description objects in the test script.Page("title:=Google").value="Login" oLogin("width").Click Note1: Create Description objects and put into one library file. ------------------------------------------------------------------- Dynamic Programming In this style of script generation.Create oPassword=description. first we create description objects.Create oOk=description.exe" Dialog(oLogin).EXE" Browser("name:=Google").Run "C:\Program Files\Internet Explorer\IEXPLORE.Winedit(oPassword). Creating Properties Collection Objects Set Set Set Set oLogin=description.Winedit(oAgent).Create Entering Properties Information into Objects oLogin("text").Create oAgent=description.com/ .Winbutton(oOK).Navigate http://www.value=320 oLogin("height"). Note2: Dynamic programming is some difficult in preparation than static programming but maintenance is very easy.Sync Browser("name:=Google").Set "mercury" Dialog(oLogin).jjperfumes.Activate Dialog(oLogin). by associating that library file.modifications easily.Set "gcreddy" Dialog(oLogin).value=204 oAgent("attached text").value="Password:" oOk("text").value="Agent Name:" oPassword("attached text"). ------------------------------------------------------ Examples: Handling similar/Duplicate Objects using Index Property SystemUtil. fragrance & cologne online").Click .Browser("name:=JJ Perfumes-Discount perfume cheap brand name perfumes.Link("innertext:=Register"."index:=0").page("title:=JJ Perfumes-Discount perfume cheap brand name perfumes. fragrance & cologne online"). 3. There are 11 Checkpoints available in QTP: 1. 5. 6. 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. we can insert these checkpoints through standard checkpoint. 2. Table checkpoint Note 1: From 6 to 11 checkpoints are only for Web. Note 2: From 9 to 11 checkpoints are hidden checkpoints. it takes expected result from the user and compares with actual results during execution and provides test results. 7. 9.Inserting Checkpoints Inserting Checkpoints Check point is a verification point. 8. Image checkpoint 11. 4. . Standard Checkpoint: It checks object property values. Navigation for Editing standard checkpoint Select Checkpoint statement and right click > choose checkpoint properties option > modify the value > click Ok. Navigation for Deleting standard checkpoint: Select Checkpoint statements and right click > choose delete option.1. 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. . We can use this checkpoint for checking any property value. exact match. c. exact match. ignore spaces. text not displayed. Navigation: Keep tool under Recording mode >Insert menu > checkpoint > Text checkpoint > Show the object > click ok > Select options (Match case. b.Note: We can insert standard checkpoints in 3 ways. 2) Text Checkpoint: It Checks object’s text property value in different ways. text not displayed. ignore spaces. Through expert view. Navigation: Keep tool under Recording mode > Insert menu> Checkpoint > Text area checkpoint > Mark the area of text > select one or more options (Match case. a. 3) Text Area Checkpoint: It checks the text area present in the application. Through keyword view.) We can select one or more options > click ok & stop Recording. Through Active screen.) . we can compare complete bitmaps as well as part of the bitmaps. Bitmap checkpoint: It compares bitmaps. 5. Note: here we do not need to put tool under Recording mode and we do not need AUT since data is from backend. Database checkpoint: It checks Content of the back end Database. 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. 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. 6.Click ok and stop recording. 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. . 4. If an item is not available then result would be pass 7. If an item is available. XML Check point (from Resource) It checks content of the XML file. . Navigation: Keep tool under Recording mode in web environment > insert menu > checkpoint (from application)> show the xml pages >click ok > stop Recording. Result Criteria: a) b) c) If item is available but not according to W3C rules then fail.It is a configurable checkpoint. we can customize. 8. XML Check point (from Application) It checks content of the XML file. according to W3C rules then Pass. according to our requirements. 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. 9. Image checkpoint: It checks Image property values. 10. If XML file is an individual and path available. Navigation: Keep tool under Recording mode with web environment > Insert menu > checkpoint > Standard checkpoint >show the web page > click ok > click ok > stop recording. If XML file is part of web application.Navigation: Insert menu > checkpoint >xml checkpoint (from resource) > browse path of the XML File > click ok > click ok. 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. separate path is not available then we can choose inserting XML checkpoints from application. Page checkpoint: It checks number of Links. It is a hidden checkpoint. Note: 2. Note: 1. we can insert this through standard checkpoint. Images and Loading time in a web page. and then we can go for inserting xml checkpoint from resource. . Navigation: Keep tool under Recording mode under web environment > Insert menu > checkpoint > standard checkpoint >show the web table > click ok >stop recording.11. . Table checkpoint: It checks content of the web tables. 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. 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. 3. 2. It is stored in run time data table. 5. 6. 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: . 4. Types of Output Values: 1. 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. . 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. 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.> 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.We can use standard output values to output the properties values of most objects. 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. 6) XML output Value (From Resource): We can use XML output values to output the values of XML elements in XML documents. . Navigation: Insert menu> output value > 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.4) Database output value: We can use Database output values to output the value of the contents of database cells. Navigation: Insert menu >output value> XML output value from resource > browse path of the XML file > click ok > select elements >click ok. 5) XML output value (from application): we can use XML output values to output the values of XML elements in XML documents. Activate Dialog("Login").Dynamic Test Data Submission: Through Loop Statements we can give strings also but every time user has to enter data.Activate Window("Flight Reservation").Parameterization Passing parameters. 6. Data Driven Testing: Testing the Same operation with multiple sets of test data. It has 3 types of usage . For orderno=1 to 10 step 1 ' for one increment step keyword is not mandatory Window("Flight Reservation").WinEdit("Agent Name:"). through this we can pass multiple values.Click Window("Flight Reservation").Dialog("Open Order"). Fetching Test Data directly from External files (Flat files & Spreadsheets) 5.exe" Dialog("Login"). Through Data Table: QTP adds one data table (Spreadsheet) for every test.WinEdit("Password:").Set Agent Dialog("Login"). 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("OK"). Getting Test Data from front end objects.WinButton("Button").SetSecure password Dialog("Login"). Through Data Table 4.").Set orderno Window("Flight Reservation"). .WinEdit("Edit").Set "ON" Window("Flight Reservation").Click Next 2. Through Loop Statements 2.WinEdit("Agent Name:"). Oracle etc).WinCheckBox("Order No.Click Window("Flight Reservation"). Types of Parameterization: We can parameterize tests in several ways in QTP 1. Note: We can’t generate Strings. Through Loop Statements: We can use loop statements for passing sequential numbers & Logical Numbers. 1.Close Next 3.Dialog("Open Order").Dialog("Open Order"). We use parameterization in Data Driven Testing. Dynamic Test Data Submission 3.Type micTab Dialog("Login").WinButton("OK"). we can use Data Table for Data Driven Testing. Fetching Test Data directly from Databases (MSAcess. WinEdit("Agent Name:").exe" Dialog("Login").SetSecure pwd Dialog("Login").) Run the test.1) Pass parameters. Importing test data from external Flat files c. Importing test data from external Spread sheets d. A. 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”.a.1) pwd=Datatable ("Password". Importing test data from Data bases.WinEdit("Password:").1) invokeapplication "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.Set Agent Dialog("Login").Type micTab Dialog("Login"). Sheet id) Example: agent=datatable(“agent”.Click Window("Flight Reservation").WinEdit("Agent Name:").WinButton("OK"). Entering test data directly into data table and use b. Entering test data directly into data table and use.Activate Dialog("Login"). Agent = Datatable("Agent".Close . 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. Start programs>MS Office>MS Access>file >new>Select blank Database>enter name of the database>Save with mdb extension. . 1. 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. but first we have to create /get the DSN(Data source Name)& we have to use SQL Commands. Importing test data from Data bases: Through Data table we can import Test Data from Data bases. Creating a Test Database: open MS Access (or we can use any other database). 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. c. Entering Data into Tables: Select table>enter the data.b. D. WinEdit("Password:").Set rs.WinEdit("Password:"). Fetching Test Data directly from Flat files Dim fso.con do until rs.SetSecure S(1) Dialog("Login").movenext loop .connection") Set rs=createobject("adodb.fields("password") Dialog("Login"). 4.Activate Dialog("Login"). by using the DSN we can get data for number of tests.WinEdit("Agent Name:").Set s(0) Dialog("Login").eof=true SystemUtil. myfile Set fso=createobject("scripting.Close rs.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.Type micReturn Window("Flight Reservation")."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".Type micTab Dialog("Login").open "select * from login".jet."open" Dialog("Login").Activate Dialog("Login").WinEdit("Agent Name:").exe"."".readline S=split(x.rs Set con=createobject("adodb."@") SystemUtil.WinEdit("Password:").mdb" rs.0") con.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.Close Wend Fetching Test Data directly from Excel Sheets Fetching Test Data directly from Databases Option explicit Dim con.recordset") con.provider=("microsoft.oledb.open "C:\Documents and Settings\pooja\My Documents\trigun.1) myfile.Type micReturn Window("Flight Reservation").filesystemobject") Set myfile=fso.4.Type micTab Dialog("Login").opentextfile("d:\trigun.atendofline <> true x=myfile."".WinEdit("Agent Name:").WinEdit("Agent Name:")."open" Dialog("Login").WinEdit("Password:").exe"."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".txt".SetSecure rs. Note: DSN Creation is one time activity.skipline While myfile.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.fields ("agent") Dialog("Login"). Syntax: Object Hirearchy. 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.Sync Selecting an appropriate Method: .Page("Yahoo! Toolbar"). Inserting Wait statements.time in milli seconds. but AUT takes less time for some operations execution and more time for some operations execution.Synchronization It is a process of matching the speeds of both QTP and AUT in order to get proper execution and results.waitproperty “property name”. Where Synchronization is required: During test execution QTP gives instructions one by one with same speed. Syntax: Wait(time in seconds) Note: If we insert wait statements QTP waits up to maximum time even though operation is completed. 2. that time we may not get proper execution and results. Syntax: object hierarchy. 1. 3. but QTP does not wait up to maximum time unnecessarily. In order to get proper results in between QTP & AUT synchronization is required. Inserting Synchronization points. Sync Method (Only for WEB) 5. after completion of the current operations. There are several methods available in QTP for synchronization. Note: if we insert Synchronization points.value. it does not wait up to maximum time. 4. Sync Method: (only for WEB) Waits for the browser to complete current navigation.Sync Ex: Browser("Yahoo! Toolbar"). After completion of one statement execution it goes to next statement immediately. Increasing Tool default synchronization time. 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. it goes to next step immediately. 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. it is better to use wait statement in functions. . Suppose in our test more statements are taking more time for execution then selecting “increasing tool time out” . 3. 2. even though some drawbacks are there in using wait statement. Above two are local features but wait statement is Vbscript feature.1. Suppose in our test one or more statements only are taking more time for execution then selecting “Inserting synchronization method” is better. EndTransaction “Transaction Name” Note: these options (Start and End Transactions) available in QTP tool Insert menu Example: services.exe".Activate Dialog("Login").WinButton("OK"). that can be used for measuring transaction time.StartTransaction “Transaction Name” Statements -----------Services. we want to measure how much time that one test or part of the test is taking for execution/running. we can measure using these transaction point (Start and End) Syntax: Services."open" Dialog("Login").Activate services. ST=Timer’ It returns elapsed time since 12:00 AM Mid night in seconds Example: .Click Window("Flight Reservation").Set "naga" Dialog("Login").WinEdit("Password:").EndTransaction "Login" Note: We can insert number of transaction points in a test Using Timer Function ‘Timer’ is a VB Script Built-in function.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a."".SetSecure "4baf50f18b0ae0d5f5425fe760653e96da50bde7" Dialog("Login").Inserting Transaction Points Inserting Transaction Points QTP is providing a Utility object called Services for measuring transaction time Suppose."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".WinEdit("Agent Name:").StartTransaction "Login" SystemUtil. "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a."open" Dialog("Login"). I used: ST for Start Transaction ET for End transaction TT for Transaction Time .SystemUtil.Activate ET=Timer TT=ET-ST msgbox TT Note: here ST. you can take any variable.WinEdit("Password:").exe".WinEdit("Agent Name:").WinButton("OK").Set "naga" Dialog("Login").SetSecure "4baf50f18b0ae0d5f5425fe760653e96da50bde7" Dialog("Login")."". ET and TT are variables.Activate Dialog("Login").Click Window("Flight Reservation"). After we open the Step Generator. Expert View. VBScript functions. 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). Before we open the Step Generator to define a new step. we first select the category for the step operation (test object. Hover. parameterizing them if required. The Step Generator then inserts a step with the correct syntax into y test. We can continue to add further steps at the same location without closing the Step Generator. or to access the list of library functions. property. in function libraries. we cannot use the Step Generator to access test object names or collections. we can add a step that checks that an object exists.Step Generator Step Generator (F7) Step Generator is a feature of QTP. Library of Functions. used for generating the Recordable and Non-Recordable steps. or function) and define the arguments and return values. or that stores the returned value of a method as an output value or as part of a conditional statement. . Utility object or function) and the required object or the function library. 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 then select the appropriate operation (method. and internal script functions For example. or Active Screen. We can open the Step Generator from the Keyword View. we first select where in our test the new step should be inserted. We can parameterize any of the values in our step. Note: we can use the Step Generator to insert steps in tests and function libraries. First. such a procedure might also retrieve items that are not comments. a single quotation mark by itself can be difficult to see at times. it makes the comment stand out from the rest of the text. VBScript allows two delimiters: the single quotation mark (') and the REM statement. you might consider following the single quotation mark with an asterisk when commenting your code: '* This is another comment. . This can be a problem if we use an automated procedure to extract comments from a script. Second. both of the following lines of code are valid comments: ' This is a comment using a single quote delimiter. it makes a good delimiter. To ensure that the script host does not attempt to interpret a comment as a command. For example. REM This is a comment using the REM statement as a delimiter. This approach has two advantages over the single quotation mark alone.Adding Comments Adding Comments to Scripts Comments are statements that are ignored by the script host when the script runs. Although most script writers use the single quotation mark. we must preface each comment with a comment delimiter. 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. If Err. If Err.Clear Wscript.CreateObject("WScript. WshNetwork. "\\RemoteServer\Public" '* Map drive Z. Comments included on the same line as a VBScript statement (end-of-the-line comments) are valid but can be difficult to read. Err.Clear Wscript. the comments are placed on separate lines.MapNetworkDrive "Z:".Echo "The drive could not be mapped.Number <> 0 Then Err. comments are placed on the same line as a VBScript statement." End If '* Map drive Z. in the first half of the script." End If . compare the two commenting styles in the following script snippet. "\\RemoteServer\Public" '* Check to make sure the operation succeeded. For example. Most people find it easier to quickly identify the comments used in the second half of the script.Always include comments on separate lines except for comments that accompany the declaration of a variable. ----------------------------------------------On Error Resume Next Set WshNetwork = WScript. while in the second half of the script.MapNetworkDrive "Z:".Echo "The drive could not be mapped.Number <> 0 Then '* Check to make sure the operation succeeded.Network") WshNetwork. ----------------------------------------------Code Commenting Conventions All procedures should begin with a brief comment describing what they do. and other system dependencies. and procedures should be named clearly to ensure that inline comments are only needed for complex implementation details. . erroneous comments. should also be described at the beginning of each procedure. or worse. algorithms. enumerating objects. resulting in unnecessary comment maintenance work. Return values for functions and variables that are changed by a procedure. procedures. Procedure header comments should include the following section headings. 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. At the beginning of your script. Sometimes a piece of pseudocode describing the algorithm can be helpful. dialog boxes. especially through reference arguments. you should include an overview that describes the script. This description should not describe the implementation details (how it does it) because these often change over time. Variables. The code itself and any necessary inline comments describe the implementation. 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. controls. For debugging. . It starts execution b. after that it executes one statement at a time. c. If it is function call. if we use step over it executes one statement at a time only. QTP is providing debug commands and breakpoints.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. 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. b. 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.3) Step Out (shift +F11): It executes all remaining statements in a function at a time. We can watch variables whether the variables are taking correct values or not at a specific point of time. Variables 3. there we can use breakpoints.y. We can change Values of Variables temporarily. Debug viewer Pane: It is used for viewing. Ex : Dim x.z x=10 y=20 z=x+y msgbox z msgbox "Hello" x=35 .Or Place mouse pointer before the statement and click. 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. 1. Watch 2. modifying or setting the value of the variables during the execution break with the help of 3 Tabs. Command Note: Through Debug Viewer Pane. y=67 z=x*y msgbox z msgbox "bye bye" Navigation: View menu > Debug Viewer > Use step into feature. . Syntax: Reporter. then we have to define our own result. XML and PDF formats.Doc)."Result Step". It provides test wise result only.ReportEvent micPass. we export test result from result window in Document (.Utility object ReportEvent-Method micPass-Status of the Result. QTP Result Window: After Running/Executing a test. HTML. suppose if we use flow control statements (conditional and Loop statements). For defining our own results."Res". and send defect reports. 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.Analyzing Test Results & Reporting Analyzing the Test Result is not a responsibility of QTP. if we use qtp tool features like checkpoints. After Running Tests. Res-Result step "Login operation Successful". test results.ReportEvent status of the Result. we can define our own results. if we execute test batches."Login operation Successful" exaplanation: Reporter. Note: QTP doen't provide batch wise test result. QTP is providing an utility object called "Reporter" by using reporter.Message . User (Test Engineer) has to analyze the test result. then QTP Provide result window."message" Example" Reporter. Status of the Result: 1) Pass -micPass or 0 2) Fail -micPass or 1 3) Done.micDone or 3 .micDone or 2 4) Warning. Result Exporting facility also available in QTP Result window. we can report defects in various methods. then after analyzing results. various methods for crating and enhancing Tests. After Running Tests. QTP provides result in Result window and also provides a facility to define our own Results. then entering defect details in company prescribed format and sending. 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.Reporting Defects QTP is an Object based Test tool. . After analyzing results. 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. If we are using QTP for Functional Test Automation and Defect management manual. QTP Provides. Any how Analyzing Results is the Responsibility of Test Engineer after running tests. then we can send defects directly from QTP result window. We can create and execute tests using QTP. delte) 2. insert. 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. Purpose of Actions: For understandability For reusing components Types of Actions: 1) Non Re usable actions 2) Re usable actions 3) External actions Operations on Actions: • Creating Actions • Splitting Actions • Renaming Actions • Deleting Actions • Calling an Action • Copying an Action • Making an Action Reusable/Non Reusable Creating an Action: Insert>call to new action>enter name of the action>click ok Steps: 1. . Create required actions(ex login. Splitting an action: Navigation: Place cursor in desired location>Edit menu>action>split action>Enter Action 1 name & action 2 name. Deleting Actions: Select desired action in action drop down box>edit menu>action>delete action>confirm deletion. 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. Note: U can’t edit Copying an action: Insert>call to copy of action>browse path of the test>select desired action>click ok. Generate total test in the default action 2. . Note: we can edit this action. Making an action reusable: Select Non Reusable action >edit >action>action properties>check reusable action check box >click ok.Steps: 1. Note: At a time we can split one actions into 2 actions. Split into meaningful actions. 3) msgbox x ' Output: H92 x=Left(9247837478.3) msgbox x ' Output: 10/ .5) msgbox x ' Output: 92478 val=#10-10-10# x=Left(val.3) msgbox x ' Output: Hyd val="9247837478" x=Left(val.Lengh) Example: Dim val.x val="Hyderabad" 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. 5) msgbox x ' Output: 37478 val=#10-10-10# x=Right(val.2) Right Function Returns a specified number of charectors of a given string from Right side Example: Dim val.3) msgbox x ' Output: bad x=Right(9247837478.x val="Hyderabad" x=Right(val.3) msgbox x ' Output: bad val="9247837478" x=Right(val.x val="Hyderabad" x=Mid(Val.5) msgbox x ' Output: rabad .5.5) msgbox x ' Output: /2010 3) Mid function Returns a specified number of charectors of a given string Example: Dim val.1) msgbox x ' Output: 8 val="H92yderabad" x=Right(val.3) msgbox x ' Output: rab val="Hyderabad" 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) .5) msgbox x ' Output: 837478 val=#10-10-10# x=Mid(val.5) msgbox x ' Output: 37478 val="H92yderabad" x=Mid(val.val="9247837478" x=Mid(val.6.5) msgbox x ' Output: 0/2010 4) StrReverse retuns reverse value of a string Example: Dim val.1) msgbox x ' Output: H92yderabad x=Mid(9247837478. returns 1(one) b) String 2 greater than string 1.str2. returns 0(zero) b) String 1 greater than string 2.1) msgbox x 'Output 0 str1="India" str2="Indian" x=StrComp(str1.str2.1) msgbox x 'Output -1 str1="Indian" str2="India" x=StrComp(str1.str2.1) msgbox x 'Output 1 str1=100 str2=100 .1) msgbox x 'Output 0 str1="india" str2="INDIA" x=StrComp(str1.1) msgbox x 'Output -1 str1="Indian" str2="Ndia" x=StrComp(str1.x str1="India" str2="India" x=StrComp(str1.str2.str2.msgbox x 'Output: 001 5) StrComp Function It compares two string (Binary and textual) if a) Both are equal.str2. returns -1 Example: Dim str1. 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 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.str2.x=StrComp(str1.1) msgbox x 'Output 0 str1=100 str2=101 x=StrComp(str1.str2. 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 . User defined variables: Variables that we predefine in the active external environment variables file. modifications are difficult. if you want to use some variables globally (From number of tests) declaring as global variables is better.Run ProductDir & app Dialog("Login"). we can access from all tests but these are designed as read only.Click Creating user defined environment variables: Navigation: . If we declare as local variables in number of tests.WinButton("OK").Activate Dialog("Login").WinEdit("Agent Name:").WinEdit("Password:"). Types of Environment variables: 1. We can create as many files as we want and we can change values of variables. Usage of environment variables: Syntax: Variable = Environment(“environment variable name”) Ex: X=Environment (“ActionName”) Msgbox x Example Script: ProductDir =environment ("ProductDir") app= "\samples\flight\app\flight4a. 2.exe" Systemutil. Built in variables: These are system defined variables.SetSecure "4b3c86f2107ff565cc195ba6c24739091b656407" Dialog("Login").Environment Variables Environment Variables in QTP These are global variables.Set "kajal" Dialog("Login"). .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. 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. Or We can load environment file directly Environment. 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. an Environment parameter value. Ways of 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.Regular Expressions Regular Expressions in QTP What is Regular Expression? It is a way of representing data using symbols. 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. They are often used within matching. a Data Table parameter value. For XML checkpoints we can set attribute or element values as regular expressions. or a property value in Descriptive programming. searching or replacing algorithms. We can define the text string as a regular expression. Regular Expressions in QTP: Regular expressions can be used in QTP for identifying objects and text strings with varying values. Ex: To search for the date 1867.a) Backslash Character: A backslash (\) can serve two purposes. we can use square brackets ([ ]) with the hyphen (-) character. It can be used in conjunction with a special character to indicate that the next character be treated as a literal character. or d. Example: [^ab] Matches any character except a or b. Matches welcomes. c) Matching Any Single Character in a List: Square brackets instruct QTP to search for any single character within a list of characters. enter: 186[789] d) Matching Any Single Character Not in a List: When a caret (^) is the first character inside square brackets. b) Matching Any Single Character: A period (. and cr g) Matching One or More Specific Characters: . welcomed. or 1869. such as the letters n. Alternatively. 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. Ex: welcome. caaaaaar.) instructs QTP to search for any single character (except for \n). Example: For matching any year in the 2010s. 1868. For example: ca*r Matches car. it instructs QTP to match any character in the list except for the ones specified in the string. the combination indicates a special character. 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. w. t. or welcome followed by a space or any other single character. but nothing else. starter.* Matches start. n) Matching Any Non-AlphaNumeric Character: \W instructs QTP to match any character other than alphanumeric characters and underscores. started. or after a newline character. + .A plus sign (+) instructs QTP to match one or more occurrences of the preceding character. m) Matching Any AlphaNumeric Character Including the Underscore: \w instructs QTP to match any alphanumeric character and the underscore (A-Z. or before a newline character. Using groups is especially useful for delimiting the argument(s) to an alternation operator ( | ) or a repetition operator ( * . . a-z. ? . we can use a combination of brackets and an asterisk to limit the search to a combination of non-numeric characters. start. and so forth. starting. j) Matching One of Several Regular Expressions: A vertical line (|) instructs QTP to match one of a choice of expressions. For example: ca?r Matches car and cr. h) Matching Zero or One Specific Character: A question mark (?) instructs QTP to match zero or one occurrences of the preceding character. 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. For example. just as in mathematics and programming languages. { } ). 0-9. For example: ca+r Matches car and caaaaaar. l) Matching the End of a Line: A dollar sign ($) instructs QTP to match the expression only at the end of a line. k) Matching the Beginning of a Line: A caret (^) instructs QTP to match the expression only at the start of a line. but not cr. _). 2 digits.Test(objFile. ([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.Arguments(0) For Each objFile In colFiles bMatch = objRE.CurrentDirectory Set objFolder = objFS.GetFolder(strCurrentDirectory) Set colFiles = objFolder.Pattern = WScript.Name) If bMatch Then WScript.Name End If Next . 3 digits. It provides simple support for defining regular expressions. or 4 digits between 1000-1200.Files Set objRE = New RegExp objRE.FileSystemObject") Set objShell = CreateObject("WScript.Global = True objRE. we need to match numbers with 1 digit.Shell") strCurrentDirectory = objShell. The regular expression below matches any number between 0 and 1200.For example: [a-zA-Z]* To match any number between 0 and 1200.IgnoreCase = False objRE. 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.Echo objFile. 2) Match Content in a File against a Regular Expression strFileName = "E:\gcreddy.Value Next .Close Set objRE = New RegExp objRE.FileSystemObject") Set objTS = objFS.Echo "Searching Within: " WScript.ReadAll WScript.Arguments(0) Set colMatches = objRE.txt" Set objFS = CreateObject("Scripting.Echo strFileContents objTS.Execute(strFileContents) WScript.Echo "At position " & objMatch.IgnoreCase = False objRE.FirstIndex & " matched " & objMatch.Global = True objRE.Pattern = WScript.Echo vbNewLine & "Resulting Matches:" For Each objMatch In colMatches WScript.OpenTextFile(strFileName) strFileContents = objTS. 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 . 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. Note: QTP doesn’t provide Batch wise result. Open 'Test batch Runner' Tool and Form Batches. 2). QTP is providing a separate Tool called 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. For performing Batch Testing. Run or Execute Test Batches from Test Batch Runner. . 5) View Test wise Result in 'Test Result Viewer'. Steps for Batch Testing: 1). Create Individual Tests and Run once. Forming a Test Batch: Launch Test Batch Runner. >Enter Scenario Name ->Next.>Select selected executable application->Next ->Select Recovery Operation [Keyboard.>Finish . Close Application Process.>Close . QTP runs Tests one by one. Mouse Operation.> Select Application Crash as Trigger event->Next .> Click Next . Navigation: Resources Menu -> Recovery Scenario Manager-> Click New. Recovery Scenarios Recovery Scenario Manager To recover from unexpected events and errors that are occurred in the test environment during run session.qrs” (qrs stands for QuickTest Recovery Scenario.>Next .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.>Save the scenario in specified location with “. For good recovery. error must be known the occurrence is unknown.>Next .) (ii) Popup Window.>If you want to check Add another operation else uncheck->Next . Restart. we can use Recovery Scenario Manager. 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. function Call. Microsoft Windows] ->Next . Navigation: Resources Menu ->Recovery Scenario Manager ->New .>Select “Popup .>Select Option . To handle unwanted popups. There are (4) Types of events such as: (i) Application Crash An open application fails during Test Run. Note: Allowing other products to Run Tests. Restart current test Next run.vbs fie path -> Next -> Uncheck Add another Recovery Operation -> Next -> Select Post-Recovery Test Run Option [Repeat current step and continue.>Next . Proceed to Next step.>Show unwanted window with Hand icon ->Next ->Next . Proceed to next test iteration. You can specify property values for each object in the hierarchy. Proceed to Next Action.vbs extension] ->Browse the .vbs extension] . Proceed to Next step.qrs” �� ok.>Next -> Select Post-Recovery Test Run Option [Repeat current step and continue. Proceed to Next Action. Stop the Test Run] -> Next-> Enter Scenario Name -> Next -> Select Option -> Finish -> Save the scenario with “.>Select function call as Recovery Operation ->Next [Open Notepad ->Save empty file with . A step in your test does not run successfully then Test Run Error can be raised. Proceed to Next Action. Click Cancel] take the script into function ->Save the library file ->Click Run (iii) Test Run Error.>Select function call as Recovery Operation ->Next [Open Notepad ->Save empty file with . Stop the Test Run] �� Select Option �� Next �� Enter Scenario Name �� �� Save the scenario with Finish �� Record required Recovery Operation [Click “. Proceed to next test iteration.vbs extension] -> Browse the .>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 . Click Cancel] take the script into function -> Save the library file -> Click Run .vbs fie path ->Next ->Uncheck Add another Recovery Operation .> Finish ->Save the scenario with “.vbs fie path ->Next ->Uncheck Add another Recovery Operation . Stop the Test Run] ->Next ->Enter Scenario Name ->Next .>Select Option . The property values of an object in your application match specified values. Proceed to Next step.qrs” -> Record required Recovery Operation [Click ok. Restart current test run.>Next .> Select Post-Recovery Test Run Option [Repeat current step and continue. Navigation : Resources Menu ->Recovery Scenario Manager ->New .>Browse the .qrs” ->Record required Recovery Operation [Click ok.false)->click next -> Select function call as Recovery Operation -> Next [Open Notepad -> Save empty file with .Window” as Trigger event ->Next ->Click on Hand Icon . Proceed to next test iteration.>Select “Testrunerror Window” as Trigger event ->Next ->select any error o .>Next . Restart current test run. Click Cancel] take the script Click Run Save the library file �� into function �� (iv) Object State. It allows us to use the familiar object.method syntax with a rich set of properties. .File System Operations File System Operations File System: Its an operating system feature. drives. it allows users to create. view and delete. modify. methods.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. and events to process folders and files.folders and files VB Script is providing an object called scripting. We can also employ the traditional Visual Basic statements and commands. our primary goal is to store data in an efficient. In this case. contained in the Scripting type library (Scrrun. however.filesystemobject") fso. alter. We may not want to have such overhead. The FSO model makes processing files much easier as well. the FSO model does not support binary files. The FSO model. or to determine if and where particular folders exist. We need to be able to create files. and output (read) the data. When processing files.dll). supports the creation and manipulation of text files through the TextStream object.filesystemobject") If fso. Examples: 1) Create a folder Dim fso. or our data access requirements may not call for the extra functionality associated with a full-featured database. use the FileOpen Function with the Binary keyword. To manipulate binary files. easy-to-access format. insert and change the data. storing our data in a text file or binary file is the most efficient solution. strFolder strFolder="D:\Documents and Settings\gcreddy\Desktop\Dibyalok" Set fso=createobject("scripting. strFolder strFolder="D:\Documents and Settings\gcreddy\Desktop\Dibyalok" Set fso=createobject("scripting. Although we can store data in a database. such as their names and the date they were created or last modified. and delete folders.The FSO model gives our application the ability to create.CreateFolder(strFolder) 2) Create a folder Dim fso. It also enables us to get information about folders. doing so adds a significant amount of overhead to our application.FolderExists(strFolder) Then . move. Set myField(1) wait 2 Dialog("text:=Login").1) '1 for Read.FileSystemObject") Set myFile=objFso.WinEdit("attached text:=Password:").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.Activate Dialog("text:=Login").ReadLine myField=Split(myLine.SkipLine Do Until myFile. 'Author: G C Reddy 'Date of Creation: 13-08-2010 'Pre-requisites: 'vinod.WinEdit("attached text:=Agent Name:").Close . 2-Write & 8-Append myFile.OpenTextFile("C:\Documents and Settings\gcr. myField Set objFso=CreateObject("Scripting. '********************************************************* 'Test Requirement: Data Driven Testing by Fetching Test data directly from a Text file.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.GCRC9A12FBD3D9\Desktop\vindod.CreateFolder(strFolder) End If 3) Data Driven Testing by fetching Test data directly from a Text file.AtEndOfStream myLine=myFile.".Click Window("text:=Flight Reservation").") SystemUtil.txt".Set myField(0) Dialog("text:=Login"). myFile.WinButton("text:=OK").msgbox "Folder already exists" else fso.exe" Dialog("text:=Login"). myLine. "C:\jvr".GetFolder(strDirectory) msgbox strDirectory & " already created " else Set objFolder = objFSO. objFolder.CreateFolder(strDirectory) end if 5) Returning a collection of Disk Drives Set oFSO = CreateObject("Scripting.FileSystemObject") If objFSO.CopyFolder "E:\gcr".FileSystemObject") oFSO.DeleteFolder("E:\Gcreddy") 3) Copying Folders Set oFSO=createobject("Scripting. objFolder.FileSystemObject") Set colDrives = oFSO. True 4) Checking weather the folder available or not.CreateFolder(strDirectory) 2) Delete a Folder Set oFSO = CreateObject("Scripting.DriveLetter Next .Drives For Each oDrive in colDrives MsgBox "Drive letter: " & oDrive.FileSystemObject") Set objFolder = objFSO. strDirectory strDirectory = "D:\Gcreddy" Set objFSO = CreateObject("Scripting.Filesystemobject") oFSO. strDirectory strDirectory = "D:\Gcreddy" Set objFSO = CreateObject("Scripting.FolderExists(strDirectory) Then Set objFolder = objFSO.Loop myFile. if not creating the folder Option Explicit Dim objFSO.Close Set objFso=Nothing for more Examples visit: File System Scripts File System Scripts 1) Create a Folder Option Explicit Dim objFSO. FileSystemObject") Set oDrive = oFSO.GetDrive("C:") MsgBox "Available space: " & oDrive.FileExists(strDirectory & strFile) Then Set objFolder = objFSO. if not creating the File strDirectory="E:\" strFile="Gcreddy. 1) Do Until objFile.FileSystemObject") Set objFile = objFSO.FileSystemObject") If objFSO. 1) Do Until objFile.CreateTextFile("E:\Gcreddy.txt") 2) Checking weather the File is available or not.AvailableSpace Flat File Scripts Flat File Scripts 1) Creating a Flat File Set objFSO = CreateObject("Scripting.FileSystemObject") Set objFile = objFSO.txt" Set objFSO = CreateObject("Scripting.FileSystemObject") Set objFile = objFSO.OpenTextFile("E:\Gcreddy.txt") End if 3) Reading Data character by character from a Flat File Set objFSO = CreateObject("Scripting.AtEndOfStream strCharacters = objFile.OpenTextFile("E:\Gcreddy.Read(1) msgbox strCharacters Loop 4) Reading Data line by line from a Flat File Set objFSO = CreateObject("Scripting.txt".AtEndOfStream strCharacters = objFile.CreateTextFile("E:\Gcreddy.txt".Readline msgbox strCharacters Loop 5) Reading data from a flat file and using in data driven testing .GetFolder(strDirectory) Else Set objFile = objFSO.6) Getting available space on a Disk Drive Set oFSO = CreateObject("Scripting. txt") txtFilepath. f2 f1="e:\Gcreddy1."".Delete() 8) Checking weather the File is available or not.txt" f2="e:\Gcreddy2.opentextfile ("F:\Gcreddy.WinButton("OK").atendofline <> True x=myfile.delete () End if 9) Comparing two text files Dim f1.GetFile("E:\gcr.WinEdit("Agent Name:"). 8.FileSystemObject") Set WriteStuff = myFSO. if available delete the File strDirectory="E:\" strFile="gcr. FilePath2) . ".1) myfile.txt" Public Function CompareFiles (FilePath1.OpenTextFile("e:\Gcreddy.FileSystemObject") If objFSO.myfile Set fso=createobject("scripting.Activate Dialog("Login").Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a. dateStamp dateStamp = Date() Stuff = "I am Preparing this script: " &dateStamp Set myFSO = CreateObject("Scripting.txt" Set objFSO = CreateObject("Scripting. True) WriteStuff.Set s(0) Dialog("Login").Close SET WriteStuff = NOTHING SET myFSO = NOTHING 7) Delete a text file Set objFSO=createobject("Scripting.FileExists(strDirectory & strFile) Then Set objFile = objFSO.Click Window("Flight Reservation").WinEdit("Password:").filesystemobject") Set myfile= fso."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".skipline While myfile.txt".") SystemUtil.Getfile(strDirectory & strFile) objFile.SetSecure s(1) Dialog("Login").Dim fso.WriteLine(Stuff) WriteStuff. WriteStuff.exe".Close Wend 6) Writing data to a text file Dim Stuff."open" Dialog("Login").txt".readline s=split (x. myFSO.filesystemobject") Set txtFilepath = objFSO. oMatches Set oFso = CreateObject("Scripting.Pattern = sString oRegEx.FileSystemObject") If FS.GetFile(FilePath1).txt" sString="gcreddy" Const FOR_READING = 1 Dim oFso. f2) = False Then MsgBox "Files are identical. File1.Read Str2 = File2." Else MsgBox "Files are different. oRegEx.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 . 0) CompareFiles = False Do While File1. FOR_READING) sReadTxt = oTxtFile. 0) If CompareFiles <> 0 Then CompareFiles = True Exit Do End If Loop File1.Size <> FS.Size Then CompareFiles = True Exit Function End If Set File1 = FS.ReadAll Set oRegEx = New RegExp oRegEx.Dim FS.Close() End Function Call Comparefiles(f1.IgnoreCase = bIgnoreCase oRegEx.OpenAsTextStream(1.OpenAsTextStream(1.Execute(sReadTxt) MatchesFound = oMatches. 0) Set File2 = FS. sReadTxt.Read CompareFiles = StrComp(Str1.AtEndOfStream = False Str1 = File1." End If 10) Counting the number of times a word appears in a file sFileName="E:\gcr.GetFile(FilePath2).OpenTextFile(sFileName.FileSystemObject") Set oTxtFile = oFso.Close() File2.f2) If CompareFiles(f1. File2 Set FS = CreateObject("Scripting. Str2.Global = True Set oMatches = oRegEx. oTxtFile.GetFile(FilePath1).GetFile(FilePath2). Item("Name") Wscript.Size Msgbox x& " Bytes" 14) 'Test Requirement: Open 1 to 10 orders in Flight Reservation .HDR=YES.Item("Department") Wscript.OpenTextFile _ ("e:\gcreddy.Readline arrServiceList = Split(strNextLine .Open "SELECT * FROM PhoneList.Connection") Set objRecordSet = CreateObject("ADODB.AtEndOfStream strNextLine = objTextFile.Set objConnection = CreateObject("ADODB.FileSystemObject") x= objFso. 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 .Open "Provider=Microsoft. ForReading) Do Until objTextFile. File1.0.txt".Echo "Extension: " & objRecordset.FMT=Delimited""" objRecordset.Jet.Fields.FileSystemObject") Set objTextFile = objFSO.Echo "Name: " & objRecordset.OLEDB.txt" Set objFso=CreateObject(" Scripting. adOpenStatic.GetFile(File1).Fields.Fields." & _ "Extended Properties=""text.MoveNext Loop 12) Read a Text File into an Array Const ForReading = 1 Set objFSO = CreateObject("Scripting.Echo "Service: " & arrServiceList(i) Next Loop 13) 'Calculate size of a Text file Dim objFso. adCmdText Do Until objRecordset. adLockOptimistic. _ objConnection.4.File2 File1="C:\Documents and Settings\1 RIGHATWAY\Desktop\xyz.EOF Wscript.") Wscript.Echo "Department: " & _ objRecordset.Recordset") strPathtoTextFile = "C:\Databases\" objConnection.csv". "." & _ "Data Source=" & strPathtoTextFile & ".Echo "Server name: " & arrServiceList(0) For i = 1 to Ubound(arrServiceList) Wscript.Item("Extension") objRecordset. WriteLine "--------------------" If Not Window("Flight Reservation").Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.WriteLine "Cusomer Names" myFile. objFso.Set "asdf" Dialog("Login").Dialog("Open Order").Exist(3) Then SystemUtil.WinCheckBox("Order No.WinButton("OK").WinEdit("Agent Name:").exe".Click Window("Flight Reservation").WinButton("Button").Click Customer_Name = Window("Flight Reservation")."open" Dialog("Login").Activate Dialog("Login").WriteLine Customer_Name Next myFile."C:\Program Files\HP\QuickTest Professional\samples\flight\app\"."".WinEdit("Password:").WinEdit("Edit").Activate Window("Flight Reservation").Set "ON" Window("Flight Reservation").Click End If For Order_Number= 1 to 10 step 1 Window("Flight Reservation").FileSystemObject") Set myFile= objFso.Close Set objFso=Nothing .GetROProperty("text") wait (2) myFile.2) myFile.txt".Dialog("Open Order").").CreateTextFile ("C:\Documents and Settings\1 RIGHATWAY\Desktop\abcNew.Set Order_Number Window("Flight Reservation").WinButton("OK").WinEdit("Name:").SetSecure "4c48590870466b8dc050bbd24e816890c747ccf8" Dialog("Login").Dialog("Open Order").'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. Customer_Name. myFile Set objFso=CreateObject("Scripting. Data Source=Your_Server_Name.UserId=Your_Username." SQL OLE DB connection strings Standard Security: "Provider=SQLOLEDB. SQL Server connection strings SQL ODBC connection strings Standard Security: "Driver={SQLServer}.Pwd=Your_Password.Initial .Server=Your_Server_Name.Trusted_Connection =yes." Trusted connection: "Provider=SQLOLEDB. whether on the same machine or not.Server=Your_Server_Name.Data Source=Your_Server_Name.Database connections Database connections Database connection is a facility in computer science that allows client software to communicate with database server software.Initial Catalog= Your_Database_Name.Database=Your_Database_Name.Database=Your_Database_Name.Uid=Your_Usernam e.Password=Your_Password." Trusted connection: "Driver={SQLServer}. NET framework) connection strings Open connection to Access database: "Provider=Microsoft."Server=Your_Server_Name.Initial Catalog=Your_Database_Name." MS Access OLE DB & OleDbConnection (. Password=" Open connection to Access database using Workgroup (System database): "Provider=Microsoft.0. Uid=Your_Username.mdb)}.Database=Your_Database_Name.Jet.4." < br>2.Initial Catalog= Your_Database_Name. Dbq=C:\App1\Your_Database_Name.mdb." Exclusive "Driver={Microsoft Access Driver (*.4.Jet.0. Remote Provider=Microsoft.Uid=Your_Username. Jet OLEDB:Database Password=Your_Password" Open connection to Access database located on a network share: "Provider=Microsoft.mdb.mdb)}.mdb.OLEDB. Data Source=c:\App1\Your_Database_Name.mdw.4. Jet OLEDB:System Database=c:\App1\Your_System_Database_Name.Trusted_Connection=False" Trusted connection: 1. Data Source=c:\App1\Your_Database_Name.UserID=Your_Username.Initial Catalog= Your_Database_Name.mdw" Open connection to password protected Access database: "Provider=Microsoft.Database=Your_Database_Name.UserId=Your_Username.Pwd=Y our_Password.OLEDB. SystemDB=C:\App1\Your_Database_Name.Catalog=Your_Database_Name.mdb.mdb.Jet.Trusted_Connection=True.UserId=Your_Username. "Data Source=Your_Server_Name." MS Access connection strings MS Access ODBC connection strings Standard Security: "Driver= {MicrosoftAccessDriver(*. Exclusive=1.DBQ=C:\App1\Your_Database_Name.mdb)}. "Data Source=Your_Server_Name. Data Source=c:\App1\Your_Database_Name.OLEDB." Trusted connection: "Provider=SQLOLEDB. DBQ=C:\App1\Your_Database_Name.Password=Your_Password.mdb" Open connection to Access database located on a remote server: "Provider=MS Remote. Data Source=c:\App1\Your_Database_Name. Data Source=\\Server_Name\Share_Name\Share_Path\Your_Database_Name. User Id=admin.Data Source=Your_Server_Name.Integrated Security=SSPI.OLEDB." SQL OleDbConnection .Password=Your_Password.NET strings Standard Security: 1." SQL SqlConnection .4.4.NET strings Standard Security: "Provider=SQLOLEDB.Initial Catalog=Your_Database_Name.OLEDB. Remote Server=http://Your-Remote-Server-IP.0.mdb" .0.Jet.Jet.Integrated Security=SSPI.Integrated Security=SSPI.Data Source=Your_Server_Name." 2. "Server=Your_Server_Name. Pwd=Your_Password.Password=Your _Password.0." Workgroup: "Driver={Microsoft Access Driver (*.mdb. "Provider= OraOLEDB.Password=Your_Password.Oracle." Open trusted connection to Oracle database "Provider= OraOLEDB." Oracle OLE DB & OleDbConnection (.Uid=Your_Username.User Id=Your_Username.world. DATABASE=Your_MySQL_Database. PASSWORD=Your_Password. DRIVER={MySQL ODBC 3.UserId=Your_Username.OSAuthent=1.MySQL connection strings MySQL ODBC connection strings Open connection to local MySQL database using MySQL ODBC 3.UserId=Your_Username.Server=Your_Oracle_Server." 2." .NET framework) connection strings Open connection to Oracle database with standard security: 1.51Driver}. "Provider=MSDAORA. SERVER= localhost. Password=Your_Password.51 Driver "Provider=MSDASQL.NET framework) connection strings Open connection to MySQL database: "Provider=MySQLProv.Password=Your_Password. OPTION=3" MySQL OLE DB & OleDbConnection (.Your_Oracle_Database." Oracle connection strings Oracle ODBC connection strings Open connection to Oracle database using ODBC "Driver= {Microsoft ODBCforOracle}.Data Source= Your_Oracle_Database.Data Source=Your_MySQL_Database.Pwd=Your_Password.DataSource=Your_Oracle_Database.Oracle. UID= Your_Username. together with their properties.Net for automating QTP operations.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. Java script or VC++. methods and properties that enable us to control QTP from another application. QTP Automation object model provides objects. Example: . that automate our QTP operations. We can use Scripting languages or programming languages such as VBscript. We can use QTP Automation object Model to write scripts. methods and events. . and their relationships. An object model defines a set of classes and interfaces. Using this feature we can increase QTP performance. QTP is providing an object called “RepositoriesCollection”.option explicit Dim qtApp.Test qtTest. finding path of the repositories and removing repositories is called Dynamic Handling of Object Repositories.open "C:\Documents and Settings\admin\My Documents\login" Set qtTest=qtApp.Add “Path of the Repository File” Syntax for finding Position of the Repository: Variable=RepositoriesCollection.close qtApp.qtTest Set qtApp=createobject ("Quicktest.visible=True qtApp. To do this.RemoveAll .run qtTest.Application") qtApp.Remove(position) Syntax for Removing All Repositories: RepositoriesCollection.quit Note: AOM Script can be used in Automation framework as an Initialization script. Dynamic Handling of Object Repositories Dynamic handling of object Repositories Loading repositories during running.open "C:\Documents and Settings\admin\My Documents\open order" Set qtTest=qtApp.Find(“Path of the Repository”) Syntax for Removing the Repository: RepositoriesCollection.run qtTest.close qtApp.Launch qtApp. Syntax for Loading a Repository: RepositoriesCollection.Test qtTest. Click pos=RepositoriesCollection.WinButton("OK").RemoveAll *********************************** Go to home page for QTP Guide. . Interview questions and Framework etc.WinEdit("Agent Name:").Set "mercury" Dialog("Login").WinEdit("Password:").tsr" RepositoriesCollection.Add (RepPath) systemutil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.Example: RepPath="C:\Documents and Settings\Administrator\My Documents\Login. Script examples.Activate Dialog("Login").exe" Dialog("Login").Find(RepPath) RepositoriesCollection.Set "sudhakar" Dialog("Login").Remove(pos) RepositoriesCollection.