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. Attributes) Load and Stress Testing Which Software Testing should not be automated? Usability Testing One time testing .U.I. 4)It has some limitations (It cannot test every thing) Which Software Testing should be automated? Tests that need to be execute of every build of the application (Sanity Testing) Tests that use multiple data values (Retesting / Data Drives Testing) Tests that required data from application intimates (G.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.

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

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

0) .5 –2008 H..0.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..• 9.

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

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

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

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

QTP Add ins Info

This document provides QuickTest Professional add ins information like Activex, web, visual basic, SAP, Java, .NET, People soft, TE, Web services and Oracle environments. I) ActiveX Environment Object Description ---------------------------------------------------ActiveX An ActiveX control. ---------------------------------------------AcxButton An ActiveX button. ------------------------------------------------AcxCalendar An ActiveX calendar object. ---------------------------------------------------AcxCheckBox An ActiveX check box. ---------------------------------------------------AcxComboBox An ActiveX combo box object. -------------------------------------------------------AcxEdit An ActiveX edit box. -----------------------------------------------------AcxRadioButton An ActiveX radio button. ----------------------------------------------AcxTable An ActiveX table. -----------------------------------------------AcxUtil An object that enables you to work with objects returned by performing an operation (usually via the Object property) on an ActiveX test object. ******************************************************** II) Delphi Environment Object Description ----------------------------------------DelphiButton A Delphi button. -------------------------------------------------DelphiCheckBox A Delphi check box. ---------------------------------------------------DelphiComboBox A Delphi combo box. ----------------------------------------------------DelphiEdit A Delphi edit box. ----------------------------------------------------DelphiEditor A Delphi multi-line editor.

------------------------------------------------------------DelphiList A Delphi list. -----------------------------------------------------------DelphiListView A Delphi list-view control. ------------------------------------------------------------DelphiNavigator A Delphi navigator control. -------------------------------------------------------------DelphiObject A Delphi object. -------------------------------------------------------------DelphiRadioButton A Delphi radio button. --------------------------------------------------------------DelphiScrollBar A Delphi scroll bar. -----------------------------------------------------DelphiSpin A Delphi spin box. ----------------------------------------------------DelphiStatic A Delphi static control. ----------------------------------------------------------DelphiStatusBar A Delphi status bar. ------------------------------------------------------------DelphiTable A Delphi table. -----------------------------------------------------------DelphiTabStrip A Delphi tab strip. ----------------------------------------------------------DelphiTreeView A Delphi tree-view control. -----------------------------------------------------------DelphiWindow A Delphi window or dialog box. *************************************************** III) Java Environment Object Description JavaApplet Java applet. -----------------------------------JavaButtonA Java button. ----------------------------------------JavaCalendar A Java calendar. ----------------------------------------JavaCheckBox A Java check box. ----------------------------------------JavaDialog A Java dialog box. -------------------------------------------JavaEdit A Java edit box. ------------------------------------------JavaExpandBar A Java control that contains labeled bar items, which can be expanded or collapsed by the user. -------------------------------------------------------JavaInternalFrame An internal frame that can be activated from the Java applet. ---------------------------------------------------------JavaLink A Java control that displays text with links. ----------------------------------------------------------------JavaList A Java list box with single or multiple selection. --------------------------------------------------------------------

JavaMenu A Java menu item. ----------------------------------------------------JavaObject A generic Java object. --------------------------------------------JavaRadioButton A Java radio button. -------------------------------------------JavaSlider A Java slider. ------------------------------------------JavaSpin A Java spin object. ------------------------------------------JavaStaticText A Java static text object. -----------------------------------------------------JavaTab A Java tabstrip control containing tabbed panels. ---------------------------------------------------------------JavaTable A Java table. --------------------------------JavaToolbar A Java toolbar. ----------------------------------JavaTree A Java tree. ----------------------------JavaWindow A Java window. --------------------------------------****************************************** IV) .NET Web Forms Environment Object Description -------------------------------------WbfCalendar A .NET Web Forms calendar control. ---------------------------------------------------------------WbfGrid A .NET Web Forms DataGrid object. ---------------------------------------------------------------WbfTabStrip A .NET Web Forms tabstrip control. -------------------------------------------------------------WbfToolbar A .NET Web Forms toolbar control. ------------------------------------------------------------WbfTreeView A .NET Web Forms tree view object. ------------------------------------------------------------WbfUltraGrid A .NET Web Forms UltraGrid object. ************************************************** V) .NET Windows Forms Environment Object Description --------------------------------SwfButton A .NET Windows Forms button object. SwfCalendar A DateTimePicker or a Month Calendar .NET Windows Forms calendar object. SwfCheckBox A .NET Windows Forms check box. SwfComboBox A .NET Windows Forms combo box.

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

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

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

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

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

SiebView A view object in a Siebel test automation environment. SiebRichText A rich text control in a Siebel test automation environment. SiebTextArea A text area in a Siebel test automation environment. SiebList A list object in a Siebel test automation environment. SiebPicklist A pick list in a Siebel test automation environment. SiebScreenViews A screen view in a Siebel test automation environment. Dialog A Windows dialog box. SiebText A text box in a Siebel test automation environment. SiebCommunicationsToolbar The communications toolbar in a Siebel test automation environment. XIII) Standard Windows Environment Object Description Desktop An object that enables you to access top-level items on your desktop. SiebThreadbar A threadbar in a Siebel test automation environment. SiebTaskAssistant The Task Assistant in a Siebel test automation environment. SiebTree A tree view object in a Siebel test automation environment. SiebPageTabs A page tab in a Siebel test automation environment. SiebCheckbox A checkbox in a Siebel test automation environment. SiebCurrency A currency calculator in a Siebel test automation environment. SiebScreen A screen object in a Siebel test automation environment. SiebPDQ A predefined query in a Siebel test automation environment.SiebCalculator A calculator control in a Siebel test automation environment. SiebToolbar A toolbar in a Siebel test automation environment. SiebCalendar A calendar control in a Siebel test automation environment. SiebMenu A menu or menu item in a Siebel test automation environment. Static . SiebViewApplets A view applet in a Siebel test automation environment. SiebTaskUIPane The task UI pane in a Siebel test automation environment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Help Menu: This menu provides QTP help as well as VB Script help. 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 . Through this menu we can contact technical support people and we can send feedback.

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

Run "C:\Program Files\Internet Explorer\IEXPLORE.Set "gcreddy" Ex2: Browser("Google")."mercury") vi) Utility Statements Ex1: SystemUtil.icicibank.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). and generates them in a script in the Expert view. .Click iii) Comments iv) Flow Control Statements (Conditional & Loop) Ex:) If Total=Tickets*Price Then Msgbox "Test Passed" Else Msgbox "Test Failed" End If v) Function / Action calls Ex: Call Login("gcreddy". Price ii) Object calls Ex1: Dialog("Login").Link("Gmail"). Simultaneously it adds Objects information into Object Repository.WinEdit("Agent Name:").exe" **It launche the Application Ex2: SystemUtil."http://www.Page("Google"). y.Dim x. z Const City. During Recording QTP Creates steps in Keyword view.EXE".Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.

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

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

Additionally. our tests become more modular. 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. e) Advantages of Recording/ Where Applicable • It is used for Analyzing the AUT in the initial stage to find out weather the QTP tool is Recognizing all of our Application Objects or not • It is easy to create Tests / Test Scripts •It is used for frequently changing UI (User Interface) • It takes less time to create Tests Keyword Driven Methodology Keyword-Driven Methodology By creating our tests with a keyword-driven methodology in mind.• User may not have command on the Recorded script. So locating errors is difficult • Recorded scripts are QTP internal files. they may corrupt. because it is possible to add objects to the object repository before they exist in an application.

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

select File > New > Test. Each test object class has a list of identification properties that QuickTest can learn about the object. Create the required actions. Associate our object repositories with the relevant actions This enables us to insert steps that perform operations on those objects.Create new tests. . if needed. and a set of relevant operations that QuickTest can perform on the object. To do so. a sub-set of these properties that can uniquely identify objects of that class. Associate our function libraries with the relevant tests. 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.

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

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

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

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

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

Resources > object repository >select object and right click >choose rename option >modify the name>release the mouse. Deleting Objects a. Note: After merging also.>close repository b. source repository files will be available. Navigation>Tools>object spy>take hand icon & Show the object>get information (Object Spy shows the specific objects all available properties with their values) . Shared Repository: Resources >object repository manager>file>open>browse path of the repository file >file>enable editing>select object &Right click>choose rename option>modify the name > release mouse>save the file & close repository manager. using this we can get objects information. Spying Objects For getting objects information. if we do not want source files we can delete. Local Repository: Resources > object repository >select object and right click >choose delete option >confirm deletion>. 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. Defining New Test Objects Navigation: Object>Define new test object >Select Environment>Select Class of the object>Enter name of the object>Click Add>click close>Select object >select property name>enter value (like this select one by one properties and enter values)>save Note: This feature can be used for preparing tests before the AUT is ready. >close repository b. (Test objects names. property & Values) QTP is providing a feature called Object Spy. 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.

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

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

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

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

Sheet_Name) = Value / variable Or datatable(Parameter_Name.SetCurrentRow (3) datatable. c a=datatable.1) = g .Value (1.1) = g (8) SetNextRow We can use this method to take the row after the current Row as New Current Row in the Run time data table.SetNextRow datatable.We can use this method to set or get value of cell in the specified parameter and the current row of the Rum time data table.1) = c Note: Default property of Datatable is value (7) SetCurrentRow We can use this method to take a specified row as current row in the Run Time Datatable (By default it is 1st Row of 1st Sheet) Syntax: datatable.1) c=cint(a)+cint(b) datatable.1) b=datatable.SetCurrentRow(Row_Number) g="gcreddy" datatable. Sheet_Name) Ex: Option explicit Dim a. Sheet_Name) Or Variable = datatable(Parameter_Name.SetNextRow Ex: g="gcreddy" datatable.Value(Parameter_Name.Value (1.Value (1.Value (3. Syntax: datatable. Sheet_Name) = Value / variable To get data Syntax: Variable = datatable.SetCurrentRow (3) datatable. To set data Syntax: datatable.Value (2. b.Value(Parameter_Name.

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

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

Agent Name:. Static Programming 2. Set.Property names 3. Setsecure. b) Scripts are portable (we can run these scripts from any machine easily) c) Maintenance is easy (less amount of resources) d) We can start Test Execution process even though Application is not ready. Activate. Descriptive programming is basically 2 types. Password:.Winedit("attached text:=Agent Name:"). we provide objects information directly into the script.Winedit("attached text:=Password:"). Dynamic Programming Static Programming In this style of script generation. text. Click . 1.Property values or Logical Names of the Object 4.Methods Note2: If we feel one property information is not sufficient for recognizing the object uniquely. Dialog. OK .Set "gcreddy" 4) dialog("text:=Login"). Note 3: .Winbutton("text:=OK".Click Note: 1.exe" 2) dialog("text:=Login").Descriptive Programming Descriptive Programming Entering / Providing objects information directly into the test script is called Descriptive Programming. Example: 1) Invokeapplication "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a. WinEdit and WinButton – Test Objects 2. then we can provide more properties information by separating with commas. attached text ."width:=60").Activate 3) dialog("text:=Login"). we no need to have Object Repositories. Advantages: a) Descriptive Programming based Test scripts are faster in execution than Repository based Test scripts. Login.Set "mercury" 5) dialog("text:=Login"). In this method of script creation.

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

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

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

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

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 Deleting standard checkpoint: Select Checkpoint statements and right click > choose delete option.1. Standard Checkpoint: It checks object property values. Navigation for Inserting standard checkpoint Keep tool under recording mode > place cursor in desired location > Insert > check point > Standard checkpoint > Show the object > click okay > select property and enter expected results & click Ok and stop Recording. Navigation for Editing standard checkpoint Select Checkpoint statement and right click > choose checkpoint properties option > modify the value > click Ok. . We can use this checkpoint for checking any property value.

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

Navigation: Keep tool under Recording mode > Insert menu > Checkpoint > Bitmap checkpoint > show the Bitmap >click ok >select “check only selected area” option if we want to compare part of the bitmap > click ok >stop recording. 5. 4. Database checkpoint: It checks Content of the back end Database. . Note: here we do not need to put tool under Recording mode and we do not need AUT since data is from backend. 6. 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. Bitmap checkpoint: It compares bitmaps.Click ok and stop recording. we can compare complete bitmaps as well as part of the 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.

. Navigation: Keep tool under Recording mode in web environment > insert menu > checkpoint (from application)> show the xml pages >click ok > stop Recording. 8. according to our requirements. Configuring accessibility checkpoint: Tools menu> options >web > advanced > check/uncheck items > click apply > click ok Invigilation: Keep tool under recording mode with web environment >insert>checkpoint>accessibility checkpoint>show the webpage>click ok>click ok>stop recording. If an item is not available then result would be pass 7. XML Check point (from Resource) It checks content of the XML file. If an item is available. according to W3C rules then Pass.It is a configurable checkpoint. Result Criteria: a) b) c) If item is available but not according to W3C rules then fail. XML Check point (from Application) It checks content of the XML file. we can customize.

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

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

4. It is stored in run time data table. Types of Output Values: 1. 2. 6. 5.Inserting Output values Inserting Output Values It is a step in which one or more values are captured during test execution. Standard output value Text output value Text area output value Database output value XML output value (From Application) XML output value (From Resource) 1) Standard output value: . 3. it is located in QTP result window and can be retrieved later. The values can later be used as input at a different point in the run session or we can use as input for another test.

2) Text output value: We can use Text output values to output text strings displayed in an application.. Navigation: Keep tool under recording mode> Insert menu> output value > text output value > show the text >select one of the option(output text/text before/text after) > click modify if you want to change the column name > click ok > click ok. Navigation: Keep tool under recording mode > insert menu >output value > 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. .We can use standard output values to output the properties values of most objects. Navigation: Keep tool under Recording mode > Insert menu >output value> standard output value > show the object > click ok > select property > modify the column name (if required) > click ok >click ok >stop recording.> check in runtime table after running it. 3) Text Area output value: We can use text area output values to output text strings displayed within a defined area of the screen. When creating a text output value we can output a part of the objects text and we can also specify text before and after options.

. Navigation: Insert menu >output value> XML output value from resource > browse path of the XML file > click ok > select elements >click ok.4) Database output value: We can use Database output values to output the value of the contents of database cells. Navigation: Insert menu> output value > Database output value> choose specify SQL statements manually >click next >click create >Select Machine Data source > Select Driver (QT_flight32) > click ok > enter SQL statement (select *from orders) > click finish > select data cells > click ok > Run and it will capture and see the results in run time table. 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. 5) XML output value (from application): we can use XML output values to output the values of XML elements in XML documents. 6) XML output Value (From Resource): We can use XML output values to output the values of XML elements in XML documents.

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

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

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

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

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

Above two are local features but wait statement is Vbscript feature. 2. Suppose in our test one or more statements only are taking more time for execution then selecting “Inserting synchronization method” is better. it is better to use wait statement in functions. 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” .1. 3.

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

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

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

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

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

procedures. 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. Return values for functions and variables that are changed by a procedure. controls. and other system dependencies. dialog boxes. . Procedure header comments should include the following section headings. Variables. This description should not describe the implementation details (how it does it) because these often change over time. you should include an overview that describes the script. or worse. At the beginning of your script. algorithms. Sometimes a piece of pseudocode describing the algorithm can be helpful. resulting in unnecessary comment maintenance work. The code itself and any necessary inline comments describe the implementation. 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. should also be described at the beginning of each procedure.----------------------------------------------Code Commenting Conventions All procedures should begin with a brief comment describing what they do. erroneous comments. especially through reference arguments. and procedures should be named clearly to ensure that inline comments are only needed for complex implementation details.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Set "kajal" Dialog("Login").exe" Systemutil.SetSecure "4b3c86f2107ff565cc195ba6c24739091b656407" Dialog("Login").WinEdit("Password:"). 2. we can access from all tests but these are designed as read only.Environment Variables Environment Variables in QTP These are global variables. if you want to use some variables globally (From number of tests) declaring as global variables is better. User defined variables: Variables that we predefine in the active external environment variables file.WinButton("OK"). We can create as many files as we want and we can change values of variables.Activate Dialog("Login"). Built in variables: These are system defined variables. Usage of environment variables: Syntax: Variable = Environment(“environment variable name”) Ex: X=Environment (“ActionName”) Msgbox x Example Script: ProductDir =environment ("ProductDir") app= "\samples\flight\app\flight4a. modifications are difficult.Run ProductDir & app Dialog("Login").WinEdit("Agent Name:"). Types of Environment variables: 1.Click Creating user defined environment variables: Navigation: . If we declare as local variables in number of tests.

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

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

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

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

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

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

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

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

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

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

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

methods. We can also employ the traditional Visual Basic statements and commands. . drives. modify. It allows us to use the familiar object.File System Operations File System Operations File System: Its an operating system feature.folders and files VB Script is providing an object called scripting.filesystemobject and some methods for performing file systems operations File System Object Model: The File System Object (FSO) model provides an object-based tool for working with folders and files.method syntax with a rich set of properties. view and delete. it allows users to create. and events to process folders and files.

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

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

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

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

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

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

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

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

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

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

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

. We can use Scripting languages or programming languages such as VBscript. Java script or VC++. methods and events.Automation Object Model AOM Scripting (Automation Object Model) Object Model: An object model is a structural representation of software objects (classes) that comprise the implementation of a system or application. We can use QTP Automation object Model to write scripts. that automate our QTP operations.Net for automating QTP operations. methods and properties that enable us to control QTP from another application. and their relationships. QTP Automation object model provides objects. together with their properties. An object model defines a set of classes and interfaces. Example: .

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

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

Sign up to vote on this title
UsefulNot useful