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:

I. 4)It has some limitations (It cannot test every thing) Which Software Testing should be automated? Tests that need to be execute of every build of the application (Sanity Testing) Tests that use multiple data values (Retesting / Data Drives Testing) Tests that required data from application intimates (G. Attributes) Load and Stress Testing Which Software Testing should not be automated? Usability Testing One time testing .a) Fast: Tools are faster in execution than human users b) Reliable: Tools are reliable in complex calculations and tasks c) Reusable: we can reuse Automated Tests at any number of times d) Repeatable: we can repeat same operations for required number of times e) Programmable:we can use flow control statements for appalying logic f) Comprehensive: we can execute test batches without human interaction also Test Automation can be used in below areas of Testing: a) Functional & Regression Testing b) Load/Stress/Performance Testing c) Security Testing d) Unit Testing Drawbacks of Automation Testing 1)It is expensive 2)We cannot automate all areas. 3)Lack of expertisation.U.

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

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

5 –2008 H..0.0) .• 9.00 –2009 January Overview ---------------------------------------------------------------a) Disadvantages of Manual Testing 1) Huge Amount of Human Resources as well as Environment (Test lab) 2) Time taking process 3) Less Accuracy 4) Tideness b) Advantages of Test Automation 1) 2) 3) 4) 5) 6) Fast Reliable Accurated Reusable Repeatable Comprehensive c) Draback of Test Automation 1) Expensive 2) Technical expertise 3) 100% Automation not Posible d) Types of Test Tool Business cla Technical cla -------------------------------------Vendor Tools Functional & Regression Test tools Opensource Performance/Load/stress Test tools In-House Test Management Tools Defect Management Tools Security Unit Test tools Etc.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...5...

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

if you perform any modifications in one view those automatically reflects in another view. 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.Test pane has 2 views. Expert view. 2) Active Screen It has an optional element of QTP. It can be used for understanding and editing the test easily. Key word view. it takes snap shots of every statement that user performed action or operation on AUT. Navigation: View menu>active screen (for launching and closing) . Note 2: Technical users use expert view and business user use key word view.Test in VB script format. Note 3: User can customize Test pane view options.Test in Icon based GUI format.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Shared object repositories are read-only when accessed from tests. Object: Object is something. which has structure and properties. Object Repository Object Repository: It is a storage place of QTP where objects information can be stored and it also acts as interface between the Test script and the AUT in order to identify the objects during execution. When you open and work with an existing test. You can also use multiple object repositories for each action. you edit them using the Object Repository Manager.Local objects are saved locally with the action. you can use the same object repository for multiple actions. Software objects: . When using a shared object repository. and can be accessed only from that 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.

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

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

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

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. Importing Repository from XML file. We can import XML file to our repository. Navigation: View>Locate in repository >show the object>click Ok>it locates specified object in the repository. In local repository 3.(1. Exporting Repository to an XML file We can export our repository file to an xml file.Note: As Object spy is an important feature. Highlight in Application This feature can be used for identifying objects from repository to application. In tools Menu 2. In Repository manager) View Options Locate in Repository This feature can be used for identifying objects from application to repository. Note: The purpose of this feature is Editing objects information outside of the QTP Navigation: Resource menu>object repository (Short cut key Ctrl+R) Object Identification Configuration Object Identification Configuration Overview: . Navigation: File>import from XML >browse path of the XML file >it loads objects. it can be available in 3 Areas.

At the end of assistive properties list also if it feels not satisfied and it finally goes to Ordinal Identifier. qtp recognizes object using 2 0r 3 important properties. After normal identification if qtp feels not satisfied then it goes to smart . QTP learns information in the following in case of Smart Identification: Smart identification is an optional feature. if it feels sufficient then it stops learning otherwise. 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 has default object identification configuration for every environment. like this qtp learns one by one. in order to avoid Ordinal Identifier. and then we configure Smart Identification for that object. It learns first assistive property and once again stops and thinks. if we feel normal identification is not sufficient for any object.Generally for every object 20-25 properties information available.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

QTP is providing debug commands and breakpoints.Debugging Tests Debugging Tests Debugging is a process of executing the script or a program in a User designed fashion with some temporary break points in order to identify the errors. It 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. If it is function call. if we use step over it executes one statement at a time only. it opens the function. after that it executes one statement at a time. c. It starts execution b. . For debugging. Debug Commands: 1) Step Into (short cut key F11): a.

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

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

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

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

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

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

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

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

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

2) Right Function Returns a specified number of charectors of a given string from Right side Example: Dim val.1) msgbox x ' Output: 8 val="H92yderabad" x=Right(val.5) msgbox x ' Output: rabad .5.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.3) msgbox x ' Output: rab 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.x val="Hyderabad" x=Mid(Val.x val="Hyderabad" x=Right(val.

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

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

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

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

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

File > settings > Environment > select variable type as user defined > click add icon (+) > enter variable name & Value > click ok (like this we can create number of variables) > click export > browse path & enter file name. .loadfromfile”path of the xml file” Usage of user defined Environment variables: Associate environment file to current test: Variable = Environment (“Variable Name”) X=environment (“city”) Msgbox x Modifying Environment files: Select XML file>open with notepad>modify the values>Save. Or We can load environment file directly Environment. Associating environment variable file: Navigation: File > settings >Environment > select variable type as user defined > check “load variables and values from the external file” > browse path of the xml file > click apply & ok. save with xml extension > click ok.

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

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

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

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

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

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 .

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

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

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

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

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

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

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

FileSystemObject") Set objFile = objFSO.CreateTextFile("E:\Gcreddy.GetFolder(strDirectory) Else Set objFile = objFSO.AvailableSpace Flat File Scripts Flat File Scripts 1) Creating a Flat File Set objFSO = CreateObject("Scripting.txt" Set objFSO = CreateObject("Scripting.OpenTextFile("E:\Gcreddy.txt".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".Read(1) msgbox strCharacters Loop 4) Reading Data line by line from a Flat File Set objFSO = CreateObject("Scripting.txt") 2) Checking weather the File is available or not.AtEndOfStream strCharacters = objFile. 1) Do Until objFile.6) Getting available space on a Disk Drive Set oFSO = CreateObject("Scripting. if not creating the File strDirectory="E:\" strFile="Gcreddy.AtEndOfStream strCharacters = objFile.FileSystemObject") Set oDrive = oFSO.OpenTextFile("E:\Gcreddy.FileSystemObject") If objFSO.FileSystemObject") Set objFile = objFSO.FileSystemObject") Set objFile = objFSO.CreateTextFile("E:\Gcreddy.txt") End if 3) Reading Data character by character from a Flat File Set objFSO = CreateObject("Scripting.GetDrive("C:") MsgBox "Available space: " & oDrive. 1) Do Until objFile.

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

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

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

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

Data Source=Your_Server_Name." Trusted connection: "Provider=SQLOLEDB.Initial Catalog= Your_Database_Name." SQL OLE DB connection strings Standard Security: "Provider=SQLOLEDB.Initial .Password=Your_Password.Server=Your_Server_Name.Pwd=Your_Password.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.Database=Your_Database_Name.Database=Your_Database_Name.Server=Your_Server_Name.UserId=Your_Username. whether on the same machine or not. SQL Server connection strings SQL ODBC connection strings Standard Security: "Driver={SQLServer}.Data Source=Your_Server_Name.Uid=Your_Usernam e.

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

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

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

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

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

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.