QTP Guide

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

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

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

Dynamic Handling of Object Repositories

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

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

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

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

.5 –2008 H.0. -----------------------------------------------------------------------I) Basic Features of QTP ------------------------------------------------------------------------a) QTP Supporting Environments 1) UI (GUI/Windows and Web) 2) Only Windows (Clien side and Server side) b) Version History QTP derived from Astra QuickTest(1.5.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..• 9...0) ..P • 10.

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

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

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

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

QTP Add ins Info

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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) . used for Data driven testing. apply and okay.Configuring Active Screen: view>options>active screen tab>increase /Decrease capture level. 3) Data Table It has an integrated spread sheet (Excel like).

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

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

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

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

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

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

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

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

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

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

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

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

QTP Test Process 7 Stages of QTP Testing Process 1) Planning o o o o Analyzing the AUT Automation Test Plan Generation Automation Framework Implementation Generating/Selecting Test cases for Automation . Through this menu we can contact technical support people and we can send feedback.Help Menu: This menu provides QTP help as well as VB Script help. Through this menu we can check for updates and download or install directly.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Activate: It activates dialog boxes/Windows Syntax: Object hierarchy. Activate Ex: Dialog(“Login”).Activate Window(“Flight Reservation”).Activate Click Method: It clicks on an object (Buttons) Syntax: Object hierarchy. Click Ex: Dialog(“Login”).Winbutton(“ok”).click Close Method: It closes the window,Dialog box, Browser window etc. Syntax: Object hierarchy. Close Ex: Window(“Flight Reservation”).Close Browser(“Browser”).Close Dblclick: It Double clicks the object. Set Method: It can be used in three ways. a. For setting the value of an edit box Syntax: Object Hierarchy. SET “Value” Ex: Dialog (“Login”).WinEdit(“Agent Name”).Set “asdf” b. Selecting a Radio Button Syntax: Object Hierarchy. Set Ex: Window("Flight Reservation").WinRadioButton("Business").Set c. Selecting/Deselecting check boxes Syntax:object Hierarchy.Set “ON/off” Ex: Window ("Flight Reservation"). Dialog("Open Order").WinCheckBox("Order No.").Set "ON" Select Method: It is used for selecting an item from a combo box or list box. Syntax: Object hierarchy.select “item” Ex: Window("Flight Reservation").WinComboBox("Fly From:").Select "London" Window("Flight Reservation").Dialog("Flights Table").WinList("From").Select "12572 GetVisibletext: It returns Text from the specified area. Syntax: Variable =object hierarchy.getvisibletext Ex: x=Window("Flight Reservation").WinComboBox("Fly From:").GetVisibleText msgbox x GetRoproperty: It returns current object property value. It can be used for getting any object’s, any property value. Syntax: Variable = object hierarchy.getroproperty (“property name”) Ex: x=Window("Flight Reservation").WinEdit("Tickets:").GetROProperty ("width") msgbox x Navigate Method: It opens a specified URL in the Browser. Syntax: object hierarchy.navigate “URL” Ex: Browser("Yahoo!").Navigate http://www.google.co.in/

Getitemscount: It returns number of items in a combobox. Syntax: Variable=object hierarchy.getitemscount Ex: x=Window("Flight Reservation").WinComboBox("Fly From:").GetItemsCount msgbox x Getcontent: It returns all items from a combobox. Syntax: variable=object hierarchy.GetContent Ex: x=Window("Flight Reservation").WinComboBox("Fly From:").GetContent msgbox x Exist property: It checks whether the object is available or not. Syntax: Object hierarchy.exist(time in seconds) Ex: Window("Flight Reservation").Exist(5)

Data Table Methods

QTP Data Table Methods
(1) Add Sheet: We can use this method to “add” one new sheet to the run time data table. Syntax: DataTable.AddSheet "sheet name" Ex: DataTable.AddSheet "gcreddy" (2) Delete Sheet: We can use this method to “delete” one specified sheet from the Run Time Data table. Syntax: datatable.DeleteSheet (Sheet_ID) Ex: datatable.DeleteSheet (3) (3) GetSheetCount We can use this method to count number of sheets in the run time data table. Syntax: datatable.GetSheetCount msgbox datatable.GetSheetCount (4) GetRowCount We can use this method to count number of rows in the 1st sheet (longest column) of the Run time data table. Syntax: datatable.GetRowCount Ex: msgbox datatable.GetRowCount (5) GetSheet We can use this method to return a specified sheet from the Run Time data table. Syntax: datatable.GetSheet(SheetID) Ex: msgbox datatable. GetSheet(1).GetRowCount (6) Value

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

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

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

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

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

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

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

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

Navigation for Editing standard checkpoint Select Checkpoint statement and right click > choose checkpoint properties option > modify the value > click Ok. Inserting Standard check points through active screen: View > Active Screen >place cursor in desired location >Place mouse pointer on active screen & right click> choose insert standard checkpoint option > click ok > enter expected result > click ok Note: Inserting Standard check points through keyword view same as in expert view. Navigation for Deleting standard checkpoint: Select Checkpoint statements and right click > choose delete option. 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.1. Standard Checkpoint: It checks object property values. We can use this checkpoint for checking any property value. .

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

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

we can customize. If an item is available. If an item is not available then result would be pass 7. XML Check point (from Resource) It checks content of the XML file. according to W3C rules then Pass. . 8. according to our requirements. Result Criteria: a) b) c) If item is available but not according to W3C rules then fail. 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. XML Check point (from Application) It checks content of the XML file.It is a configurable checkpoint.

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

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.

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

. 2) Text output value: We can use Text output values to output text strings displayed in an application. Navigation: Keep tool under recording mode > insert menu >output value > text 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. 3) Text Area output value: We can use text area output values to output text strings displayed within a defined area of the screen. Navigation: Keep tool under recording mode> Insert menu> output value > text 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. When creating a text output value we can output a part of the objects text and we can also specify text before and after options. .We can use standard output values to output the properties values of most objects. 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.

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

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

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

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

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

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

even though some drawbacks are there in using wait statement. Suppose in our test one or more statements only are taking more time for execution then selecting “Inserting synchronization method” is better. . it is better to use wait statement in functions. 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. 2. 3.

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

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

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

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

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

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

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

Ex: Dim a.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. Navigation: Place cursor in desired location >Debug menu>Insert/Remove break point Or Use short cut key (F9) .3) Step Out (shift +F11): It executes all remaining statements in a function at a time.b.

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

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

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

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

various methods for crating and enhancing Tests. Any how Analyzing Results is the Responsibility of Test Engineer after running tests. We can create and execute tests using QTP. If we are using Bugzilla or Zera or PR-Tracker like Bug Tracking tool. After analyzing results. QTP provides result in Result window and also provides a facility to define our own Results. then entering defect details in company prescribed format and sending. Result Exporting facility also available in QTP Result window. In between QTP and Quality Center back to back integration is available. . QTP Provides. we can report defects in various methods. then after analyzing results.Reporting Defects QTP is an Object based Test tool. then we can send defects directly from QTP result window. 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. After Running Tests. 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. Splitting an action: Navigation: Place cursor in desired location>Edit menu>action>split action>Enter Action 1 name & action 2 name. insert. Purpose of Actions: For understandability For reusing components Types of Actions: 1) Non Re usable actions 2) Re usable actions 3) External actions Operations on Actions: • Creating Actions • Splitting Actions • Renaming Actions • Deleting Actions • Calling an Action • Copying an Action • Making an Action Reusable/Non Reusable Creating an Action: Insert>call to new action>enter name of the action>click ok Steps: 1. Create required actions(ex login.delte) 2. Prepare Scripts for those actions. .

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

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

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

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

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

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

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

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

We can define the text string as a regular expression. when creating a text checkpoint to check that a varying text string is displayed on our application. 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.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. Regular Expressions in QTP: Regular expressions can be used in QTP for identifying objects and text strings with varying values. we can set the expected value of an object's property as a regular expression so that an object with a varying value can be verified. They are often used within matching. an Environment parameter value. We can define a regular expression in standard checkpoint to verify the property values of an object. searching or replacing algorithms. Ways of Regular Expressions: . a Data Table parameter value. or a property value in Descriptive programming.

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

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

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

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

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. Navigation:  Select Tools Menu . We can manage the virtual objects defined on our computer using the Virtual Object Manager.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful