QTP Guide

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

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

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

Dynamic Handling of Object Repositories

An overview on Test Automation Test Automation
Basically Software Testing is 2 types 1) Manual Testing 2) Test Automation Manual Testing: Testing software manually is called Manual Testing. we can test all accepts of software manually. Below Testing Types can be tested manually Test Types: a) Functional Testing b) Regression Testing c) GUI Testing d) Usability Testing e) Security Testing f) Compatibility Testing g) Recovery Testing h) Reliability testing Etc… Drawbacks of Manual Testing (i)Time consuming. (ii) More resources required. (iii)Human Errors (iv)Repetition of the Task is not much (v)Tiredness (vi)Simultaneous auctions are not possible (Parallel) Test Automation: Testing Software using any Automation tools is called Test Automation Advantages of Test Automation:

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

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

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

• 9.P • 10. -----------------------------------------------------------------------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..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...5..0) ..0.

Checkpoints. Test Batch Runner. 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 . SQL Engine...1 2006 9.0.2 2005 9.5. Object Repository etc.0 2009 (Jan) c) QTP License(Seat/Node Locked and Concurent/Float) c) QTP IDE 1) QTP Features Ex: Recording. 3) Integrated Tools (Others) Ex: Spread sheet. Test Result Dletion Tool etc.6 2002 (Nov) 6.2 2007 9..0 2004 8. 9. VB Script Engine.5 2003 8. 2) Integrated Tools (HP) Ex: Password Encoder.5 2008--------HP 10.

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 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. generating Tests b) Dynamic Programming i) Creating Collection Objects ii) Entering Properties Information into Collection Objects iii) Using Collection Objects.

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.

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

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

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

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

SiebApplet An applet in a Siebel test automation environment. SblTabStrip A number of tabs and four arrows that move its visible range to the left and to the right. SAPGuiStatusBar A status bar in an SAP GUI for Windows application. XII) Siebel Environment Object Description SblAdvancedEdit An edit box whose value can be set by a dynamic object that opens after clicking on a button inside the edit box SblButton A Siebel button. SAPGuiTabStrip A tab strip in an SAP GUI for Windows application. SiebButton A button control in a Siebel test automation environment.SAPGuiLabel A static text label in an SAP GUI for Windows application. or simple tree control in an SAP GUI for Windows application. SAPGuiOKCode An OK Code box in an SAP GUI for Windows application. SAPGuiRadioButton A radio button in an SAP GUI for Windows application. SAPGuiTable A table control in an SAP GUI for Windows application. SblCheckBox A check box with an ON and OFF state. SAPGuiMenubar A menu bar in an SAP GUI for Windows application. list tree. SAPGuiToolbar A toolbar in an SAP GUI for Windows application. SAPGuiWindow A window or dialog box containing objects in an SAP GUI for Windows application. SblEdit An edit box. SAPGuiTextArea A text area in an SAP GUI for Windows application. SblTreeView A tree view of specific screen data. SblTable A Siebel table containing a variable number of rows and columns. . SAPGuiSession Represents the SAP GUI for Windows session on which an operation is performed. SiebApplication An application in a Siebel test automation environment. SblPickList A drop-down pick list. SAPGuiUtil A utility object in an SAP GUI for Windows application. SAPGuiTree A column tree.

SiebToolbar A toolbar in a Siebel test automation environment. SiebMenu A menu or menu item in a Siebel test automation environment. SiebTree A tree view object in a Siebel test automation environment. SiebRichText A rich text control in a Siebel test automation environment. SiebList A list object in a Siebel test automation environment. SiebCalendar A calendar control in a Siebel test automation environment. Dialog A Windows dialog box. Static . SiebText A text box in a Siebel test automation environment.SiebCalculator A calculator control in a Siebel test automation environment. SiebCommunicationsToolbar The communications toolbar in a Siebel test automation environment. SiebScreen A screen object in a Siebel test automation environment. SiebTaskAssistant The Task Assistant 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. SiebPDQ A predefined query in a Siebel test automation environment. SiebViewApplets A view applet in a Siebel test automation environment. SiebCurrency A currency calculator in a Siebel test automation environment. SiebView A view object in a Siebel test automation environment. SiebCheckbox A checkbox in a Siebel test automation environment. SiebThreadbar A threadbar in a Siebel test automation environment. SiebTaskUIPane The task UI pane in a Siebel test automation environment. SiebScreenViews A screen view in a Siebel test automation environment. SiebPicklist A pick list in a Siebel test automation environment. SiebPageTabs A page tab in a Siebel test automation environment. SiebTextArea A text area in a Siebel test automation environment.

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

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

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

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

Test in VB script format. if you perform any modifications in one view those automatically reflects in another view. Note1: Here in test pane Test is same but views are different. Navigation: Tools Menu> view options> we can use font size and colors etc. 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. Key word view.Test in Icon based GUI format. 2) Active Screen It has an optional element of QTP. Navigation: View menu>active screen (for launching and closing) . Expert view. Note 3: User can customize Test pane view options.Test pane has 2 views. Note 2: Technical users use expert view and business user use key word view.

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

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

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

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

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

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

Tool Bar options 3. open existing tests.QTP Commands QTP Commands QTP Commands are available in 3 ways. Creates a new application area.Short cut keys (for Some important operations only) File menu: Through file menu user can create. Opens an existing business or scripted component. Creates a new business component. Opens an existing test. 1. Creates a new scripted component. save tests. export tests in zip format. Creates a new function library. .Menu options 2. 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.

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

enabling you to define settings for the open document. . 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.Convert to Scripted Component Print Print Preview Converts a business component to a scripted component. Edit Menu: It provides editing options and renaming. enabling you to manage the list of processes that are available in QuickTest. Closes the QuickTest session. Associates the active function library with the open document. Prints the active document. Opens the Settings dialog box. deleting and splitting actions. Displays the Keyword View as it will look when printed and enables you to modify the page setup. (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.

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

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

Record Run

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.

Object Repository

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

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

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

Help Menu: This menu provides QTP help as well as VB Script help. Through this menu we can contact technical support people and we can send feedback. Through this menu we can check for updates and download or install directly. QTP Test Process 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) .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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(Parameter_Name.Value (2.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.Value(Parameter_Name.1) b=datatable.Value (1. Sheet_Name) Ex: Option explicit Dim a.1) = g .Value (1. c a=datatable. Sheet_Name) = Value / variable Or datatable(Parameter_Name.SetNextRow Ex: g="gcreddy" datatable.SetCurrentRow (3) datatable. b.Value (1.Value (3.SetCurrentRow (3) datatable. To set data Syntax: datatable.SetNextRow datatable.SetCurrentRow(Row_Number) g="gcreddy" datatable.1) = c Note: Default property of Datatable is value (7) SetCurrentRow We can use this method to take a specified row as current row in the Run Time Datatable (By default it is 1st Row of 1st Sheet) Syntax: datatable. Syntax: datatable. Sheet_Name) Or Variable = datatable(Parameter_Name. Sheet_Name) = Value / variable To get data Syntax: Variable = datatable.1) c=cint(a)+cint(b) datatable.

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

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

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

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

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

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

6. 8. 5. . 2.Inserting Checkpoints Inserting Checkpoints Check point is a verification point. Table checkpoint Note 1: From 6 to 11 checkpoints are only for Web. we can insert these checkpoints through standard checkpoint. Note 2: From 9 to 11 checkpoints are hidden checkpoints. 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. 7. it takes expected result from the user and compares with actual results during execution and provides test results. There are 11 Checkpoints available in QTP: 1. Image checkpoint 11. 9. 3. 4.

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. Navigation for Deleting standard checkpoint: Select Checkpoint statements and right click > choose delete option. 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.1.

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

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

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

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

.11. Navigation: Keep tool under Recording mode under web environment > Insert menu > checkpoint > standard checkpoint >show the web table > click ok >stop recording. Table checkpoint: It checks content of the web tables.

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

Navigation: Keep tool under Recording mode > Insert menu >output value> standard output value > show the object > click ok > select property > modify the column name (if required) > click ok >click ok >stop recording. 2) Text output value: We can use Text output values to output text strings displayed in an application.> check in runtime table after running it. .. 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. 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.We can use standard output values to output the properties values of most objects. 3) Text Area output value: We can use text area output values to output text strings displayed within a defined area of the screen. Navigation: Keep tool under recording mode > insert menu >output value > text area output value >Mark the text area >click modify the column name if necessary > click ok > again click ok > check in run time table after running it.

4) Database output value: We can use Database output values to output the value of the contents of database cells. Navigation: Insert menu >output value> XML output value from resource > browse path of the XML file > click ok > select elements >click ok. 6) XML output Value (From Resource): We can use XML output values to output the values of XML elements in XML documents. Navigation: Insert menu> output value > Database output value> choose specify SQL statements manually >click next >click create >Select Machine Data source > Select Driver (QT_flight32) > click ok > enter SQL statement (select *from orders) > click finish > select data cells > click ok > Run and it will capture and see the results in run time table. 5) XML output value (from application): we can use XML output values to output the values of XML elements in XML documents. . Navigation: Keep tool under recording mode with web environment > Insert menu > output value > XML output value from application > Show the XML document > select elements > click ok >stop recording.

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

WinEdit("Agent Name:").1) Pass parameters.WinEdit("Password:"). Sheet id) Example: agent=datatable(“agent”. Importing test data from external Flat files c. Entering test data directly into data table and use.a.SetSecure pwd Dialog("Login").WinButton("OK").Close .1) pwd=Datatable ("Password".Activate Dialog("Login").1) invokeapplication "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a. Agent = Datatable("Agent". Steps: Generate the basic test>open data table(View>Data Table) Click on column header>enter the name of the field (like this we can create number of columns) > Enter Data>connect the data to test (variable=datatable(“column name”.Type micTab Dialog("Login").Click Window("Flight Reservation").exe" Dialog("Login").WinEdit("Agent Name:"). Entering test data directly into data table and use b. Importing test data from external Spread sheets d.) Run the test. A.Set Agent Dialog("Login"). Importing test data from Data bases.

.b. 1. D. 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. Creating a Test Database: open MS Access (or we can use any other database). 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. Entering Data into Tables: Select table>enter the data. but first we have to create /get the DSN(Data source Name)& we have to use SQL Commands. Start programs>MS Office>MS Access>file >new>Select blank Database>enter name of the database>Save with mdb extension. Importing test data from Data bases: Through Data table we can import Test Data from Data bases. c. Importing test data from external files: Open Data Table (view>Data table)>place mouse pointer on data table and right click>file>import from file>Click ok>Browsw path of the file(it imports data from the flat file) Connecting Test Data to QTP Test as above and run the test.

"".eof=true SystemUtil.0") con.Type micTab Dialog("Login")."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".fields("password") Dialog("Login").opentextfile("d:\trigun.fields ("agent") Dialog("Login")."open" Dialog("Login").WinEdit("Password:"). Note: DSN Creation is one time activity.connection") Set rs=createobject("adodb.Creating DSN & importing data Navigation: view>data table>Place mouse pointer on Data table>sheet>import>from database(Database query wizard opens)>choose ‘specify SQL statements manually>click next >click create>click new>select driver type>click next >browse path to store> enter DSN Name>Click Save>click next>click finish>select>browse the database& select>click ok>click ok>select DSN>click ok>enter SQL statement (select *from login)>click finish.WinEdit("Agent Name:").readline S=split(x. myfile Set fso=createobject("scripting.skipline While myfile.4.WinEdit("Agent Name:"). 4.rs Set con=createobject("adodb.SetSecure S(1) Dialog("Login").open "C:\Documents and Settings\pooja\My Documents\trigun.Close Wend Fetching Test Data directly from Excel Sheets Fetching Test Data directly from Databases Option explicit Dim con.con do until rs.WinEdit("Password:").""."open" Dialog("Login").WinEdit("Password:").atendofline <> true x=myfile.Activate Dialog("Login").WinEdit("Password:").Type micReturn Window("Flight Reservation").provider=("microsoft. Fetching Test Data directly from Flat files Dim fso.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a. by using the DSN we can get data for number of tests.exe".recordset") con."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".1) myfile.exe".SetSecure rs.Type micTab Dialog("Login")."@") SystemUtil.Set rs.WinEdit("Agent Name:").movenext loop .mdb" rs.Close rs.Activate Dialog("Login").txt".open "select * from login".Type micReturn Window("Flight Reservation").oledb.WinEdit("Agent Name:").Set s(0) Dialog("Login").jet.filesystemobject") Set myfile=fso.

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

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

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

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

or Active Screen. and internal script functions For example. The Step Generator then inserts a step with the correct syntax into y test. Expert View. 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. parameterizing them if required. we first select where in our test the new step should be inserted. We can parameterize any of the values in our step. we first select the category for the step operation (test object. 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). in function libraries. or to access the list of library functions. Note: we can use the Step Generator to insert steps in tests and function libraries. We can open the Step Generator from the Keyword View. Before we open the Step Generator to define a new step. Library of Functions. we cannot use the Step Generator to access test object names or collections. used for generating the Recordable and Non-Recordable steps. we can add a step that checks that an object exists. Utility object or function) and the required object or the function library. We can then select the appropriate operation (method. . or function) and define the arguments and return values. Hover. We can continue to add further steps at the same location without closing the Step Generator. or that stores the returned value of a method as an output value or as part of a conditional statement. After we open the Step Generator. property.Step Generator Step Generator (F7) Step Generator is a feature of QTP.

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

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

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

c. It starts execution b. it opens the function. If it is function call.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. if we use step over it executes one statement at a time only. . For debugging. Debug Commands: 1) Step Into (short cut key F11): a. It executes one statement at a time. 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. after that it executes one statement at a time. QTP is providing debug commands and breakpoints.

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. Navigation: Place cursor in desired location >Debug menu>Insert/Remove break point Or Use short cut key (F9) .b. Ex: Dim a.

Variables 3. Command Note: Through Debug Viewer Pane.Or Place mouse pointer before the statement and click. there we can use breakpoints. Watch 2. 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. We can watch variables whether the variables are taking correct values or not at a specific point of time.z x=10 y=20 z=x+y msgbox z msgbox "Hello" x=35 . We can change Values of Variables temporarily. Debug viewer Pane: It is used for viewing.y. modifying or setting the value of the variables during the execution break with the help of 3 Tabs. Ex : Dim x.

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

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

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

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

Create required actions(ex login. .Actions Action: Set of Statements for perfoming a Task(s) We divide our test into actions to streamline the process of testing. Splitting an action: Navigation: Place cursor in desired location>Edit menu>action>split action>Enter Action 1 name & action 2 name.delte) 2. insert. Purpose of Actions: For understandability For reusing components Types of Actions: 1) Non Re usable actions 2) Re usable actions 3) External actions Operations on Actions: • Creating Actions • Splitting Actions • Renaming Actions • Deleting Actions • Calling an Action • Copying an Action • Making an Action Reusable/Non Reusable Creating an Action: Insert>call to new action>enter name of the action>click ok Steps: 1. Prepare Scripts for those actions.

Calling an action: Insert>call to existing action>browse path of the test>select desired action>click ok. Note: At a time we can split one actions into 2 actions. Making an action reusable: Select Non Reusable action >edit >action>action properties>check reusable action check box >click ok. Generate total test in the default action 2. Note: we can edit this action. 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. Split into meaningful actions. .Steps: 1. Note: U can’t edit Copying an action: Insert>call to copy of action>browse path of the test>select desired action>click ok.

3) msgbox x ' Output: 10/ .3) msgbox x ' Output: Hyd val="9247837478" x=Left(val.5) msgbox x ' Output: 92478 val=#10-10-10# x=Left(val.3) msgbox x ' Output: H92 x=Left(9247837478.1) msgbox x ' Output: 9 val="H92yderabad" x=Left(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.Lengh) Example: Dim val.

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

6.5) msgbox x ' Output: 0/2010 4) StrReverse retuns reverse value of a string Example: Dim val.5) msgbox x ' Output: 37478 val="H92yderabad" x=Mid(val.x val="Hyderabad" x=StrReverse(val) msgbox x 'Output dabaredyH val="001" x=StrReverse(val) msgbox x 'Output: 100 val=1002 x=StrReverse(val) msgbox x 'Output: 2001 val=#10-10-10# x=StrReverse(val) msgbox x 'Output: 0102/01/01 x=StrReverse("Hyderabad") msgbox x 'Output: dabaredyH x=StrReverse(100) .val="9247837478" x=Mid(val.1) msgbox x ' Output: H92yderabad x=Mid(9247837478.5) msgbox x ' Output: 837478 val=#10-10-10# x=Mid(val.

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

str2.str2.1) msgbox x 'Output -1 6) Lcase function Coverts Upper case values into Lower case Dim val.1) msgbox x 'Output 0 str1=100 str2=101 x=StrComp(str1.x val="HYDERABAD" x=Ucase(val) msgbox x 'Output HYDERABAD .x=StrComp(str1.x val="HYDERABAD" x=Lcase(val) msgbox x 'Output hyderabad val="Hyderabad" x=Lcase(val) msgbox x 'Output hyderabad val="HederabaD" x=Lcase(val) msgbox x 'Output hyderabad val="hyderabad" x=Lcase(val) msgbox x 'Output hyderabad x=Lcase("HYDERABAD") msgbox x 'Output hyderabad 7) Ucase function Coverts Lower case values into Upper case Example: Dim val.

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

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

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. Associating environment variable file: Navigation: File > settings >Environment > select variable type as user defined > check “load variables and values from the external file” > browse path of the xml file > click apply & ok. Or We can load environment file directly Environment. save with xml extension > click ok. .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.

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

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

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

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

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

We can manage the virtual objects defined on our computer using the Virtual Object Manager. Navigation:  Select Tools Menu . Virtual objects enable us to create and run tests on objects that are not normally recognized by QTP.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.

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

Open 'Test batch Runner' Tool and Form Batches. QTP is providing a separate Tool called Test Batch Runner. 3) Provide permission to 'Test batch Runner' to run tests 4). Forming a Test Batch: Launch Test Batch Runner.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. Run or Execute Test Batches from Test Batch Runner. . For performing Batch Testing. 2). 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. Steps for Batch Testing: 1). Note: QTP doesn’t provide Batch wise result. Create Individual Tests and Run once. 5) View Test wise Result in 'Test Result Viewer'.

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

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

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

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

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

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

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

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

ReadAll Set oRegEx = New RegExp oRegEx.Read Str2 = File2. File2 Set FS = CreateObject("Scripting.OpenAsTextStream(1. FOR_READING) sReadTxt = oTxtFile. f2) = False Then MsgBox "Files are identical.txt" sString="gcreddy" Const FOR_READING = 1 Dim oFso.AtEndOfStream = False Str1 = File1. oMatches Set oFso = CreateObject("Scripting.Size <> FS. 0) If CompareFiles <> 0 Then CompareFiles = True Exit Do End If Loop File1.Pattern = sString oRegEx. oRegEx.FileSystemObject") Set oTxtFile = oFso. 0) CompareFiles = False Do While File1. 0) Set File2 = FS.Close() End Function Call Comparefiles(f1.OpenAsTextStream(1.Close() File2.OpenTextFile(sFileName.GetFile(FilePath2).Dim FS.Execute(sReadTxt) MatchesFound = oMatches.IgnoreCase = bIgnoreCase oRegEx. File1. Str2.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 .f2) If CompareFiles(f1. sReadTxt.Read CompareFiles = StrComp(Str1.GetFile(FilePath2). oTxtFile.GetFile(FilePath1).Global = True Set oMatches = oRegEx.Size Then CompareFiles = True Exit Function End If Set File1 = FS." End If 10) Counting the number of times a word appears in a file sFileName="E:\gcr.GetFile(FilePath1)." Else MsgBox "Files are different.FileSystemObject") If FS.

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

FileSystemObject") Set myFile= objFso.WinEdit("Agent Name:").'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. objFso.exe".Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a."C:\Program Files\HP\QuickTest Professional\samples\flight\app\".WinButton("OK").WinButton("Button").WriteLine Customer_Name Next myFile."). myFile Set objFso=CreateObject("Scripting.WinCheckBox("Order No.Activate Dialog("Login").WinEdit("Name:").Set Order_Number Window("Flight Reservation").WriteLine "--------------------" If Not Window("Flight Reservation").SetSecure "4c48590870466b8dc050bbd24e816890c747ccf8" Dialog("Login").txt".WinEdit("Edit").2) myFile."".GetROProperty("text") wait (2) myFile.Dialog("Open Order")."open" Dialog("Login").Set "asdf" Dialog("Login").CreateTextFile ("C:\Documents and Settings\1 RIGHATWAY\Desktop\abcNew.Exist(3) Then SystemUtil.WinEdit("Password:").Set "ON" Window("Flight Reservation").Dialog("Open Order").Activate Window("Flight Reservation").Click End If For Order_Number= 1 to 10 step 1 Window("Flight Reservation").WinButton("OK").Dialog("Open Order").Close Set objFso=Nothing .Click Window("Flight Reservation").WriteLine "Cusomer Names" myFile.Click Customer_Name = Window("Flight Reservation"). Customer_Name.

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

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful