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:

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. 3)Lack of expertisation.I. Attributes) Load and Stress Testing Which Software Testing should not be automated? Usability Testing One time testing .U.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.

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

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

.P • 10.5.0) ..0..5 –2008 H..• 9.. -----------------------------------------------------------------------I) Basic Features of QTP ------------------------------------------------------------------------a) QTP Supporting Environments 1) UI (GUI/Windows and Web) 2) Only Windows (Clien side and Server side) b) Version History QTP derived from Astra QuickTest(1.00 –2009 January Overview ---------------------------------------------------------------a) Disadvantages of Manual Testing 1) Huge Amount of Human Resources as well as Environment (Test lab) 2) Time taking process 3) Less Accuracy 4) Tideness b) Advantages of Test Automation 1) 2) 3) 4) 5) 6) Fast Reliable Accurated Reusable Repeatable Comprehensive c) Draback of Test Automation 1) Expensive 2) Technical expertise 3) 100% Automation not Posible d) Types of Test Tool Business cla Technical cla -------------------------------------Vendor Tools Functional & Regression Test tools Opensource Performance/Load/stress Test tools In-House Test Management Tools Defect Management Tools Security Unit Test tools Etc.

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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.Through Debug viewer user can watch variables and change values of variables temporarily. Navigation: view menu> information .

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

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

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

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

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

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

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

Advanced > Go to Function Definition

Navigates to the definition of the selected function.

Advanced > Complete Completes the word when you type the Word beginning of a VBScript method or object. Advanced > Argument Displays the syntax of a method. Info Advanced > Apply "With" to Script Generates With statements for the action displayed in the Expert View, and enables IntelliSense within With statements. Converts any With statements in the action displayed in the Expert View to regular (single-line) VBScript statements. Inserts an optional step (a step that is not required to successfully complete a run session).

Advanced > Remove "With" Statements

Optional Step

View menu: Through this menu we can launch and close, active screen, Data Table, Debug viewer, information, missing resources etc.

Insert Menu: Through this menu user can inserting check points, out put values, synchronizing points.

In this menu step generator available, using this user can generate recordable and nonrecordable scripts.

Through insert menu user can insert VB Script conditional and loop statements and transaction points (Start and End).

Through insert menu user can create new actions, call existing actions and copy existing actions.

Automation Menu: This menu provides Record, Run options and Run setting options Through this menu we can start normal recording, analog recording and Low level recording.

Through this menu we can stop recoding, running and also we run tests.

Command
Record Run

Function
Starts a recording session. Starts a run session from the beginning or from the line at which the session was paused. Stops the recording or run session. Runs only the active action.

Stop Run Current Action Run from Step

Starts a run session from the selected step.

Maintenance Run Starts a run session during which the Mode Maintenance Run Mode wizard opens for steps that failed because an object was not found in the application (if applicable). Update Run Mode Starts a run session to update test object descriptions and other options (if applicable). Analog Recording Starts recording in Analog Recording mode.

Low Level Recording Record and Run Settings

Starts recording in Low Level Recording mode. Opens the Record and Run Settings dialog box, enabling you to define browser preferences for recording and running your test.

Process Guidance Lists the processes that are available for List the current document type and for the currently loaded QuickTest add-ins, enabling you to open them. Results Enables you to view results for a test run session.

Resources Menu:

This menu provides object repository and recovery scenarios options. Through this menu we can create /modify/delete objects information and we can associate repositories. Through this menu we can create, modify and delete recovery scenarios.

Command
Object Repository

Function
Opens the Object Repository window, which displays a tree containing all objects in the current test or component. Opens the Object Repository Manager dialog box, enabling you to open and modify multiple shared object repositories. Opens the Associate Repositories dialog box, enabling you to manage the object repository associations for the test.

Object Repository Manager

Associate Repositories

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

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

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

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.exe" **It launche the Application Ex2: SystemUtil.Dim x.Set "gcreddy" Ex2: Browser("Google").Link("Gmail"). During Recording QTP Creates steps in Keyword view. .com/" vii) VB script other statements Examples: Option Explicit Wait (14) Recording Tests Recording and Running a) Test Recording Process It is a Process of Recording user operations on AUT (Application Under Test)."http://www.Run "C:\Program Files\Internet Explorer\IEXPLORE. and generates them in a script in the Expert view. y.Page("Google").icicibank.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"."mercury") vi) Utility Statements Ex1: SystemUtil.EXE".Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a. Price ii) Object calls Ex1: Dialog("Login"). Simultaneously it adds Objects information into Object Repository.WinEdit("Agent Name:").

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

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

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. they may corrupt. it is possible to begin preparing our . our tests become more modular. So locating errors is difficult • Recorded scripts are QTP internal files.• 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. Additionally.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Database checkpoint: It checks Content of the back end Database.Click ok and stop recording. we can compare complete bitmaps as well as part of the bitmaps. 6. 4. 5. Bitmap checkpoint: It compares bitmaps. Navigation: Insert > checkpoint > Database checkpoint >choose “specify SQL statement manually” option >click next > click create > select machine data source > Select DSN (QT_flight32) > click ok > enter SQL statement (select * from orders) > finish > click ok. Accessibility check point: It checks whether the webpage in our web application is developed according to W3C (World Wide Web consortium) Rules and Regulations or not. . Navigation: Keep tool under Recording mode > 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. Note: here we do not need to put tool under Recording mode and we do not need AUT since data is from backend.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

First. the single quotation mark is a valid VBScript character that has uses beyond delimiting comments. Although most script writers use the single quotation mark. REM This is a comment using the REM statement as a delimiter. 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. it makes a good delimiter. 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. a single quotation mark by itself can be difficult to see at times.Adding Comments Adding Comments to Scripts Comments are statements that are ignored by the script host when the script runs. such a procedure might also retrieve items that are not comments. For example. . we must preface each comment with a comment delimiter. it makes the comment stand out from the rest of the text. you might consider following the single quotation mark with an asterisk when commenting your code: '* This is another comment. This approach has two advantages over the single quotation mark alone. Second. This can be a problem if we use an automated procedure to extract comments from a script.

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

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

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

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

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

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

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

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

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

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

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

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

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

5) msgbox x ' Output: 0/2010 4) StrReverse retuns reverse value of a string Example: Dim 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) .6.5) msgbox x ' Output: 37478 val="H92yderabad" x=Mid(val.val="9247837478" x=Mid(val.5) msgbox x ' Output: 837478 val=#10-10-10# x=Mid(val.1) msgbox x ' Output: H92yderabad x=Mid(9247837478.

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

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

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

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

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.File > settings > Environment > select variable type as user defined > click add icon (+) > enter variable name & Value > click ok (like this we can create number of variables) > click export > browse path & enter file name. Or We can load environment file directly Environment. . 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.

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

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

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

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

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

Virtual objects enable us to create and run tests on objects that are not normally recognized by QTP.Virtual Object Configuration Virtual Object Configuration Virtual Object Configuration: Virtual Object Configuration is a process of making the QTP to treat a specified area or a user defined object as Virtual Object. 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 .

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. Note: QTP doesn’t provide Batch wise result. Steps for Batch Testing: 1). For performing Batch Testing. Navigation: Start>program>quicktest professional>Tools>Test Batch Runner>File>new>batch>add>browse path of the test (like this add number of tests)>save with MTB extension (Module test batche)>close test batch runner. Forming a Test Batch: Launch Test Batch Runner. . 5) View Test wise Result in 'Test Result Viewer'. Create Individual Tests and Run once. 3) Provide permission to 'Test batch Runner' to run tests 4). 2). Run or Execute Test Batches from Test Batch Runner. QTP is providing a separate Tool called Test Batch Runner. Open 'Test batch Runner' Tool and Form Batches.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful