What is Test Suite?

Test suites are normally used to group similar test cases together. The collection of individual test cases that will be run in a test sequence is called a test suite. The collection of individual test cases that will be run in a test sequence until some stopping criteria are satisfied is called a test suite. Test suite preparation involves the construction and allocation of individual test cases in some systematic way based on the specific testing techniques used. Another way to obtain a test suite is through reuse of test cases for earlier versions of the same product. This kind of testing is commonly referred to as regression testing. It ensures that common functionalities are still supported satisfactorily in addition to satisfactory performance of new functionalities. Special types of formal models are typically used to make the selection from existing test cases. Test suite management includes managing the collection of both the existing test cases and the newly constructed ones. At a minimum, some consistent database for the test suite needs to be kept and shared by people who are working on similar areas. Some personnel information can also be kept in the test suite, such as the testers who designed specific test cases, to better supported future use of this test suite.

An object as we know is a graphic user element in an application e.g. a button or a list or an edit box and the special characteristics of an object within the QuickTest are called object properties. QTP stores the recorded object properties in Object Repository. Object Repositories are of two types Local and shared . If objects are stored in a Local Object Repository then these are available to specific actions but not to all the actions. But if these objects are stored in one or more Shared Object Repositories then multiple actions or tests can use them. By default QTP makes and uses Local Object Repository. If we create a new blank test and do a recording on it, QTP automatically creates a Local Object Repository for that test or action and stores the information about any object it finds in that corresponding Object Repository. In QTP 9 we can associate multiple Shared Object Repositories with an action. If multiple Shared Object Repositories are associated with an action then also while recording QTP stores objects in corresponding Local Object Repository on the condition that those objects are not already stored in any corresponding associated Shared Object Repositories. This is the default that every time we create a new action QTP creates a new corresponding Local Object Repository. It is also true that Object Repositories are associated with actions and no matter how many times we learn or record on the same object in our application in different actions the object will be stored as separate test object in each of the Local Object Repository. Local Object Repository is automatically saved with the test when we save it. The extension of the Local

Object Repository is .mtr, but it is not accessible as a separate file as in case of the Shared Object Repository. We can also manipulate some aspects of Local Object Repository using Quick test Object Repository Automation Object Model. For example we can add, remove, rename test objects in Local Object Repository. [QuickTest Object Repository Automation documents the Object Repository automation object model that enables you to manipulate QuickTest object repositories and their contents from outside of QuickTest.] When we open a test that was created using a version of QTP earlier that version 9 we are asked whether we want to convert it or view it in read only format. In any case if the test previously used per-action Object Repository, the objects in each per action repository are moved to the Local Object Repository of each action in the test. If the test previously used a shared object repository, the same shared object repository is associated with each of the actions in the test, and the local object repository is empty. While learning or recording we can specify Shared Object Repository for the selected action. We can specify and associate one or more Shared Object Repositories with each action. We can also create new Shared Object Repository and associate it with our action. In case of Shared Object Repository, QTP uses existing information and does not add objects to the Object Repository if we record operations on an object that already exists either in Shared or Local Object Repository. As said earlier QTP does not add objects directly to the associated Shared Object Repository as we record, instead it adds new objects in Local Object Repository (if that object does not already exist in associated Shared Object Repository). We can surely export Local objects to Shared Object Repository. There are different ways in which we can move objects from Local Object Repository to Shared Object Repository: 1) Exporting the objects to the Shared Object Repository from the Local Object Repository: In Object Repository window choose the action whose local objects you want to move. Choose File-> Export Local Objects.Select the location in which you want to save the file. Click on save. 2) We can update the Shared Object Repository with the Local Object Repository: If we create a new test it will be created with Local Object Repository, we can associate any new or old Shared Object Repository with it, and so we can update that Shared Object Repository with Local Object Repository. In Object Repository Manager open the Shared Object Repository (clear open in read only check box). The test in this case should not be open. In Object Repository Manager go to Tools –> Update From Local Repository. Select the test who's Local Object Repository you want to use. Click update all. It will move all the objects to the Shared Object Repository.

3) We can also merge objects from two Object Repositories (called as primary and secondary in QTP 9) into a new single Object Repository (target Object Repository in QTP 9). The original source files are not changed. It also enables you to merge objects from Local Object Repository of one or more action(s) into a Shared Object Repository. It is recommended to use as a primary Object Repository the file in which you have invested alot of your effort, like which has more number of objects. If we do not specify a file extension for Shared Object Repository when creating a new Shared Object Repository QTP automatically appends a default extension name for Shared Object Repository as .tsr. This means that we can create Shared Object Repository with any extension other than .tsr, it should work fine (I have tried that and it works fine), I think it may create problems while merging two Object Repositories (I haven't tried that yet). We can compare two Object Repositories using the Object Repository Comparison Tool. The tool enables you to identify similarities, variations or changes between two Object Repositories. We can also copy objects to Local Object Repository from the Shared Object Repository. We can copy, paste and move objects in Local Object Repository and copy, paste and move objects within Shared Object Repository and between Shared Object Repositories.As said earlier we can also copy objects from shared Object Repository to Local Object Repository to modify them locally. We cannot remove an association between the action and its Local Object Repository. According to QTP user guide: You can associate as many object repositories as needed with an action, and the same object repository can be associated with different actions as needed. You can also set the default object repositories to be associated with all new actions in all tests. Whenever we make any changes to an Object Repository those changes are automatically updated in all the associated tests open on the same computer as soon as we make the change even if the Object Repository is not yet saved and if we close the same Object Repository without saving the changes the changes are rolled back in any open tests. For the test that was not open when we changed Object Repository, when we open the test on the same machine on which we modified the Object Repository the test is automatically updated with all the saved changes. To see saved changes in a test or repository open on a different computer, you must open the test or object repository file or lock it for editing on your computer to load the changes. Important points about Object Repositories It is a point to consider while planning and creating test that how you want to store objects; either you want to store them in Local Object Repository or Shared Object Repository. 1) For each action, we can also use a combination of objects from the Local and Shared Object Repositories, according to our needs. Local objects can also be transferred to a shared object repository, if necessary. This will cut maintenance and increase the reusability of the tests because it will enable us to maintain the objects in a single, shared location instead of multiple locations. 2) If there is a same name object in both the Local Object Repository and in a Shared Object

Repository associated with the same action, the action uses the local object definition i.e. the local object is given preference over the shared object. If an object with the same name is stored in more than one Shared Object Repository associated with the same action, the object definition is used from the first occurrence of the object, according to the order in which the Shared Object Repositories are associated with the action. 3) When we open an existing test, it always uses the object repositories that are specified in the Associated Repositories tab of the Action Properties dialog box or in the Associate Repositories dialog box. When we access Shared Object Repositories from tests they are read-only; we can edit them only using the Object Repository Manager. 4) As and when an application under test changes, such as when a "Log in" button is renamed "Sign Into," we can make one update to an XML-based Shared Object Repository (within the new Object Repository Manager), and the update will circulate (propagate) to all tests that reference this object. QuickTest Professional keeps object-level changes synchronized among users throughout test creation efforts. Object Repository dialog box Object Repository dialog box window shows a tree of all the objects (either Local or Shared) on its left hand side in the selected action. On selecting any object in the tree Object Repository window shows the information about the object like the name, repository in which it is stored etc. On the left hand side in a tree local objects are editable while the shared ones are grayed out (non-editable). To view the test object properties, to modify test object properties and to add objects to Local Object Repository we can use Object Repository window. We can also delete objects from Object Repository window; this is needed as when an object is removed form the test it is not automatically removed from the Local Object Repository. Object Repository in QTP is XML based means that if we change something related to the object in Shared Object Repository., the change will be propagated to all the tests that reference this object, in real time. Adding Objects to Repositories
[Please see QTP user guide for in-depth information on these below points.]

We can add objects to Shared Object Repository or Local Object Repository in a number of different waysWe can decide whether to add only a selected object, or to add all objects of a certain type, such as all button objects, or to add all objects of a specific class, such as all WebButton objects. We can modify objects stored in a Local Object Repository using the Object Repository Window and objects in a Shared Object Repository using the Object Repository Manager. It is possible to add objects to the object repository before they exist in an application. We can also add objects to the Local Object Repository while editing our test.

We can add objects to the Local Object Repository of the current action by selecting the required object in the Active Screen. 2) Second step in QTP is Creating Tests or Components We can create a test or component by a) Either recording a session on your application or Web site. A test is composed of actions (3 kinds of actions are there in QTP Non-reusable action. We can add objects to the object repository using the Add Objects to Local or Add Objects option. or submitting a data form. which we can use to verify that our application performs as expected. short tests that check specific functions of the application or complete site. Reusable action and External action). Test . A step is something that causes or makes a change in your site or application. If needed. We can also add objects to a Shared Object Repository while navigating through the application ("Adding Objects Using the Navigate and Learn Option"). so that it is available in all actions that use this Shared Object Repository. OR . We can also add an object to the Local Object Repository by choosing it from the application in the Select Object for Step dialog box (from a new step in the Keyword View or from the Step Generator). Decide how you want to organize your object repositories. you should plan it and prepare the required infrastructure. determine the functionality you want to test.We can add the object directly to a Shared Object Repository using the Object Repository Manager. 1) First step is Planning Before starting to build a test. such as clicking a link or image. QTP (QuickTest Professional) lets you create tests and business components by recording operations as you perform them in your application. The Documentation column of the Keyword View also displays a description of each step in easy-to-understand sentences. For example. QuickTest graphically displays each step we perform as a row in the Keyword View. we can merge test objects from the Local Object Repository into a Shared Object Repository. As we navigate through the application or site.A compilation of steps organized into one or more actions.

QuickTest connects to your Web site or application and performs each operation in a test or component. Run test or component to check the site or application. We can use many functional testing features of QuickTest to improve your test or component and/or add programming statements to achieve more complex testing goals. QuickTest substitutes the fixed values in your test or component with parameters Each run session that uses a different set of parameterized data is called an iteration. This enables you to identify whether the Web site or application is functioning correctly. or tables you specified. 3) Third step is Inserting checkpoints into your test or component. We can also set breakpoints to pause the test or component at pre-determined points. 5) Fifth step is running the test After creating test or component. checking any text strings. If we parameterized the test with Data Table parameters. And Step Out commands to run a test or component step by step. objects. When we run the test or component. A checkpoint is a verification point that compares a recent value for a specified property with the expected value for that property. We can also use output values to extract data from our test or component. We can subsequently use this output value as input data in your test or component. we run it. To check how your application performs the same operations with different data you can parameterize your test or component.b) Build an object repository and use these objects to add steps manually in the Keyword View or Expert View. We can use the Step Into. Step Over. When you parameterize your test or component. We can then modify your test or component with special testing options and/or with programming statements. . 4) Fourth step is Broaden the scope of your test or component by replacing fixed values with parameters. Run the test or component to debug it. QuickTest repeats the test (or specific actions in your test) for each set of data values we defined. An output value is a value retrieved during the run session and entered into the Data Table or saved as a variable or a parameter. We can control the run session to identify and eliminate defects in the test or component.

methods of test objects are methods that QuickTest recognizes and records when they are executed (performed) on an object while we are recording. ➤ View the results in the Results window.We can view the value of variables in the test or component each time it stops at a breakpoint in the Debug Viewer. Properties and methods of objects: The property set for each test object is created and maintained by QuickTest. Similarly. ➤ Report defects identified during a run session. Test Object Class Properties Methods A test object is an object that QuickTest creates in the test to correspond to (represent) the actual object in the application. We can instruct QuickTest to automatically report each failed step in the test or component. The property set for each run-time object is created and maintained by the object architect (creator) (Microsoft for Internet Explorer objects. we can report the defects fond out to a database. Netscape for Netscape objects). 6) Sixth step is analyzing the results After we run test or component. we can view the results. A test object class comprises of a list of properties that can individually (uniquely) identify objects of that class and a set of appropriate methods that QuickTest can record for it. After running the test or component. QuickTest uses the stored information about the object during the run session to identify and check the object. A run-time object is the real (actual) object in the application or Web site on which methods are performed during the run session. We can view a summary of the results as well as a detailed report. Methods of Run-time object are the methods of the object in the . or we can report them manually from the Test Results window. we can view the results of the run in the Test Results window. If Quality Center is installed. and that QuickTest executes when the test or component runs. SettingsPrivacyAddThis Test object Model is a set of object types or Classes that QuickTest uses to represents the objects in our application.

application as defined by the object architect (creator). We can access and execute run-time object methods using the Object property. Some important points to remember about methods and properties :  Each test object method we execute (perform) while recording is recorded as a separate step in the test. When we run the test, QuickTest executes (performs) the recorded test object method on the run-time object.  Properties of test object are captured from object while recording. QuickTest uses the values of these properties to identify runtime objects in the application during a run session.  Property values of objects in the application may change .To make the test object property values match the property values of the run-time object, we can modify test object properties manually while designing the test or component or using SetTOProperty statements during a run session. We can also use regular expressions to identify property values.  We can view or modify the test object property values that are stored with the test or component in the Object Properties or Object Repository dialog box.  We can view the syntax of the test object methods as well as the run-time methods of any object on our desktop using the Methods tab of the Object Spy.  We can retrieve or modify property values of the TEST OBJECT during the run session by adding GetTOProperty and SetTOProperty statements in the Keyword View or Expert View. We can retrieve property values of the RUNTIME OBJECT during the run session by adding GetROProperty statements. If the available test object methods or properties for an object are not sufficient or they do not provide the functionality we need, we can access the internal methods and properties of any runtime object using the Object property. We can also use the attribute object property to identify Web objects in the application according to user-defined properties.
qtp.blogspot.com
Bottom of Form

Checkpoints in QTP (QuickTest Professional)
A checkpoint enables you to identify whether the Web site or application under test is functioning correctly or not by comparing a current value for a particular property with the expected value for that property. After we add a checkpoint, QuickTest adds a checkpoint to the current row in the Keyword View and adds a Check CheckPoint statement in the Expert View. By default, the checkpoint name receives the name of the test object on which the checkpoint is being performed. We can change the name of the checkpoint if needed. Types of Checkpoints: 1. Standard checkpoint 2. Image checkpoints

3. Bitmap Checkpoint 4. Table checkpoints 5. Accessibility Checkpoint 6. Text Checkpoint 7. Page Checkpoint 8. Database Checkpoint 9. XML checkpoints Standard checkpoints allow checking the object property values in the Web site or application under test. Standard checkpoints evaluate (compare) the expected values of object properties captured during recording to the object's current values during a run session. For example we can check that a radio button is activated after it is selected. Standard checkpoints are supported for all add-in environments. Standard checkpoints can be used to perform checks on Images, Tables, Web page properties, and Other objects within your application or Web site. Standard checkpoints can be created for all supported testing environments (as long as the appropriate add-in(s) are loaded). Image checkpoints allow you to check the properties of an image in the application or Web page. For example, you can check that a selected image's source file is correct or not. An image checkpoint can also be created by inserting a standard checkpoint on an image object. Image checkpoints are supported for the Web add-in environment With Bitmap Checkpoint we can check an area of a Web page or application as a bitmap. While creating a test, we have to specify the area to check by selecting an object. An entire object or any area within an object can be checked. Bitmap checkpoints are supported for all add-in environments By adding table checkpoints to the test, we can check the content of tables displayed in the application. For example, we can check that a specified value is displayed in a certain cell. Certain environments also support checking the properties of the table object. For example, a check that a table has the expected number of rows and columns. A table checkpoint can also be created by inserting a standard checkpoint on a table object. Accessibility Checkpoint recognizes areas of your Web site that may not conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines. For example, check if the

images on a Web page include ALT properties, required by the W3C Web Content Accessibility Guidelines. Accessibility checkpoints are supported for the Web add-in environment QuickTest can check that a text string is displayed in the appropriate place in an application or on a Web page with Text Checkpoint. Text checkpoints are supported for the Web add-in environment, plus some Web-based add-in environments Page Checkpoint checks the features of a Web page. For example, you can check how long a Web page takes to load or whether a Web page contains broken links. A page checkpoint can also be created by inserting a standard checkpoint on page object. Page checkpoints are supported for the Web add-in environment The contents of a database accessed by your application can be checked by Database Checkpoint. Database checkpoints are supported for all add-in environments By adding XML checkpoints to your test, you can check the contents of individual XML data files or documents that are part of your Web application. The XML Checkpoint option is supported for all add-in environments.
Top of Form

qtp.blogspot.com
Bottom of Form

QTP Tutorials 4 - Standard Checkpoint
Checkpoints cannot be added manually, they are inserted using QTP's interface. Results of the checkpoint can be viewed in the Test Results Window. Checkpoint information is stored in the Local Object Repository. It is in the Resource.mtr file which is in the action folder (if you created checkpoint in action1 then it will be action 1 folder under the folder in which you are saving the test/script, if you created checkpoint in action 2 then it will be action 2 folder and so on) . In the expert view, on any blank line type Checkpoint and put "(". As soon as you put the starting bracket it will show all the checkpoints you have used in the test. Now we will start with checkpoints. I will try to show easy to understand example of each and every checkpoint. Lets start with simple example of standard checkpoint which checks a variety of objects such as buttons, radio buttons, combo boxes etc. Standard checkpoints are supported for all add-in environments 1. Open a blank test.
2. Make sure that Flight application is open.

(Now only QTP with blank test and Flight application should be open). 3. Click on Record. When we click on Record, "Record and Run Settings" window opens up. Go to "Windows Applications" tab and choose first option "Record and run test on any open Windows based application." and click ok. 4. Go to Insert (menu)->Checkpoint->Standard Checkpoint (or press F12).The mouse pointer will become hand and QTP will be minimized.

5. Click on the "Flights..." button which is on the Right Hand Side of the "Fly To" combo box in the Flight application. 6. It will open "Object Selection - Checkpoint Properties" window (with WinButton:FLIGHT highlighted). Click ok. 7. It will open checkpoint properties window. (only one property will be checked in it i.e. 'enabled' with a value of False.) 8. Click ok. Click on Stop in order to stop the Recording. 9. Save the test. This is a small test in which we have used standard checkpoint and captured the disabled button on the Flight application. Now we can run the test in two ways to see how it fails and passes the results of the checkpoint. To see a pass test result: Make sure that this test and Flight application is open. Click on run. It will Run the test and show you the result as pass. To see a Fail test result: Make sure that this test and Flight application is open. In the Flight application enter the Date of Flight, Fly From and Fly To fields and nothing else. (The reason for doing this is that it will enable the 'Flight...' button) Click on run in order to run the test. It will Run the test and show you the result as Fail. This is because QTP was looking for a disabled 'Flight...' button for which it recorded the information at the record time, but now since the button was enabled at run time, so it failed.
qtp.blogspot.com

This will help you in understanding the standard checkpoint in QTP more deeply.
Bottom of Form

Simple example of QTP Existing Checkpoint
QuickTest (QTP) now makes it possible for you to reuse an existing checkpoint in your test. For example you can use bitmap checkpoint to verify your company's logo on each page of your application or website. Let’s see a very simple example to accomplish this.

Checkpoint Properties window opens. 13. Click on the ‘+’ sign to locate the shared Object Repository and associate it. Object Selection .. qtp. Click on the Flights. Go to Resources->Object Repository (OR associated with this particular action will open) 9. (Standard checkpoint will be added) 7.) 2.g. Existing Checkpoint will be enabled to let you insert any checkpoints already saved to the shared Object Repository (Rep1 in our case). Open a new test and Save it with the Name testtwo. Go to File-> Export and Replace Local Objects (Export Object Repository dialog opens) 10. 8. Now (in testtwo) you can see when you go to Insert-> Checkpoint. 12. right click on action 1 and choose Action Properties. 3. Save the test as testone. 14. Checkpoint Properties window opens.blogspot. Open a new test (Make sure that Flight Reservation Window in open. 6. Click Stop in order to stop recording. 5. Click OK.1. button which is on the right hand side of Fly To dropdown.) 4. Click OK. Go to Insert->Checkpoint->Standard Checkpoint. rep1 and click Save (All the objects in Local Object Repository will be grayed) 11.com . Close that Object Repository. Associate Shared Object Repository Rep1 with it also. (If it asks for Automatic Relative Path Conversion Click Yes) Click Ok to close that Action Properties window. (QTP will be minimized and mouse pointer will take the shape of a hand. (If not already associated) In the keyword view. Click on Record in order to start recording. Enter any filename e. Go to Associated Repositories tab..

co. Let all the options be default. 7. Click on 'Page : Google' option which has a page icon on left of it with right corner of the page slightly folded. Click anywhere on the white space on the Google.co. broken links etc.Checkpoint Properties" window.in in offline mode (not on internet).google. Click ok.Page Checkpoint Page checkpoint:It is for web applications only. The mouse pointer will become hand and QTP will be minimized.Common things to check with this are load time. Make sure thathttp://www. Open a blank test.Bottom of Form QTP Tutorials 5 . on left hand side. 9. A 'Page Checkpoint Properties' window opens up. When you run it. In the Expert view it will add just one line: Browser("Google").google. Click on Stop in order to stop the Recording. It recorded the following properties: Property Name load time number of images number of links Property Value "0" "2" "20" Here it shows the load time as 0 because I did not open Google at the time of running the test.com it may fail. 6. It will Open "Object Selection .in/ is open. When we click on Record. Go to Insert (menu)->Checkpoint->Standard Checkpoint (or press F12).(Now only QTP with blank test and www. 10. Click on Record. it will show (when every option is expanded): Test Checkpoint-page Summary (where Checkpoint-page is the name with which I saved the test Run-Time Data Table Checkpoint-page Iteration 1 (Row 1) Action1 Summary Google (This will be the browser) Google (This will be the Page) Checkpoint "Google" If you run this test on www." and click ok. 2. I ran this test by opening www.in page. 5.google.co. 8. 1.in should be open. 4.co. . it was already open. "Record and Run Settings" window opens up. in the results window.Check CheckPoint("Google") We will explore this line later on. Click ok. Go to "Web" tab and choose first option "Record and run test on any open browser.google.) 3.Page("Google").

Go to "Windows Applications" tab and choose first option "Record and run test on any open Windows based application. Click 'Test Connection' Button. Click on Record. 14. 7. If successful it will show 'Testing Connection' window with 'Connection Successful' written on it. Enter 'description' (I entered "SQL") 12. "Record and Run Settings" window opens up. 9. Select Oracle (on my machine it was 'Oracle in OraHome9'). Enter your password for Oracle. 13. 15. Select 'User Data Source' from Select a type of data source. 3. Go to Insert (menu)->Checkpoint->Database Checkpoint . 10. Open a blank test.blogspot. Click on 'Machine Data Source' Tab 4. It will show all the data source drives it could find. It will open 'Oracle ODBC Driver Configuration' window.com Bottom of Form QTP Tutorials 6 . 'Create New Data Source' window opens. 2. Enter 'Data Source name' ( I entered "oracle") 11. 1. Click Next. Click Finish. For this go to Insert -> Checkpoint -> Database Checkpoint.(before doing any recording) 1. A Database Query Wizard opens. 6. Now we will record a test. 2.It will ask for a Password. When we click on Record. Click Next. Click Next. This completes our task of Connecting QTP with Oracle. Select ' Specify SQL statement manually' from the Query definition area.qtp. 3." and click on ok. Enter userid (I used SCOTT). 8. Here click on 'Create' button which is on the right of "Connection String:" It will open 'Select Data Source' window. Click on New Button. my oracle database name) from combo box.Database Checkpoint Now we will try out Database checkpoint: using Oracle 9i First of all you have to connect oracle 9i to QTP 9. Select 'TNS Service Name' ( I selected 'DB02'. 5.

It will open 'Database Checkpoint Properties' window with the result of the query. Click Ok. Click Finish. Click on Run. 5.PFC=10.UID=SCOTT. Click Stop in order to stop the Recording.com Bottom of Form . Lets run it.blogspot. It will come to Database Query Wizard window with 'Connection String' field filled with: "DSN=oracle. Click Next.". Enter password.4.FRC=10. with the count of cells. Click Ok. ( we don't need to open any other window or application to run this as our Oracle is running at the back end as a service .EXC=F.FEN=T.QTO=T.FWC=F. 12.DBQ=DB02.PWD=TIGER.RST=T. A 'Database Query Wizard' opens.DBA =W. qtp. It means if you go to the oracle and add or delete any row and run this test again it will fail.GDE=F." In the SQL Statement area type "select * from emp.FDL=10. Select ' Specify SQL statement manually' from the Query definition area. 10.APA=T. it just adds one line "DbTable("DbTable"). Select Oracle from data source name.Check CheckPoint "DbTable")" This is the simplest database checkpoint example. 11.) When it is passed it will show following in the Result window: Test Checkpoint-database Summary (where Checkpoint-database is the name with which I saved the test) Run-Time Data Table Checkpoint-database Iteration 1 (Row 1) Action1 Summary DbTable Checkpoint "DbTable" ( when you click on this.TLO=0.CSR=F.MTS=F. In the Expert View. Click Create. LOB=T. Click ok 9. Go to 'Machine Data Source' Tab 7. in details it will show checked 112 cells (in your case number of cells may differ). 6.FRL=F.BAM=IfAllSuccessful. It will open 'Oracle ODBC Driver Connect' 8.) Just try to think how QTP is comparing the expected results with the actual one. MDI=F.nothing special.default way in which it was installed.

instead of clicking on the "Fly To" combo box. Click on the "Fly To" combo box. 9. "Record and Run Settings" window opens up. Go to Insert (menu)->Checkpoint->Bitmap Checkpoint 4. (note: it will show that only in case of Failed result) .. 5. Go to "Windows Applications" tab and choose first option "Record and run test on any open windows based application. "Object Selection. Open a blank test. When we click on Record. Click ok 6. It will have "WinObject:Flight Schedule" highlighted. To see how it stores the results. so that we will have no wait time while running the test. Click on Record. 8." and click Ok. STYLE A 1. It will open "Bitmap Checkpoint Properties" window. so that we will have no wait time while running the test. I will have "WinComboBox:Fly To" highlighted. click somewhere in the empty space above the "Fly From" Combo box but below the line. Click ok. If you have recorded in the style A then just select any value in the "Fly To" combo box and then run the test. Mouse pointer will change so that you can select any area by dragging.QTP Tutorials 7 . in the "Flight Schedule" area. Now you can run the test it will pass. This time it will have "Flight schedule" area instead of just the "Fly To" combo box. it will show you the expected bitmap and actual bitmap on the right hand side. i. Now click on the "Select Area. Make sure that QTP and the Flight application are open. Click stop to stop recording the test. "Object Selection." button.Bitmap Checkpoint Properties" window opens up. Click ok It will open "Bitmap Checkpoint Properties" winodow.. STYLE B Above. Change the "Checkpoint timeout" at the bottom of the window to 0 seconds. Click ok. 3.Bitmap Checkpoint Properties" window opens up.Bitmap Checkpoint Now we will look at the bitmap checkpoint which is different from the image checkpoint. In the result window on the left hand side when you click on Checkpoint "Fly To:". Just select "Fly From" combo box by dragging.e. just fail the test. 2. after 3rd point. Change the "Checkpoint timeout" at the bottom of the window to 0 seconds. Click stop to stop recording the test. 7.

Check CheckPoint("Sunset") If you run it with that image open in internet explorer it will pass.Sample Pictures( containing 4 pictures . Go to Insert (menu)->Checkpoint->Standard Checkpoint(or press F12). "Record and Run Settings" window opens up. In this way you can test for some or all the properties of the image which it showed in the 'Image Checkpoint Properties' Window. On your system under My Documents. Go to My Documents->My Pictures-> Sample Pictures and right click on image named 'Sunset' and open it with internet explorer. Rest every thing will be default. It will Open 'Image Checkpoint Properties' Window.blogspot. If you change the name of some other picture in that folder to Sunset and run the test with that it will also pass. Go to "Web" tab and choose first option "Record and run test on any open browser.qtp." and click on Ok. When we click on Record.The mouse pointer will become hand and QTP will be minimized. It will open 'Object Selection Checkpoint Properties' window with Image: Sunset highlighted.blogspot. Click on Record.com Bottom of Form . In this window just uncheck all the property values like href. QTP Tutorials & Interview Questions qtp. Water lilies) We will run this test with one of the image there. under this you will will find a folder. html tag etc and only check last property which is src. In the expert view it will just add one line Browser("file:///C:/Documents%20and %20S").Sunset. It is just checking that the image in the explorer is in the same location in which it was when the test was recorded and its name is Sunset. Click stop to stop recording the test. Now only a new blank test and internet explorer with this image should be open. Click OK. Click Ok. Sunset.Image Checkpoint We will look at the Image checkpoint.Page("file:///C:/Documents%20and%20S").Image("Sunset"). This test is not intelligent enough. Winter.Blue Hills. there will be a folder named My Pictures. Open a blank test. Click on the image which is opened in the explorer.com Bottom of Form QTP Tutorials 8 .

Checkpoint properties" window opens. Click on Record. Click on stop in order to stop recording.. Again Click ok to come out of "Text Checkpoint Properties" window. "Record and Run Settings" window opens up.editorial. qtp. Click on Record. Select "WebTable: Software Testing Life Cycle" which has a table icon on its left.blogspot.QTP Tutorials 9 . Go to Insert (menu)->Checkpoint->Standard Checkpoint (or press F12). 3.php" in offline mode. but for now just click ok. 6. change before and after text and so on. This website has a table at the bottom of the page. It will show the text to be checked in "Checkpoint Summary" area in red color and also show in blue color the text which is displayed before and after the selected text. Go to "Web" tab and choose first option "Record and run test on any open browser. . At the bottom of the "Text Checkpoint Properties" window change 'Checkpoint timeout' to 0 seconds." and click on ok.co. Go to "Web" tab and choose first option "Record and run test on any open browser. Go to Insert (menu)->Checkpoint->Text Checkpoint. 4. Try to understand those. Click ok. The mouse pointer will become hand and QTP will be minimized. "Object Selection . When we click on Record. On the right hand side it will show you the details.in/software/software-testinglife-cycle. 5. Run the test and when it is passed just go to the results window and on the left hand side just expand every option and click on last option Checkpoint "Cannot find server". When we click on Record.Text Checkpoint Now we will look at the Text Checkpoint: 1.The mouse pointer will become hand and QTP will be minimized. "Text Checkpoint Properties" window opens up. Click somewhere inside the table.Click on the first paragraph (which starts with-The page you are looking.Table Checkpoint In this tutorial we will look at a table Checkpoint just to get familiar with it. where "Software Testing Life Cycle" is the name of the table. Click on Configure -here you can change your selected text. Open a blank test and a web page in offline mode like this below: 2." and click on ok. "Record and Run Settings" window opens up.) of that web page.com Bottom of Form QTP Tutorials 10 . Open a blank test and also open a website "http://www.

WinButton("FLIGHT"). mainly the checkpoint results to see how QTP verifies the result.com Bottom of Form Difference Between Text & Text Area Checkpoint Text Checkpoint Text Checkpoint checks that a text string is displayed in the appropriate place on a Web page or application. We will manipulate test results in later tutorials. qtp. Window("Flight Reservation"). So the final version looks like this: Dim return return = Window("Flight Reservation"). In the expert view of the test you will see only one line i. Open that test that contains the standard Checkpoint. Lets now capture it.WinButton("FLIGHT").e.Check CheckPoint("FLIGHT") msgbox (return) One thing more we need to do here is that we have to enclose Checkpoint ("FLIGHT") in brackets. This time we will not do any extra setting.'Table Checkpoint properties' window opens. It will show all the rows and columns of the selected table.WinButton("FLIGHT").blogspot. . according to specified criteria.blogspot. Just change the Checkpoint timeout at the bottom of this window to 0 seconds and click ok . qtp.Check CheckPoint("FLIGHT") Now we will make some changes in this one line so that it can return some value. Text Area Checkpoint Text Area Checkpoint checks that a text string is displayed within a defined area in a Windows-based application. Run the test and analyze the results in the result window. Declare a variable and catch the return value in that variable: Dim return return = Window("Flight Reservation"). NOTE: Checkpoint always returns a value.Check (CheckPoint("FLIGHT")) msgbox (return) Now run the test and see the msgbox appearing with the return value.Checkpoint Return Value We will use the Standard Checkpoint which we did in tutorial 4. Click stop in order to stop recording.com Bottom of Form QTP Tutorials 11 . it depends on us whether we capture it or not.

A small & simple example to get a feel of both Text and Text Area Checkpoint: Make sure that the Flight Reservation window is open as shown below. Go to Insert (Menu) ->Checkpoint->Text Checkpoint QTP will be minimized and the mouse pointer will change into pointing hand. Text Checkpoint Properties window opens. (See Screenshot for Text Checkpoint Properties window below). and ActiveX. Java. as Standard Windows. Visual Basic. Click Cancel.recording a test on Windows-based applications.00 in the above Flights Table. Click OK. . Object Selection window opens.You can add a text checkpoint while You can add a text area checkpoint only while recording or editing steps in a Windows. Open a New test in QTP and click Record. Go to Insert (Menu) ->Checkpoint->Text Area Checkpoint QTP will be minimized and the mouse pointer will change into crosshairs. With the pointing hand click on $110. such or Web-based application.

Object Selection Window for "Text Area checkpoint" will also be similar as the below one for "Text Checkpoint": Text Checkpoint Properties window [In Windows-based environments.With the crosshairs select $110. Click OK. Click Cancel. Object Selection window opens. (See Screenshot for Text Area Checkpoint Properties window below). You can then click Configure to view and manipulate the actual selected text for the checkpoint.00 in the above Flights Table.] Text Area Checkpoint Properties window: . if there is more than one line of text selected. the Checkpoint Summary area displays [complex value] instead of the selected text string. Text Area Checkpoint Properties window opens.

QuickTest records all parent level objects as Window test objects and all other objects as WinObject test objects. analyze yourself: Which one is better (if any) and Which one is to be used in which situation? qtp. Each step recorded in Low Level Recording mode is shown in the Keyword View and Expert View. if an environment or on an object not recognized by QuickTest. Analog Recording : Exact mouse and keyboard operations are recorded in relation to either the screen or the application window. In this QTP also records and tracks every movement of the mouse for example. Low Level Recording : At any time. use Low Level Recording. . Analog Recording steps are not editable from within QuickTest. Normal mode is the default and takes full advantage of the QuickTest test object model.com Bottom of Form QTP (QuickTest Professional) Recording The default mode of recording is the Normal recording mode. recording a signature produced by dragging the mouse. There are other recording modes also like Analog Recording or Low Level Recording.Now considering both Text and Text Area checkpoints. as it recognizes the objects in the application regardless of their location on the screen. It records at object level and records all run-time objects as Window or WinObject test objects.blogspot.

To use a value within a specific action. For example. Analog Recording and Low Level Recording require more disk space than normal recording mode. It is known as parameterization. Parameters let us check how the application performs the same operations with multiple sets of data. Recording in Analog mode can be relative to the screen or relative to a specific window (see user guide for detail) In Analog Recording a separate file is saved and stored with the action.blogspot. Exact location of the operation on your application screen is necessary. Use Analog Recording when : The actual movement of the mouse is what you want to record. QuickTest adds to your test a RunAnalog statement that calls the recorded analog file.com Bottom of Form Parameterizing Tests in QTP (QuickTest Professional) By replacing fixed values with parameters QuickTest enables you to enlarge the scope of a basic test. Action parameters enable us to pass values from other actions in your test.g. in normal mode QuickTest performs the step on an object even if it has moved to a new location on the screen. If the location of the object is important to your test. the value must be passed down through the action hierarchy of the test to the required action. we can switch to either Analog Recording or Low Level Recording in the middle of a recording session for specific steps and then return to normal recording mode. In Analog Recording mode. Use Low Level Recording when : Environments or objects not supported by QuickTest. We can then use that parameter value to parameterize a step in the test. A parameter is a variable that is assigned a value from an external data source or generator. There are four types of parameters: Test/action parameters: Test parameters make possible for us to use values passed from the test. greatly increases the power and flexibility of a test. suppose that we want to parameterize a step in Action3 using a value that is passed into the test from the external application that runs (calls) the test. We can pass the value from the test level to Action1 (atop-level action) to Action3 (a nested action of Action1). and then parameterize the required step using this action input parameter value (that was passed through .All the three modes of recording can be used in a single test e. switch to Low Level Recording qtp. Values in steps and checkpoints and also the values of action parameters can be parameterize.

suppose that Action2. Action3. Environment variable parameters allow us to use variable values from other sources during the run session.from the external application). Parameterizing the value of a checkpoint property enables us to check how an application or Web site performs the same operation based on different data qtp. This column shows a hierarchical icon-based tree. and all steps are contained within the relevant branch of the tree. In the keyword view there are 4 visible columns – (For other valuable information on below points please see QTP user guide pg 92 and pg 114) Item The item on which we want to perform the step and it can be a test object. and generates them in a script (in an Expert View). then run a test and then analyze the results. and Action4 are sibling actions at the same hierarchical level. Therefore. all occurrences of the specified object within the action are parameterized. Values in steps and checkpoints can be parameterized while recording or editing the test. QuickTest displays them as steps in the Keyword View. After recording all the operations. we can pass an output action parameter value from an action step to a later sibling action at the same hierarchical level. we are amending the test object description in the local object repository.blogspot. In each repetition. QuickTest uses a different value from the Data Table. Operation The operation (methods or functions) to be performed on the item selected in the Item column. The values of the operation (method or function arguments) defined for the step can also be parameterized. We can then use these parameters in the action step. The highest level of the tree is actions. function call. First of all let's talk a little about keyword view in QTP and then we will talk about recording in QTP and then we will move on to other things. When the value of an object property for a local object is parameterized. but before running the test we can also enhance it with checkpoints and parameters. for example. We can parameterize a call to Action4 based on an output value retrieved from Action2 or Action3. Random number parameters Enable us to insert random numbers as values in your test. or values that QuickTest generates for us based on conditions and options we choose. For example. or statement. Data Table parameters allow us to create a data-driven test (or action) that runs several times using the data that we supply. These may be values that we supply. Click or Select. Alternatively. .com Bottom of Form QTP (QuickTest Professional) keyword view In QTP (QuickTest Professional) we first of all record a test. or iteration. utility object. The values of object properties can be parameterized for a selected step. and that these are all nested actions of Action1.

An action is stored with the test in which you created it. This column is not visible by default. check inbox. By breaking up the tests into calls to multiple actions. Click the "findFlights" image. modify.com Bottom of Form Actions in QTP 9 (QuickTest Professional) Actions break up the test into logical sections/units such as specific activities that we perform in our application. qtp. They also make it easier to re-record steps in one action when part of your application changes. This column is also not visible by default. If you create a test in which you log into the system (email). For every action called in the test. and all objects in its local object repository. your test might be structured as shown—one test calling three separate actions: Test 1 Call to action 1 Call to action 2 Call to action 3 Actions stored with Test 1 Action 1(Logging In) Action 2(Checking Inbox Mails) Action 3(Logging Out) ---> ---> ---> Actions make it possible to parameterize and iterate over specific elements of a test. containing all of the steps recorded in that action. Three types of actions are: Non-reusable action This non reusable action can be called only once and that too in the test with which it is stored. the mouse button to use when clicking the image. for example. Comment Any textual information you want to add regarding the step. Store in cCols would store the return value of the current step in a variable called cCols so you can use the value later in the test. and enhance the steps . Assignment The assignment of a value to or from a variable for example. When we create a new test. Documentation It is a Read-only auto-documentation of what the step does in an easy-tounderstand sentence. we can design more modular and well organized and professional tests. An action has its own test script. we can record. for example. QuickTest creates a corresponding action sheet in the Data Table so that we can enter Data Table parameters that are specific to that action only.blogspot. Reusable action Reusable actions are like functions in any programming language. and then log out of the system (email). If there is a process that needs to be included in several tests. it contains a call to one action.Value The argument values for the selected operation.

as well as by other tests. modifying. Wait is like forcing the QTP to wait for a specified amount of time while synchronization is not a 'forced' wait e. Examples where synchronization can be used: For a web page to load. QTP will generate a WaitProperty statement in the Expert View in case of synchronization. Then we can call the action from other tests. When we run a test with multiple actions. and can view the detailed results for each action individually. External action is a reusable action stored with another test. rather than recording. Synchronization is possible in many ways: 1) We can insert a synchronization point for example for a progress bar to reach 100%. By default. and enhancing the same steps each time.g. Synchronization is there to take care of the timing problems between QTP and the AUT. if the wait is for 10 seconds and a webpage loads in 3 seconds then it still waits for 7 seconds. you should use relative paths for your reusable actions so that other users will be able to open your tests even if they have mapped their network drives differently. but we can choose to use a local. the test results are divided by actions within each test iteration so that we can see the outcome of each action.com Bottom of Form QTP Sync. whenever a specific page loads QTP moves forward in case of synchronization. qtp. Each action created in a test can be marked as reusable or non-reusable. but in case of wait. External actions are read-only in the calling test. When a call to an external action is inserted. If you expect other users to open your tests and all actions in your tests are stored in the same drive. It can be called several times by the test with which it is stored (the local test). editable copy of the Data Table information for the external action. new actions are non-reusable. Wait and Synchronization Synchronization makes available specified amount of time for an object to process prior to moving on to the next step. . the action is inserted in readonly format We can create an additional call to any reusable or external action in the test by pressing CTRL while we drag and drop the action to another location at a parallel (sibling) level within the test. For a button to become enabled or disabled.of the process and save them in a reusable action. For client-server communications to finish.blogspot. Deleting a reusable action that is called by other tests will cause those tests to fail.

Go to Insert (menu)-> Synchronisation Point.. .' text in the Flight application. Click on Flights..H. Enter your name in the Name field. Click on that 'Insert Done. 3) We can also modify the default amount of time that QTP waits for a Web page to load. QTP will be minimized and cursor will take the shape of a hand. Go to "Windows Applications" tab and choose first option "Record and run test on any open windows based application.2) We can use Exist or Wait statements. "Record and Run Settings" window opens up. Exist statements always return a Boolean (0 or 1) value.blogspot.." (Don't forget to put those 3 dots. When we click on Record.. In Flight application go to File (menu)-> New Order. 'Object Selection .' selected. (Browser Navigation Timeout.' text... " in the Property value text box. In Fly From choose Denver.com Bottom of Form Example of Synchronization Make sure that only QTP and Sample Flight application are open. File(menu)-> Settings-> Run tab) Synchronization is enabled only during recording. (Object Synchronization Timeout. It will automatically fill some of the fields. Choose Property name as 'text' and Property value as "Insert Done.) Click Ok. Click Ok. 'Add Synchronization Point' window will open..S of the Fly To combo box. we can increase the default timeout settings for a test to instruct QuickTest to allow more time for objects to appear. Let the first option remains selected in that and just click on ok.g." and click on ok. button which is on the R.Synchronization Point' window will open with 'ActiveX: Threed Panel Control. Click on Insert Order and let it complete uptill 100% untill you see the 'Insert Done. qtp. Click Stop in order to stop the recording.. Click on Record. Flights Table window open up. In Fly To Choose Frankfurt. and double quotation marks e. Enter the Date of flight as tommorrows date. File(menu)-> Settings-> Web tab) 4) When working with tests.

Select "Frankfurt" Window("Flight Reservation").Select "Denver" Window("Flight Reservation"). "Insert Done.Dialog("Flights Table").ActiveX("MaskEdBox").Set "axc" Window("Flight Reservation"). WaitProperty Waits until the particular object property attain the specified value or exceeds the specified timeout before continuing to the next step.Click Window("Flight Reservation")..WinComboBox("Fly From:")..Select "Denver" Window("Flight Reservation").Type "092407" Window("Flight Reservation").".".Click Window("Flight Reservation").ActiveX("MaskEdBox").Click Window("Flight Reservation"). "Insert Done.WinComboBox("Fly From:").WinButton("FLIGHT").WaitProperty ("text"..WaitProperty "text".Select "Frankfurt" Window("Flight Reservation").Click 1.Click 1.com Bottom of Form Example of WAIT Make sure that only QTP should be open..Click rc=Window("Flight Reservation").WinButton("Insert Order").Type "092407" Window("Flight Reservation")."sync on Insert Done. ReportEvent method sends the results to the result window.ReportEvent micPass.WinEdit("Name:").Set "axc" Window("Flight Reservation"). Window("Flight Reservation").ActiveX("MaskEdBox"). 10000) If rc=true Then reporter.Click qtp. The code in the Expert view looks like this: Window("Flight Reservation").WinButton("OK").WinComboBox("Fly To:").This whole process will add WaitProperty.WinComboBox("Fly To:").Click I have modified the above script a little bit to capture the WaitProperty value..Click Window("Flight Reservation")..WinEdit("Name:").WinButton("Button").WinButton("FLIGHT").WinButton("OK").WinButton("Insert Order").". For more info on these plase see QTP help. "Property of text is true" End If msgbox rc Window("Flight Reservation").ActiveX("Threed Panel Control").Dialog("Flights Table").9 Window("Flight Reservation").ActiveX("Threed Panel Control").WinButton("Button"). .ActiveX("MaskEdBox"). 10000 Window("Flight Reservation").9 Window("Flight Reservation").Click Window("Flight Reservation"). Reporter is an Object used for sending info to test results and it uses ReportEvent method to accomplish this.blogspot.

Click 7) Window("Flight Reservation")..google. Open internet explorer (make sure your default page is www.exe".com Bottom of Form Example of Sync Make sure that your internet is On and QTP is open. "Record and Run Settings" window opens up.SetSecure "46ed14b628c7ae93e3a3ab35576f08fc424a6fb9" 6) Dialog("Login"). 1)SystemUtil.WinEdit("Agent Name:").) Type Blogger in the search text box and click on "I'm Feeling Lucky" button instead of Search button. when you see 'Done' on the status bar at the bottom) . Enter Username as your first name (make sure to enter 4 or more characters).com as homepage.blogger.WinEdit("Password:").' Click Ok. click on Back toolbar button (below File menu) to go back to google. .Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a. Go to Start->AllPrograms->QuickTest Professional->Sample Applications->Flight.Type micTab 4) wait(5) 5)Dialog("Login"). When Flight Reservation window is open. Click on Record."open" 2) Dialog("Login").com is open (i. Go to "Web" tab and choose first option "Record and run test on any open browser. When www.WinMenu("Menu").WinButton("OK"). When we click on Record." and click on ok.) Enter password as 'mercury." and click on ok.WinEdit("Agent Name:").Set "sachin" 3) Dialog("Login").e. It will record the code as below but one thing which I have added extra is Wait(5) in step 4 (just go to the expert view and add this line before the line which includes encrypted password). go to File(Menu)->Exit. so that when you open internet explorer.com.Exit" qtp.com again. It will record the following code with sync automatically recorded by QTP (see 4th step)."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\". it by default opens google.Click on Record. When we click on Record.blogspot. Go toFile(Menu)->Exit. "Record and Run Settings" window opens up."". (use tab to move to password textbox. Go to "Windows Applications" tab and choose first option "Record and run test on any open windows based application.Select "File.

WebEdit("q"). Now go to File(Menu)->Settings. This is just to give you a startup on parameters in QTP. it works fine.WinMenu("ContextMenu").Set "blogger" 3) Browser("Google"). after the 3rd step it just waits for 2 second after which it goes to the Back button.WinToolbar("ToolbarWindow32")."".Select "Close" Try to run this code.Back 6) Browser("Google").e.Click 4) Browser("Google").blogspot."open" 2) Browser("Google").Sync 5) Browser("Google").blogger.EXE"."C:\Documents and Settings\Sachin". It will fail because sync method waits for the browser to complete the current navigation.Press "&File" 7) Browser("Google"). Keep 'Browser navigation Timeout' to 10 seconds in File(Menu)->Settings and then it should pass because in 10 seconds it surely makes the back button enabled after the 3rd step of clicking "I'm Feeling Lucky". because what happens is.com is open. Environment Variables in QTP Random Variables in QTP Test parameters Action Parameter Global and Action data sheet Parameters QTP Output Values Parameterize a checkpoint . to open www. but here we have set the browser navigation timeout to 2 seconds.Page("Blogger: Create your Blog").Page("Google").com after clicking on "I'm Feeling Lucky" button (I am not on T1 lines. qtp.1)SystemUtil\Program files\Internet Explorer\IEXPLORE. which is too short for a browser to complete the navigation i.blogger. but it finds it disabled as it gets enabled only when www. my internet connection is average).com Bottom of Form QTP Parameters This is not an exhaustive material on parameterization.WebButton("I'm Feeling Lucky"). so that you can go ahead and do wonders with parameters in QTP on your own.Page("Google"). Web tab and change the 'Browser navigation Timeout' to 2 seconds for example and then run the above code again.

Lets look at an example of this: 1. 7. a Test Settings window opens. Open a new Test. .g. It will add the variable with its type as 'internal'. 2.blogspot. 2. Open a new Test. It is just a simple way to show how a Built-in environment variable works. 5. 4. 4. respectively. ActionName which are for Operating System. 3. 5. Operating System Version and name of the action which is currently running.com Bottom of Form QTP Environment Variables User-Defined Internal. Now close this Test Settings window and go to test. And Run the test. Go to Environment Tab. It will show you the value of variable 'a' in the message box.Go to File (Menu)->Settings. Go to Environment Tab. 6. Click Apply and OK to come out of Test Settings window. Now Run the test.qtp. in Name type 'a' and in Value type 'hello' (without quotes. From Variable type dropdown select User-defined. 7. Built-in variables as the name suggests are predefined by QTP. OSVersion. User-Defined External. Built-in are the types of environment variables available in QTP. I have added quotes just for clarity) and click on OK. type the name and value of the variable e. Go to File (Menu)->Settings. Examples of such variables are OS. Lets look at an example of this: 1. I just did the above four steps in order to show you from where you can access Built-in variables. User Defined Internal variables are the variables defined by you (the user) within the test and which are saved within the test and also accessible from within the test. 6. By default Built-in variable type is selected and you will be able to see Name and Description of Built-in variables below Variable type dropdown box. Go to expert view and type: msgbox(environment("a")) 8. You can click on any of those variables to see their current value. 'Add New Environment Parameter' window opens up. a Test Settings window opens. 3. In the Expert View type: a = environment("ActionName") & " is running on " & environment("OS") msgbox (a) 8. Click on the '+' which is on the right of Variable type dropdown.

It will open 'Value Configuration Options' window. You can create as many files for environment variables as you want and choose them for your test. select 'Action Call Properties'. 2. 3. 4. 3.User-Defined external variables are the variables which are defined in the file outside of test.blogspot. Click Ok. There are many different ways in which you can use Random numbers in QTP. Again right-click on Action1 in the keyword View . 4. In the keyword View right-click on Action1. Go to Environment Tab. Click on "Load variables and values from external file" check box and import that external xml file that we created above. Open a new test. As soon as it is imported the complete path of that file will be shown in the File text box and the variable in it will show under Name. Go to File (Menu)->Settings. 6. Now lets look at an example of this: Open a new text file and type the following lines in it and save it with . 5. 6. Lets jump at the examples straightway.) 1. Click on Apply and Ok to come out of it. it will become a button '<#>'. . These act as read only for the test. 2. It will show you the value of variable 'Address' in the message box. Make a single click under 'Value' column in the 'Input Parameter's' area. select Action Properties. Type as Number. Go to 'Parameters' Tab. Click on this button. 'Action Call Properties' window opens. qtp. 5.xml extension. In the 'Input Parameters' area click on the '+' sign and enter the Name of the input parameter as 'a'. Open a new Test.com Bottom of Form QTP Random Variables First example of Random Numbers: When you define parameters for an action you can set the parameter's value as Random numbers. 'Action Properties' window opens. Go to 'Parameter Values' Tab. From Variable type dropdown select User-defined. a Test Settingswindow opens. Example 1: 1. Value and Type heading (in our case it will show Address under Name. 25 yellow Road under Value and External under Type). Go to expert view and type: msgbox(environment("Address")) 7. Now run the test. and Default value as 1. ( I saved it in 'tests' folder in the 'QuickTest Professional' folder under C:\Program files.

just click ok. but different values if you run it next time i. then it will show you which step it is currently running by pointing to that particular step with yellow color arrow and then you will be able to understand it in a better way. If we select the second option 'For each test iteration' then a message box will show same values. Again Click ok to come out of 'Action Call Properties' window. click ok to insert a new action. select first option-For each action iteration. it will show you a message that it has made Action1 Reusable. You will see that it shows a different value in each msgbox() because we selected 'For each action iteration' from the 'Generate new random number' area. Now Run the test. 9. Now Go to Insert (Menu)-> Call to New Action. Go to Expert View of Action2 and type: For i=1 to 3 RunAction "Action1". When you copy the above text to Expert View of Action2. 'Insert Call to New Action' window opens. RandomNumber(ParameterNameOrStartNumber [. Second example of Random Numbers: Here is another way of generating random numbers: Open a new test and in the Expert view write these lines and run the test: For i=1 to 5 var1=RandomNumber (0. Click on Name Checkbox and choose arg_a from the dropdown. a different value at each test run. 12. In the 'Generate New Random Number' area. 11. select 'Random Number' from the dropdown.7. 15. RandomNumber("arg_a") Next 14. Click ok.) RandomNumber is an Object.action2.e. oneIteration. In the Numeric Range enter 0 against From and 100 against To. Go to Expert view of action1 and type: msgbox "action1" msgbox(parameter("a")) 13. Click on 'Parameter' radio button. (It would be better if you run it by activating the expert view. 8. 100) msgbox(var1) Next Third example of Random Numbers: (This is more or less same as the first one) .EndNumber]) EndNumber is optional above. 10.

Click Ok. If the number is omitted. 'Action Call Properties' window opens. Click on 'Name' Checkbox and choose arg_a from the dropdown. Click on 'Parameter' radio button. In the keyword View right-click on Action1. 11. it will become a button '<#>'. 'Action Properties' window opens. Open a new test. select 'Random Number' from the dropdown. MsgBox var1 next Let's talk about Randomize and Rnd for some time: Randomize [number] We use a number with Randomize to initialize the Rnd function's random-number generator. It will open 'Value Configuration Options' window. In simple terms Rnd is a function and Randomize is used to initialize this function. 2. 3. select 'Action Call Properties'. And Run the Test. Click ok. 8. the Rnd function (with no arguments) uses the same number as a seed the first time it is called. Fourth example of Random Numbers: Another VBScript method of generating a random number: For i= 1 to 3 var1 = int((101*rnd)+0) ' Generate random value between 0 and 100. the value returned by the system timer is used as the new seed value. Now in the Expert View of action1 type: x=RandomNumber("arg_a") msgbox(x) 12. 5. select first option-For each action iteration. 4. Make a single click under 'Value' column in the 'Input Parameter's' area. Go to 'Parameters' Tab. 7. In the 'Generate New Random Number' area. 1. and Default value as 1. 9. In the Numeric Range enter 0 against From and 100 against To. 6. No matter how many times you Run the below code it generates the same values: For i= 1 to 3 randomize(2) . 10. select 'Action Properties'. Go to 'Parameter Values' Tab. Type as Number. Again Click ok to come out of 'Action Call Properties' window. Click on this button. If Randomize is not used. Again right-click on Action1 in the keyword View .One more way is to define a Random Number parameter in the 'Parameter Options' or 'Value Configuration Options' dialog box. giving it a new seed value. In the 'Input Parameters' area click on the '+' sign and enter the Name of the input parameter as 'a'.

For i= 1 to 3 x=rnd(0) msgbox(x) Next If the number is Not supplied then Rnd generates 'The next random number in the sequence. For i= 1 to 3 x=rnd(1) msgbox(x) Next If the number is Equal to zero (=0)then Rnd generates 'The most recently generated' number.' For i= 1 to 3 x=rnd() msgbox(x) Next . For i= 1 to 3 x=rnd(-1) msgbox(x) Next If the number is Greater than zero(> 0) then Rnd generates 'The next random' number in the sequence. The Rnd function returns a value less than 1 but greater than or equal to 0. MsgBox var1 next Some light on Rnd: The following formula is used to produce a random number in a given range: Int((upperbound . MsgBox var1 next But if you omitt randomize(2) from the above code and instead put only randomize then at each run it generates different values. For i= 1 to 3 randomize var1 = Int((6 * Rnd) + 1) ' Generate random value between 1 and 6.var1 = Int((6 * Rnd) + 1) ' Generate random value between 1 and 6.lowerbound + 1) * Rnd + lowerbound) likewise Int((6 * Rnd) + 1) ' Generate random value between 1 and 6. Rnd(number)If the number is Less than zero (< 0) then Rnd generates 'The same number' every time. using number as the seed.

under 'Value' it will show <vartest>. Click on 'Parameter' radio button and select 'Test/action Parameter' from that dropdown.com Bottom of Form QTP Test parameters 1. Go to 'Parameters' Tab. go to 'Parameters' Tab. Enter the Name of the parameter as 'varaction' and its Type as string and no default value. 9. Above we have created a Test Parameter. 7. Before calling Rnd. Just click on this button to open 'Value Configuration Options' window. Click Ok. Enter the Name of the parameter as 'vartest' and its Default Value as 'hello'. qtp. 'Action Properties' window opens. Go to 'Parameter Values' Tab. Click Ok to come out of that window. 'Test Parameters' radio button will be selected by default and under 'Test Parameters' radio button select 'vartest' from Parameter dropdown. The Type of this parameter is string. 'Action Call Properties' window opens. While running it will show 'hello' in the msgbox. Click on '+' sign which is on the top right. 3. Now run the test. There you will see the 'varaction' action parameter we created earlier. Remember (taken from QTP guide): . 6. use the Randomize statement without an argument to initialize the randomnumber generator with a seed based on the system timer. a 'Test Settings' window will open. 5. Go to File->Settings. Go to Expert View and type: msgbox(parameter("varaction")) 15. in the 'Action Call Properties' window. Open a New Test. 12. When you click on ok to come out of 'Value Configuration Options' window. Make a single click under 'Value' heading. the same number sequence is generated because each successive call to the Rnd function uses the previous number as a seed for the next number in the sequence. Click on '+' sign which is on the top right.Remember: For any given initial seed. 10. 2. 14. Now in the Keyword View right click on Action1 and select 'Action Properties'. Again in the Keyword View right click on Action1 and select 'Action Call Properties'. 4. 8. 11. Click Apply and then Ok. it will show a button like this <#>. This example show how to declare test parameters and how to access those.[ remember this vartest is a test parameter we created at the beginning] 13.blogspot.

you must pass the test parameter to the action containing the step.2 10.blogspot. 4. Click Ok. Just click ok to insert a new action. 2. 2. oneIteration. Open a new Test. In the keyword View right click on action2 and select 'Run from Step'. QTP iterates all rows of any action data sheet. In the Keyword View right click on Action1 and select 'Action Properties'. 5. Make action2 reusable as we did for action1. for each row. 3. 'Action Properties' window opens. To use values supplied for test parameters in steps within an action. 'Insert Call to New Action' window opens. In the same way create another Number parameter 'b'. In the Keyword View right click on Action1 and select 'Action Properties'.com Bottom of Form QTP Action Parameter 1. qtp. in the format: Parameter ("ParameterName"). it will show you the sum 4 in msgbox. . Click on Record. you can enter the parameter name in the Expert View using the Parameter utility object. In the general tab. 1. In the Expert View of action2 type: RunAction "Action1". 2. Click on '+' sign which is on the top right. 9. 'Action Properties' window opens.Go to Start->All Programs->QuickTest Professional->Sample Applications->Flight. Go to 'Parameters' Tab. 3.com Bottom of Form QTP Global & Action Data Sheet Parameters Example 1 How. 8. 6. Alternatively. qtp. Go to Insert (menu)-> Call to New Action. Enter the Name of the parameter as 'a' and its Type as Number. in global data sheet.blogspot. In the Expert View of Action1 type: s1=parameter("a") s2=parameter("b") msgbox(s1+s2) 7. click on 'Reusable Action' checkbox at the bottom to make the action reusable.You can directly access test parameters only when parameterizing the value of a top-level action input parameter or when specifying the storage location for a top-level output parameter.

"C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\". when you click on 'Parameter' radio button and select Data Table from the dropdown. go to File->Exit. I added 'rama'. Go to Insert (menu) -> Call to New Action to insert action2.Exit"     19. It will add a new column in action2 Data Sheet with 'bill ' (because I used bill as an Agent Name ) as its first row. After repeating step 7. Go to Expert View of action one and type : msgbox("acton1"). make a single click on 'mary' (Agent Name)."". Now my action1 looks like this:    SystemUtil. 6.Select "File."open" Dialog("Login"). I added 'amar' and 'Sumit'. as we did for action1. . Right click on action1 and select action call properties.WinEdit("Password:").WinButton("OK"). Go to Global Data Sheet and Add one more row in it below 'mary'. In the Local Data Sheet (action2) add two more rows to make them a total of 3. 8. repeat steps from 2 to 7.WinMenu("Menu").) 5. Click Ok to close that window. 15. In the Keyword View under 'Value' column. Now you have two actions (action1 and action2). 14. click on this button to open 'Value Configuration Options' window.WinEdit("Agent Name:"). Click Stop in order to stop recording the test.WinEdit("Agent Name:"). Click Ok (make sure we click ok with mouse and not hit the return (enter) Key.Click Window("Flight Reservation"). In the Global Data sheet it will add a new columns with 'mary' as its first value. 16. a button like <#> will appear.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a. make sure you select Current action sheet (local) in the Location in Data Table area. For this action2. (This time I have used the Agent Name as 'bill') 12. click ok to come out of that window.exe". 10. Do the same for action2 and type msgbox("acton2") in its Expert view. 9.Set DataTable("p_Text". When the Flight Reservation window is open. Click on Parameter radio button and select Data Table from the dropdown and let rest everything be default.SetSecure "4725bcebeea3b6682d186bf7b15ae92cc4e6c0ba" msgbox("acton1") Dialog("Login"). 7.4. Do the same for action2. go to Run Tab and select "Run on all rows" radio button. dtGlobalSheet) Dialog("Login"). 13. 17. both of them do the same job but their data is in different sheets. 11. Enter the Agent Name as 'mary' and Password as 'mercury'.Type micTab Dialog("Login"). 18.

just to make you familiar with the process so that you can start on your own. For complete understanding of Output values please see QTP User Guide.1) type 'Action1 Data'. 4.blogspot. in cell(A. 2) 'accessing data from action1 data sheet from action1 msgbox rc In expert view of action2 type: msgbox("I am in action 2") rc = DataTable. dtGlobalSheet) 'accessing data from Global data sheet from action1 msgbox rc rc = DataTable. I have added the msgbox step in both the action just to make you understand how the QTP is picking up the rows from Data Sheets.20.Make sure that both (new test and Flight Reservation window) are open and visible. In the Action1 Data table. in cell(A. Example 2 This examples shows that each action can access data not only from Global Data Sheet or its own Local Data Sheet but also from other action's Data Sheet in the same test. Open a new test. Go to Insert (Menu)->Output Value->Standard Output Value.1) type 'Action2 Data'.Value("A". Insert two actions. In Expert View of action1 type: msgbox("I am in action 1") rc = DataTable.com Bottom of Form QTP Output Values This is a very small tutorial on output values.Value("A".Value("A". in cell(A. otherwise it will be fast and some people may not able to understand.Value("A". In the Global Data table. Now Run the test. 1. 2) 'accessing data from action1 data sheet from action2 msgbox rc qtp. In the Action2 Data table. Click on Record in order to record a test.1) type 'Global Data'. Open a new test and also open a sample Flight application (Flight Reservation window) 2. dtGlobalSheet) 'accessing data from Global data sheet from action1 msgbox rc rc = DataTable. 3. .

In the Configure Value area click on Modify button. It will also show that captured value in the Results window. 3. Click Ok. 14. (It creates Insert_Order_enabled_Out column in Global datasheet in Data Table with a Value False in the first row) 11. Make sure that both (new test and Flight Reservation window) are open and visible. QTP will be minimized and mouse pointer will take the shape of a hand. 8. Click on 'Insert Order' button in Flight Reservation window. QTP will show that value in Data Table (under Insert_Order_enabled_Out column) at Run time. Click Stop in order to stop the test. Click on first checkbox (which is Property enabled and Value False). Now it means whatever the value of Insert Order button's Enable Property will be. Open a new test and also open a sample Flight application (Flight Reservation window) 2. Again Click Ok to come out of this "Output Value Properties" window. Below tutorial shows how to use output values with Environment variables. "Output Value Properties" window opens with 'Insert Order' in the Name text field. 8. 6. 'Output Options' window opens. "Object Selection . 5. 7. Click on 'Insert Order' button in 'Flight Reservation window.Output Value Properties" window opens with WinButton : Insert Order highlighted. . Click Ok. Click on Record in order to record a test.Output Value Properties" window opens with WinButton : Insert Order highlighted. 10. 12. These above steps show you how to use output values with Data Table. Go to Insert (Menu)->Output Value->Standard Output Value. Click on first checkbox (which is Property enabled and Value False). In the 'Configure Value' area click on Modify button. "Output Value Properties" window opens with 'Insert Order' in the Name text field. 10. Output Options window opens. 13. 1. 7. 4. 9. Now earlier where under Value it was showing False (see step 8) now it will show Insert_Order_enabled_Out. It will show a true value in there at run time. "Object Selection .5. Just make that Insert Order button enable by putting some values in Flight Reservation window and then see that column (Insert_Order_enabled_Out ) in Data table. It will bring you back to "Output Value Properties" window. QTP will be minimized and mouse pointer will take the shape of a hand. In this window just click Ok.' 6. 9.

It will add a column in the Global Data Sheet with "Sachin" as its first value. ." "Checkpoint Properties" window opens. in order to highlight it and make "Configure Value" area enabled. Right-click anywhere on that row and choose "Insert Standard Checkpoint. select Environment.] In the "Checkpoint Properties" window just click on Ok to come out of it. you can click on it to see the default values QTP has set for us. In this area click on Parameter Radio button. Just add the below line in the Expert View at the end to see the value of the environment variable. Add two more values in the subsequent rows. msgbox(environment("Insert_Order_enabled_out")) 15. Make sure you use Tab key to move from one text box to another and hit Return (Enter) key after entering the Password. Make sure only the Text property is checked which has a value of "Sachin" and rest all of the properties must be unchecked. qtp. Click Ok to come out of this "Output Value Properties" window. In the Keyword view go to the row which has "Sachin" under Value column. 12. I added "aaaa" in the 2nd and "bbbb" in the 3rd. It will also show that captured value in the Results window.11. Just make that Insert Order button enable by putting some values in Flight Reservation window and then see that environment variable value (Insert_Order_enabled_Out ). This is all we need to do. which you checked above. Go to Start-> All Programs->QuickTest Professional->Sample Applications->Flight. Click on Stop in order to stop the recording. It will show a true value in there at run time.blogspot. Now Insert_Order_enabled_out will be User-Defined internal environment variable. Enter the Agent Name as "Sachin" and Password as "mercury". Open a new test.com Bottom of Form Parameterize a Checkpoint You can create a Checkpoint while recording or editing a test. In 'Output Options' window. (You can check that environment variable by going to File->Settings. Environment Tab and choosing UserDefined from variable type) 14. Just make a single click on Text Property. [On the right hand side of Parameter Radio button you will see Parameter Options button (which has paper and pen image on it). Click on Record. and click Ok. When the Flight Reservation window is open Go to File (menu)->Exit. 13. For this tutorial I will take into account Text Checkpoint created through Standard Checkpoint while editing. Now you can Run the test. from 'Output Types' dropdown.

By default.blogspot. Any value entered there first time will be compared by first row of the Global Data Sheet which has "Sachin" and any value entered there Second time will be compared by second row of the Global Data Sheet which has "aaaa" and so on. right click on Action1 and choose Action Properties. Create another input variable in_a1_2. In the Keyword View. Go to Parameters tab and create input variable in_a1_1 with Type as Number. (To create an input variable. no Tab key or Return key). 5) Working with Four Actions qtp. Remember this is a Text Checkpoint on the "Agent Name" Text field. Make sure you enter "Sachin" during first time. that's it. same as above. Rest everything be default. you have to enter Agent Name all of the 3 times (Just enter the Agent Name. "aaaa" during second time and so on.blogspot. Go to Insert (Menu) -> Call to New Action. these act as a foundation for action input and output values (this is ONE of the many ways.com Bottom of Form QTP Action input output parameters Those who are still confused about input parameters to actions and output values from actions.com Bottom of Form QTP Action input output parameters Example 1 Action output value (value returned by a called action) can be stored in a variable Open a new test. qtp. you have to click on ‘+’ sign which is on the right hand side of Input parameters section). 4) Action output value (value returned by a called action) can be stored in Any variable and RunAction Statement is not used. 1) Action output value (value returned by a called action) can be stored in a variable 2) Action output value (value returned by a called action) can be stored in data table column. Just try to enter some other value during second time like "xxxx" it will run the test but show you "Failed" in the Results window in the second iteration.Now when we run the test and it opens the window where we need to enter the Agent Name and Password. to add a new action at the end of the test. We don't need to enter the Password. it will have Action1. of course there can be other ways of doing the things I have done below). . 3) Action output value (value returned by a called action) can be stored in environment variable. just have a look at these examples. Now we have Action1 and Action2 in this test.

just click on Ok) . qtp.blogspot. 2. same as above. var1 msgbox var1 To Run this test make sure Action2 is selected / highlighted if you are in the Keyword View or Action2 is selected from the dropdown above if you are in the Expert View and then choose Automation (Menu) -> Run Current action. Create another input variable in_a1_2. oneIteration. In the Parameters tab. Now we have Action1 and Action2 in this test. you have to click on ‘+’ sign which is on the right hand side of Output parameters section). just click on Ok) RunAction "Action1". In the Expert view of Action1 type: s1=parameter("in_a1_1") s2=parameter("in_a1_2") parameter("out_a1_1")=s1+s2 In the Expert view of Action2 type: (When you copy this below code in Expert view of Action2. also create one output variable out_a1_1 with Type as Number (To create an output variable. you have to click on ‘+’ sign which is on the right hand side of Output parameters section). In the Expert view of Action1 type: s1=parameter("in_a1_1") s2=parameter("in_a1_2") parameter("out_a1_1")=s1+s2 In the Expert view of Action2 type: (When you copy this below code in Expert view of Action2. Go to Parameters tab and create input variable in_a1_1 with Type as Number. it may give you a warning that it will make Action1 reusable.In the Parameters tab. it will have Action1. also create one output variable out_a1_1 with Type as Number (To create an output variable. right click on Action1 and choose Action Properties. Open a new test. By default. it may give you a warning that it will make Action1 reusable. Go to Insert (Menu) -> Call to New Action. (To create an input variable. to add a new action at the end of the test. you have to click on ‘+’ sign which is on the right hand side of Input parameters section). In the Keyword View.2.com Bottom of Form QTP Action input output parameters Example 2 Action output value (value returned by a called action) can be stored in data table column. Rest everything be default.

it may give you a warning that it will make Action1 reusable. In the Expert view of Action1 type: s1=parameter("in_a1_1") s2=parameter("in_a1_2") parameter("out_a1_1")=s1+s2 Go to File-> Settings. 2. qtp. 2. Environment tab. just click on Ok) RunAction "Action1".RunAction"Action1". Enter the parameter name as Action1_out and click Ok. Go to Insert (Menu) -> Call to New Action. DataTable("Action1_out". oneIteration. (To create an input variable. to add a new action at the end of the test. In the Expert view of Action2 type: (When you copy this below code in Expert view of Action2.com Bottom of Form QTP Action input output parameters Example 3 Action output value (value returned by a called action) can be stored in environment variable. in the 'Variable type' dropdown choose User-defined. 2. right click on Action1 and choose Action Properties. it will have Action1. ‘Add New Environment Parameter’ window opens. Go to Parameters tab and create input variable in_a1_1 with Type as Number. Now we have Action1 and Action2 in this test. 2. Rest everything be default. Open a new test. double click on A.blogspot.dtGlobalSheet) In the Global Data Sheet. To Run this test make sure Action2 is selected / highlighted if you are in the Keyword View or Action2 is selected from the dropdown above if you are in the Expert View and then choose Automation(Menu) -> Run Current action. oneIteration. Environment ("env_var") msgbox Environment ("env_var") . In the Parameters tab. In the Keyword View. where you have column names as A. Enter the Name of the parameter as env_var and let the 'Value' field be empty and click on Ok. It will open Change Parameter Name box. you have to click on ‘+’ sign which is on the right hand side of Output parameters section). Create another input variable in_a1_2. Click on the + sign which is on the right side. same as above. also create one output variable out_a1_1 with Type as Number (To create an output variable. you have to click on ‘+’ sign which is on the right hand side of Input parameters section). B and so on. By default.

Go to Parameters tab and in the ‘Store In’ column enter var1.blogspot. In the expert view of Action1 type: Parameter("out_a1_1") = 23 In the expert view of Action2 type: msgbox Parameter(" in_a2_1") qtp. Automation (Menu) ->Run Current Action What these Actions will do: Action4 will call Action1 with two input values 2. In the Keyword View. Go to Parameters tab and create input variable in_a2_1 with Type as Any. In the Keyword View. In the Keyword View.com To Run this test. always go to Action4 and then. Go to Insert-> Call to New Action.com Bottom of Form QTP Action input output parameters Example 4 Action output value (value returned by a called action) can be stored in Any variable and RunAction Statement is not used. By default it will have Action1.To Run this test make sure Action2 is selected / highlighted if you are in the Keyword View or Action2 is selected from the dropdown above if you are in the Expert View and then choose Automation (Menu) -> Run Current action. Go to Parameters tab and in the Value column enter var1. . In the Keyword View.blogspot. Open a new test. Action1 sums those values (2+2=4) and assigns the sum to out_a1_1 (Action1’s output parameter). to add a new action at the end of the test. right click on Action2 and choose Action Properties. qtp.e. right click on Action2 and choose Action Call Properties. Go to Parameters tab and create output variable out_a1_1 with Type as Any. Now we have Action1 and Action2 in this test. right click on Action1 and choose Action Properties. 4) along with another number (3) to Action2 by calling Action2 in its last line. right click on Action1 and choose Action Call Properties. Then Action1 passes the sum (i. 2.

output variable out_a2_1) and Action3 (input variables in_a3_1 & in_a3_2. Go to Insert-> Call to New Action. Similarly add Action3 and Action4. 2. 2. 4. parameter("out_a1_1"). where these passed on values are added and the result is shown in a message box. let all other things be default. parameter("out_a2_1"). In the Parameters tab.2 QTP SystemUtil Vs InvokeApplication SystemUtil is an object which is used to control applications and processes during a run session. Obviously Action1 will be there by default. 3 In the Expert view of Action2 type: parameter("out_a2_1")= parameter("in_a2_1") * parameter("in_a2_2") RunAction "Action3". This adds Action2. Add 1st input variable as in_a1_1 (in means input. output variable out_a3_1). [op].Similarly add 2nd input variable in_a1_2 and one output variable out_a1_1 also a Number Type. file: The name of the file you want to run. 6. 5.[StartIn]) command: The path and command line options of the application to invoke. In the Keyword View right click on Action1 and choose Action properties. . [mode] The InvokeApplication method can open only executable files and is used primarily for backward compatibility InvokeApplication(Command .Run is “one of the methods” of SystemUtil object. oneIteration. when ‘Insert Call to New Action’ window opens. 3) it got from Action1 and passes on the result of multiplication (12) and another number (5) to Action3. oneIteration. Similarly add input and output parameters for Action2 (input variables in_a2_1 & in_a2_2. Although there are other methods like CloseProcessByName etc.Action2 multiplies those two values (4. In the Expert view of Action1 type: s1=parameter("in_a1_1") s2=parameter("in_a1_2") parameter("out_a1_1")=s1+s2 RunAction "Action2". which is on the right hand side of input parameters. object. [params]. a1 is for action1 and 1 is 1st variable) and keep its Type as Number. just click on Ok. oneIteration. Open a new test. [dir].5 In the Expert view of Action3 type: parameter("out_a3_1")= parameter("in_a3_1") + parameter("in_a3_2") msgbox parameter("out_a3_1") In the Expert view of Action4 type: RunAction "Action1". 1. click on the +. 3. Action Properties window opens and go to Parameters tab.Run file.

Example using Command argument The following example uses the InvokeApplication function to open Internet Explorer on my machine. "" wait(3) window("text:=foo .google.Run "iexplore.txt". (Make sure you have a file name foo.exe". "1" wait(3) window("text:=foo . the open operation is performed. Example please see QTP User Guide.EXE". "C:\"." " .Run "foo. InvokeApplication "\Program Files\Internet Explorer\IEXPLORE. You can write the below code in a new test in QTP and run it. False is returned. "c:" Example using params: SystemUtil. mode: Specifies how the application is displayed when it opens. and you selected the Record and run test on any application check box in the Record and Run Settings dialog box.txt". "".EXE" There are 10 modes.Notepad").Close You can run any application from a specified location using a SystemUtil. op:: The action to be performed.txt in C:\ drive) SystemUtil.params: If the specified file argument is an startIn:The working folder to which the executable file.Run statement. for complete list of modes. A SystemUtil.com" This below example opens a text file foo which is saved in C:\ drive and waits for sometime and then closes it.Notepad"). . Return Value Boolean.Close using both the arguments.Run statement is automatically added to your test when you run an application from the Start menu or the Run dialog box while recording a test. "". Default = 1 Activates and displays the window. Other actions can be Edit. Command path refers. This is especially useful if your test includes more than one application.Run "C:\foo. Print etc. InvokeApplication "C:\Program Files\Internet Explorer\IEXPLORE. It should work fine. You can specify one of the modes in the table below. "http://www. "Open". dir The default directory of the application or file. You can type the below line in a new test in QTP and Run it. If the function fails to open the application. If this argument is blank ( ""). use the params argument to specify any parameters to be passed to the application. Example using all arguments except params: SystemUtil.

For example: OptionalStep. In QTP click on Record in order to start recording. Go to Start-> Programs-> QuickTest Professional->Sample Applications-> Flight.com Bottom of Form QTP Optional Step By default. Enter Username. Here remember that the step does not cause the Run to fail. then the Run fails with an error message. a message is displayed for the step that failed to open the dialog box. Make sure that a new blank test and a blank Internet Explorer window is open. However if QTP does not find an Object from the optional step in the Object Repository.qtp. Enter Password. QuickTest Professional deems steps that open the following dialog boxes or message boxes as Optional Steps: Dialog Box / Message Box Title Bar AutoComplete File Download Internet Explorer Netscape Enter Network Password Error Security Alert Security Information Security Warning Username and Password Required 1.Browser("Browser"). 4. . 2. You can also add an optional step in the Expert View by adding OptionalStep to the beginning of the VBScript statement.blogspot.If a Step in an optional dialog box does not open. 2. 3. 5.Dialog("AutoComplete").Click This is an Optional step icon A simple example for Optional Step: 1. To COMPLETE a Run session an optional step is not necessarily required. 3. At the end of the Run session. QTP avoids that step and continues ahead during a Run session.WinButton("Cancel").

In the Action Properties dialog box that opens. 7.. In the Keyword view. right click on Action1 and choose Action Properties. it will not show any error message or fail. The idea is when you run the above test without IE.g. Close the Internet explorer window also from the Cross button which is on the extreme top right. 2. When the Flight application is open go to File->Exit.6. I created another test in QTP with the name "call twra". it will just bypass the ‘browser closing’ step as we have marked it Optional and it will ignore any error for the optional step. It has just one line of code: Msgbox "I am a reusable action" In the Keyword View. At present it also has just one line of code: Msgbox "I am going to call a reusable action in a test . . Now make sure that "call twra" test is open and go to Insert ->Call to Existing Action. 9. follow the below steps: Finally it looks like this Now before you run the test make sure Internet Explorer window is NOT open. But it shows you the warning in the test results.com Bottom of Form QTP Relative Path For this example assume that all of the tests are stored in C:\Program Files\Mercury Interactive\QuickTest Professional\Tests 1. Select Action window opens. I created a test in QTP with the name "twra". 8. Hit the enter key.twra" 3.blogspot. qtp. (E. check the ‘Reusable action’ checkbox in the General tab and click OK. Try to run the same test by just removing the ‘Optional Step’ tag from the above lines and see that it will fail and show you the Run Error. Click Stop to stop the test recording. for better understanding “test with reusable action").

Now go to Tools -> Options and go to Folders tab. In our case we will add C:\Program Files\Mercury Interactive\QuickTest Professional\Tests. 4. . Now without doing anything on Select Action window. The paths that you specify here can be a full path or a relative path. Click on + to add a Path.Here you have to click on “…” button or type the complete path (in ‘From test:’ dropdown) to select the test that contains the reusable action. The relative path is relative to the location of the test currently being edited. just close (Cancel) it. because all the tests are stored in Tests folder.

) as relative path. [If you enter any path (e. QuickTest searches for the file in the folders listed in . Select Action window opens. Now in the “From test:” dropdown just type the name of the test from where you want to call a reusable action (twra in our case) and it will list all of its reusable actions. then during the run session.g. Now again go to Insert ->Call to Existing Action. path for Function Library or path for Object Repository etc.After entering the path click OK. 5.

.the Folders pane of the Options dialog box.\twra in the “From test:” dropdown (No need of step 4 and 5 above) in order to access its reusable actions. This is because both the tests are located in C:\Program Files\Mercury Interactive\QuickTest Professional\Tests and we are currently in C:\Program Files\Mercury Interactive\QuickTest Professional\Tests\call twra. we can simply write . since both “twra” and “Call twra” are stored under Tests. Path of current test (<current test>) is always there in search list (Tools -> Options -> Folders tab). [Just understand the below text very carefully:] We can also do the above steps like this: (Suppose “call twra” test is open) Above in the 3rd step when Select Action window opens. Above you saw just one way of doing things.] Note: Use of relative path is possible anywhere in QuickTest Professional.. in the order in which the folders are listed.

.\twra and it will find it... Additionally you can add the below line in the "call twra" test to know which relative path it picked from the search list (Tools -> Options -> Folders tab). PathFinder is an object which lets you to find file paths.\.Locate You can use a PathFinder.\. since we are in test C:\Program Files\Mercury Interactive\QuickTest Professional\Tests\call twra.\ and type twra. Locate is a method of PathFinder object which returns the full file path that QuickTest uses for the specified relative path based on the folders specified in the Folders tab search list (Tools -> Options -> Folders tab). Script on How to add any path in the Search List '(Tools -> Options -> Folders tab) through a script.Locate ("twra")) See how much you have learned about QTP Relative & Absolute Path by answering these Multiple Choice Questions . So in all we type . so to find twra which is under C:\Program Files\Mercury Interactive\QuickTest Professional\Tests\ we go one step back with .. Msgbox (PathFinder.. One more way to understand: (Still suppose we are in “call twra”) If on your system you go to C:\Program Files\Mercury Interactive\QuickTest Professional\Tests\ and cut the folder twra from here and paste it under C:\Program Files\Mercury Interactive\QuickTest Professional\ then in the above situation you have to go two folders back and type .and our current path is C:\Program Files\Mercury Interactive\QuickTest Professional\Tests\call twra. PathFinder. .\twra) in ‘From test:’ dropdown in Select Action window.Locate statement in your test to retrieve the complete path that QuickTest will use for a specified relative path based on the folders specified in the Folders tab..\ and then type twra (so in all we have to type .

It will open 'Value Configuration Options' window. Again Click ok to come out of 'Action Call Properties' window. 'Action Call Properties' window opens. Type as Number. 8. it will become a button '<#>'. 2. Click Ok. There are many different ways in which you can use Random numbers in QTP.blogspot. Again right-click on Action1 in the keyword View . 'Action Properties' window opens. 'Insert Call to New Action' window opens. In the 'Generate New Random Number' area. In the keyword View right-click on Action1.com Bottom of Form QTP Random Variables First example of Random Numbers: When you define parameters for an action you can set the parameter's value as Random numbers. Click on this button. 5. RandomNumber("arg_a") Next 14. In the 'Input Parameters' area click on the '+' sign and enter the Name of the input parameter as 'a'. Click on 'Parameter' radio button. 4. oneIteration.qtp. Lets jump at the examples straightway. it will show you a message that it has made Action1 Reusable. select first option-For each action iteration. Go to Expert view of action1 and type: msgbox "action1" msgbox(parameter("a")) 13. 10. Make a single click under 'Value' column in the 'Input Parameter's' area. Click ok. Now Go to Insert (Menu)-> Call to New Action. select 'Action Call Properties'. select 'Random Number' from the dropdown. In the Numeric Range enter 0 against From and 100 against To. Now Run the test. Open a new test. 7. Example 1: 1. click ok to insert a new action. 9. 3. 12. Go to Expert View of Action2 and type: For i=1 to 3 RunAction "Action1". Click on Name Checkbox and choose arg_a from the dropdown. select Action Properties. Go to 'Parameters' Tab. 6. 11. and Default value as 1. . Go to 'Parameter Values' Tab. When you copy the above text to Expert View of Action2. 15.action2. just click ok.

5. but different values if you run it next time i. select 'Action Properties'. Click Ok. 10. then it will show you which step it is currently running by pointing to that particular step with yellow color arrow and then you will be able to understand it in a better way.EndNumber]) EndNumber is optional above. Open a new test.(It would be better if you run it by activating the expert view. 8. 11. Click on 'Name' Checkbox and choose arg_a from the dropdown. In the 'Input Parameters' area click on the '+' sign and enter the Name of the input parameter as 'a'. 4. 2. select 'Random Number' from the dropdown. 100) msgbox(var1) Next Third example of Random Numbers: (This is more or less same as the first one) One more way is to define a Random Number parameter in the 'Parameter Options' or 'Value Configuration Options' dialog box. If we select the second option 'For each test iteration' then a message box will show same values. In the 'Generate New Random Number' area.e. 1. 6. Make a single click under 'Value' column in the 'Input Parameter's' area. Again Click ok to come out of 'Action Call Properties' window. it will become a button '<#>'. 'Action Properties' window opens. Click ok. You will see that it shows a different value in each msgbox() because we selected 'For each action iteration' from the 'Generate new random number' area. In the keyword View right-click on Action1. 'Action Call Properties' window opens. It will open 'Value Configuration Options' window. Click on this button. 3. Second example of Random Numbers: Here is another way of generating random numbers: Open a new test and in the Expert view write these lines and run the test: For i=1 to 5 var1=RandomNumber (0. 9. Again right-click on Action1 in the keyword View . select 'Action Call Properties'. Go to 'Parameter Values' Tab.) RandomNumber is an Object. Now in the Expert View of action1 type: x=RandomNumber("arg_a") msgbox(x) . and Default value as 1. In the Numeric Range enter 0 against From and 100 against To. select first option-For each action iteration. RandomNumber(ParameterNameOrStartNumber [. 7. Go to 'Parameters' Tab. Click on 'Parameter' radio button. Type as Number. a different value at each test run.

The Rnd function returns a value less than 1 but greater than or equal to 0. Rnd(number)If the number is Less than zero (< 0) then Rnd generates 'The same number' every time. If Randomize is not used. If the number is omitted. Fourth example of Random Numbers: Another VBScript method of generating a random number: For i= 1 to 3 var1 = int((101*rnd)+0) ' Generate random value between 0 and 100. using number as the seed.lowerbound + 1) * Rnd + lowerbound) likewise Int((6 * Rnd) + 1) ' Generate random value between 1 and 6. For i= 1 to 3 randomize var1 = Int((6 * Rnd) + 1) ' Generate random value between 1 and 6. giving it a new seed value.12. And Run the Test. MsgBox var1 next Some light on Rnd: The following formula is used to produce a random number in a given range: Int((upperbound . In simple terms Rnd is a function and Randomize is used to initialize this function. MsgBox var1 next But if you omitt randomize(2) from the above code and instead put only randomize then at each run it generates different values. the Rnd function (with no arguments) uses the same number as a seed the first time it is called. the value returned by the system timer is used as the new seed value. MsgBox var1 next Let's talk about Randomize and Rnd for some time: Randomize [number] We use a number with Randomize to initialize the Rnd function's random-number generator. No matter how many times you Run the below code it generates the same values: For i= 1 to 3 randomize(2) var1 = Int((6 * Rnd) + 1) ' Generate random value between 1 and 6. For i= 1 to 3 x=rnd(-1) msgbox(x) Next .

pas = "Sachin" MsgBox Crypt_Pass(pas) . pwd = "sachin" e_pwd = Crypt. Before calling Rnd. Example 1 of Crypt Object Type the below text in a new test in QTP and run it. For i= 1 to 3 x=rnd(1) msgbox(x) Next If the number is Equal to zero (=0)then Rnd generates 'The most recently generated' number. QTP Crypt Object Crypt Object is used to encrypt strings.' For i= 1 to 3 x=rnd() msgbox(x) Next Remember: For any given initial seed. You can also write the function (Crypt_Pass) in library and call it from a QTP test. use the Randomize statement without an argument to initialize the randomnumber generator with a seed based on the system timer.Encrypt(pwd) msgbox e_pwd Example 2 of Crypt Object Type the below text in a new test in QTP and run it. the same number sequence is generated because each successive call to the Rnd function uses the previous number as a seed for the next number in the sequence. For i= 1 to 3 x=rnd(0) msgbox(x) Next If the number is Not supplied then Rnd generates 'The next random number in the sequence. Crypt object has an Encrypt method which takes string (string to encrypt) as its parameter.If the number is Greater than zero(> 0) then Rnd generates 'The next random' number in the sequence.

Write the below 3 lines in a notepad and save it with . For example I saved it as "a.Type micTab Dialog("text:=Login").vbs extension and run it from command prompt. pwd = "sachin" e_pwd = Crypt."open" Dialog("text:=Login").Set "mercury" Dialog("text:=Login").Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.SetSecure e_pwd Dialog("text:=Login").encrypt ("Sachin") Set a=Nothing Source Example 4 of Crypt Object There is one trick by which you can know the encrypted password. Entering the encrypted text in a non-secured edit box lets you know the original text.Function Crypt_Pass(epas) Crypt_Pass = Crypt.exe".Encrypt(pwd) SystemUtil. For example type the below lines in a new test in QTP and run them. I am entering the encrypted password (in e_pwd) in "Agent Name" field of the Login dialog box which shows up when you open the Flight Application.vbs" under c:\ and ran it from command prompt by typing just "a" and pressing enter.Encrypt(epas) End Function Example 3 of Crypt Object Use Encrypt outside of QTP in VBScript.Encrypter") Msgbox a.WinEdit("attached text:=Password:").Type micReturn Source .WinEdit("attached text:=Agent Name:").WinEdit("attached text:=Agent Name:")."C:\Program Files\HP\QuickTest Professional\samples\flight\app\".WinEdit("attached text:=Password:")."". Set a=CreateObject("Mercury.

[It is advisable not to give user-defined functions same name as built-in functions (refer to the Built-in functions list in the Step Generator (Insert > Step Generator. User-defined functions can be registered as a method for a QTP test object. it will show all of the Built-in functions in Operation Combo box))] If the function is stored in a function library then we have to associate that function library to a test so that the test can call all the public functions listed in that library. Advantages of Function Library (functions) 1. User-defined functions will make your tests look shorter.blogspot. 2. A user-defined function can then be called from within an action. easier to maintain. in theStep Generator dialog box choose Built-in functions from Library Combo box. read and design.qtp. User-defined functions can be stored in a function library or within an action in the test.com Bottom of Form Function Library Function Libraries in QTP If you have repeatable steps in a test or an action then consider using a user-defined function. Functions in an associated function library are accessible: . 3. Time and resources can be saved by implementing and using user-defined reusable functions.

(Resources->Associated Function Libraries. the changes will take effect only after the test is reopened.Example using private and public functions in function library Example 3 . you must add a Reporter. Functions can be created manually or by using Function Definition Generator. Steps using user-defined functions are not displayed in the test results tree of the Test Results window by default. or c) Can be entered manually in the Expert View. 2. If a function library that is referenced by a test is modified by you or any other user using an external editor. For function to appear in the test results tree. Associate it with a test (File-> Associate Library with Test). A Private function can also be created in a function library and this private function can only be called from within the function library itself in which it is defined. Functions directly stored in an action in a test can be called from within that action only making them private from the outside world.Example of overriding a copy operation of a WinEdit Class objects Some important points regarding Function Libraries. to begin running a test from a point after method registration was performed in a test step (and not in a function library). Open a new function library (File->New->Function library). you must include it in all the function libraries associated with the test otherwise QuickTest ignores all the Option Explicit statements in all function libraries. . If we use options like Run from step or Debug from step. Example 1 . Add content to it (your function).) You can save function library either from File->Save or right click on function library tab on the top of function library and choose save.Simple example of a Function Library and test Example 2 .Example of registering a function to a test object by creating a new operation Example 4 . When we register a function. Many different function libraries can be opened simultaneously as each opens in its own separate window and you can work on them separately. b) From the Operation column in the Keyword View. If you want to use Option Explicit statement in Function Library.ReportEvent statement to the function code.a) From Step Generator (for tests and function libraries). QTP does not recognize the method registration because it occurred earlier to the beginning of the current run session and this all is due to the reason that QTP clears all method registrations at the beginning of each run session. If a test is open you can view all the function libraries associated with it. it applies to an entire test object class and it's not possible to register a method for a specific test object. 3. It is easy to create a function library: 1. You are ready to go.

blogspot. We can re-register the same method with different user-defined functions without first unregistering the method. (Now both new test and function library are open at the same time and we are in function library.) 3. Go to File->New->Test. qtp. "MySet" RegisterUserFunc "WebEdit". and not to the functionality defined in the MySet function. and returns to the original QuickTest Set functionality. In the Arguments area click on ‘+’ and type the name of first argument as ‘var1’ and again click on ‘+’ and type the name of second argument as ‘var2’ and let the Pass Mode be the default which is ‘By Value’. so that tests calling your action will not be affected by the method registration. If there are two associated function libraries that define the same variable in the global scope using a Dim statement or define two constants with the same name. QTP will always call the last function because QuickTest searches the test script for the function prior to searching the function libraries. If you need to use more than one variable with the same name in the global scope.g. Go to Insert->Function Definition Generator. Now we have to write the function body (where it says TODO:) . "Set" After running the UnRegisterUserFunc statement.Example 1 1. Click on Ok to close that Function Definition Generator window. the second definition causes a syntax error. 4. it is strongly recommended to unregister the method at the end of the action (and then re-register it at the beginning of the next action if necessary). "MySet2" UnRegisterUserFunc "WebEdit". enter the Description as ‘addition function’. "Set". In the Function Definition Generator window. 8. the Set method stops using the functionality defined in the MySet2 function. Include a Dim statement only in the last function library (since function libraries are loaded in the reverse order). 5. Open a new test.com Bottom of Form Function Library Example 1 QTP Function Library . Let the ‘Documentation’ be empty. In Additional Information area. Most important of all: If you register a method within a reusable action.Always make sure that each function has a unique name. type the name of the function as my_sum. 7. When it is unregistered it is reset to its original QTP functionality e. Open a new function library. Now it will add the function to your already open Library. Go to File->New->Function library. 2. "Set". if more than one function with the same name exists in the test script or function library. RegisterUserFunc "WebEdit". 6.

txt) 11. One of the functions is private i. (File-> Associate Library with Test) 12. it can be accessed from within the function library itself and cannot be accessed from outside of this function library. 2. Go to File->New->Function library. Associate the function library with the test which is open. Open a new test. Go to File->New->Test. 5.vbs or . Save it. One of the functions is public which we will access from the test. Write the below two functions in the function library. var2) sum=var1+var2 msgbox sum End Function 10.com Bottom of Form Function Library Example 2 QTP Function Library .qfl (by default) or . 3. Finally it will look like: '@Description addition function Public Function my_sum(var1. When you run it. (Save it by giving any name and extension either .blogspot. qtp. Open a new function library. Private Function my_name_tell(name2) msgbox "Hello " & name2 End Function Public Function my_name(name1) msgbox(name1) my_name_tell(name1) End Function 4. In expert view of Associated test type: my_sum 1. it will show two message boxes.com Bottom of Form Function Library Example 3 . one from the public function and second from the private function. 2 qtp.e.blogspot. In the expert view of the test type: my_name("sachin") 7. Save the function library.9.Example 2 Another example which uses both public and private functions in the function library. 1. Associate it.

Example 3 Registering a Function to a test object by creating a new operation Open a new test. Click Ok.WinEdit("Attached text:=Name:". Type the name of the function in the 'Function definition' area (I entered function_1). just type a new value 'New_operation_1' In the ‘Additional information’ area. ‘Function’ and ‘Public’ respectively. Once it is saved. After it is copied to the already open library just complete the function body. After it is associated go the ‘Expert View’ of the test already open and type: Window("title:=Filght Reservation"). the list of operations which WinEdit supports are displayed by default (also called IntelliSense).e. go to File->'Associate Library with Test' to associate this function library with the already open test. Make sure that we are in Function Library. It copies the whole code it generated in the Preview area to the open library. After selecting New_operation_1 just supply one argument to it because while creating the function we provided one argument called var1. So the final line of code in the Expert View now looks like: . type 'my first operation on WinEdit' in Description text box. "New_operation_1".QTP Function Library . (dot). Click on '+' in the ‘Arguments’ area and type 'var1' under Name to create a new variable and let the Pass Mode be default i. Go to Insert-> Function Definition Generator. From Test Object dropdown select 'WinEdit' and in the Operation dropdown instead of selecting one of the values it already shows there. as soon as you press . Let Type and Scope be the default i. Open a Function Library. 'By Value'. Check the 'Register to a test object' checkbox. just select New_operation_1 from there.e. var1) ' TODO: add function body here msgbox var1 End Function RegisterUserFunc "WinEdit". "height:=20"). Finally it looks like this: '@Description my first operation on WinEdit Public Function function_1(test_object."function_1" Save the function library.

But if we do the below steps it surely will show: We will record a simple step in a new action.GetROProperty("text")) Edit.WinEdit("Attached text:=Name:". This New_operation_1 will be there for every object of class WinEdit.New_operation_1"merry" [You can open Flight Reservation window for this test. This is just a simple example to show how it works. Make a single click under Operation column in that row (click where it shows Set) it will show a dropdown and you will be able to see New_operation_1 in that dropdown.SetSelection 0. It just displays a message box with the value which we have supplied to it at the time of writing the code.com Bottom of Form Function Library Example 4 QTP Function Library . Len(Edit. Now insert another new action in this test. In a new library file type: Sub Copy (edit) Edit. "height:=20"). Stop recording. Now go to the ‘Keyword View’. If in this same test you go to ‘Keyword View’. go to the row which has 'Name' under item."Copy" . it will show you New_operation_1 under the Operation column.blogspot. Now QTP will not display New_operation_1unless otherwise you associate the library we created earlier to this new test. It does nothing for the WinEdit object or anything special. in the Name text box enter any name.WinEdit("Attached text:=Name:".Click Edit. In the ‘Flight Reservation’ window. "Copy". Now if you open any new test and again type Window("title:=Filght Reservation"). but it is not necessary] Just Run the test. In this ‘Keyword View’. "height:=20").Example 4 Below is an example that creates a new copy method for winedit object which copies the data from the text field to clipboard and then shows that data (which is copied to the clipboard) in a message box. But here we are not using any Object repository (we are using Descriptive Programming) so we cannot select any object from the Item list as the Object Repository is empty. It is displayed as an operation in the Keyword View Operation list when that test object is selected from the Item list. Click on Record. qtp.Type micCtrlDwn + "c" + micCtrlUp End Sub RegisterUserFunc "WinEdit".Window("title:=Filght Reservation"). (Insert->Call to New Action) Make sure ‘Flight Reservation’ window is open.

blogspot.clipboarddata. Create a new . .Copy Set objhtml=Createobject("htmlfile") a=objhtml.parentwindow. qtp. It will show the value of a as 5 in message box.com Bottom of Form ExecuteFile ExecuteFile There are two ways (usually) to associate the library file to a test. Make sure 'Login' window is open (Start-> All Programs -> QuickTest Professional -> Sample Applications ->Flight). 3. Now open a new test in QTP and write few lines as below and run the test. and you cannot debug a file that is called using an ExecuteFile statement).When you run an ExecuteFile statement within an action. In this login window type "sachin" in the Agent Name text field and run the test.getdata("text") msgbox a unRegisterUserFunc "WinEdit". 2.Open a new test and type: Dialog("text:=Login").winedit("attached text:=Agent Name:"). Resources pane of Test Settings (File->Settings) dialog (has advantages like files are in global scope –all the actions in a test can use those. I saved it under c:\ as add. Another way (obviously it uses the first one in some way).vbs script as shown below. "Copy" Associate the library with the test as we did earlier. can be debugged). ExecuteFile (Local scope . 1. We will start with a very simple example and go on to elaborate more on ExecuteFile.vbs. you can call the functions in the file only from the current action.

In addition to the functions available in the associated function libraries. When you run an ExecuteFile statement within an action. add the file name to the associated function libraries list in the Resources pane of the Test Settings dialog box.vbs file we created earlier. or any of the functions contained in the file.Important points from QTP Guide. you can also call a function contained in any function library (or VBscript file) directly from any action using the ExecuteFile function. .the absolute or relative path of the file to execute. ExecuteFile . You cannot debug a file that is called using an ExecuteFile statement. the execution marker may not be correctly displayed. i. when debugging a test that contains an ExecuteFile statement.vbs and QTP test are like as shown below. When you run your test. the ExecuteFile statement executes all global code in the function library making all definitions in the file available from the global scope of the action's script. you can call the functions in the file only from the current action. one more variable z is added. After including that file we are calling the function from that file and showing its return value in a message box.Try this Now my add. ExecuteFile . The ExecuteFile statement utilizes the VBScript ExecuteGlobal statement. Now what do you think it will show (for z) when the test is run. The syntax of ExecuteFile: ExecuteFile File Where File is a string .e. To make the functions in a VBScript file available to your entire test.Above we are using ExecuteFile function to include the add. You can also insert ExecuteFile statements within an associated function library. In addition.

And guess what will it show now for the msgbox z if the add.vbs and QTP test are as below: qtp.com Bottom of Form .On running this QTP test it will show 7 for msgbox z.blogspot.

Set We did all the above steps just to enable the radio buttons in the Class area. GetTOProperty retrieves the values of only those properties that are included in the test object description in Object Repository by QTP. delete all the lines. GetROProperty.WinButton("OK"). 6. Click Ok 9. GetROProperty.WinObject("Date of Flight:"). GetTOProperties on a radio button object.WinEdit("Name:"). 11. Just record a simple test on Flight Reservation application. I will show very easy to understand example of GetTOProperty.QTP GetTOProperty.WinComboBox("Fly From:").. 3. GetROProperty It will Return the current value (run time value) of the test object property from the object in the application. which sets the Business radio button as shown below. 4. 1. except one.Select "Denver" Window("Flight Reservation"). From the above script which QTP recorded in Expert View.Click Window("Flight Reservation"). 5. The value is taken from the Object Repository.WinButton("FLIGHT").Select "Frankfurt" Window("Flight Reservation").Click Window("Flight Reservation"). 8. button. Click stop in order to stop recording and Save the test. Select value from "Fly To" dropdown. From Class area select Business radio button. Click on Record in QTP to record a new test. Flights Table window opens. Click Flights. GetTOProperties GetTOProperties Returns properties and values which QTP has recorded and will use to identify an object at run time. Go to Start->All Programs->QuickTest Professional->Sample Applications->Flight 2. . Flight Reservation window opens. GetROProperty retrieves the current property value of the object in the application during the test run. Select value from "Fly From" dropdown. 10. 7. Enter Date of Flight..Dialog("Flights Table"). Enter Name. GetTOProperty It will Return the value of a particular property for a test object which QTP recorded to identify an object during Run time.Set "sach" Window("Flight Reservation"). Below is the Expert View script of above steps: Window("Flight Reservation").WinComboBox("Fly To:").WinRadioButton("Business").Type "120908" Window("Flight Reservation").

WinRadioButton("Business"). In the same test delete or comment all of the above code (GetTOProperties) and write the below code for GetROProperty and run the test.GetTOProperties count_of_prop = a.Value MsgBox Prop_Name & " = " & Prop_Value Next This above code which uses GetTOProperties shows all the properties of Business radio button which QTP recorded in order to identify it. Click on Business radio button as shown below It will show all the properties which QTP recorded for Business radio button. For GetROProperty & GetTOProperty you have to specify the property whose value you want to retrieve. Now to view all these properties through a script (and use them later somewhere)use GetTOProperties as below: GetTOProperties Convert the remaining one line in the Expert view like this below and add a For Loop.WinRadioButton("Business").Set Go to Resources (menu)->Object Repository. GetROProperty a=Window("Flight Reservation").Window("Flight Reservation"). . set a=Window("Flight Reservation").GetROProperty("checked") msgbox a Select Economy radio button and then run the above code again to see a different value.1 Prop_Name = a(i).Name Prop_Value = a(i).WinRadioButton("Business").Count For i = 0 To count_of_prop . Object Repository window opens.

WinRadioButton("Business").GetTOProperty("nativeclass") msgbox a a=Window("Flight Reservation"). a=Window("Flight Reservation"). then button (+).Again in the same test delete or comment all of the above code (GetROProperty) and write the below code for GetTOProperty and run the test. Finally I closed the Calculator. Because QuickTest refers to the temporary version of the test object during the run session. and do not affect the values stored in the test object repository. then button (3) and finally button (=). GetTOProperty You can view the value for only those properties which QTP recorded for a particular object. It recorded the first six lines of the script as seen below. I clicked on button (7). Object Repository shows that the text property of button named "7" has a value of 7.blogspot. Value Example 1 of SetTOProperty I opened a new test in QTP and opened Calculator (Start -> All Programs -> Accessories>Calculator). .WinRadioButton("Business"). any changes you make using the SetTOProperty method apply only during the course of the run session.SetTOProperty Property. I added the following lines afterward.GetTOProperty("text") msgbox a qtp.com Bottom of Form QTP SetTOProperty QTP SetTOProperty The SetTOProperty method enables you to modify a property value that QuickTest uses to identify an object. The Object Repository window is read-only during record and run sessions. I started Recording in QTP. Syntax of SetTOProperty method Object(description).

x=Window("Calculator").Close below statement retrieves a value of the text property of a button named "7" using GetTOProperty from memory.WinButton("7"). I saved it as a.Activate Window("Calculator").html .WinButton("3").html file.Click Window("Calculator").WinButton("7").GetTOProperty("text") msgbox x After running the above statements the Object Repository will still be the same as it was before running the above statements.WinButton("="). Window("Calculator").Click Window("Calculator").'QuickTest refers to the temporary version of the test object during the run session. x=Window("Calculator"). (See screenshot above) Example 2 of SetTOProperty Open a new Notepad.SetTOProperty "text".WinButton("7"). Write the below text in the Notepad and save it as .Click Window("Calculator").WinButton("+").Click Window("Calculator").GetTOProperty("text") msgbox x the following statement would set the button's (named "7") text property value to seven (remember temporarily) Window("Calculator").WinButton("7"). "seven" below statement retrieves a value of the text property of a button named "7" using GetTOProperty from memory.

It will record the below line of code: Browser("Browser").When you open the file in IE it will look like as shown below: Make sure that this above file (a. Stop Recording. Object Repository contains information only for Link 1 as can be seen below: .html) is open in IE and QTP is open.Click So for this test. Click on Record. While recording click on Link 1.Link("Link 1").Page("Page").

[Object Repository does not contain information on Link 2] Now if you write the below line in this test. it will click on Link 2 although Link 2 is not in Object Repository. Browser("Browser"). removing the above line (which clicks link 1) and run.Click qtp.Link("Link 1").Click But if you use SetTOProperty as below.Page("Page").Click Browser("Browser").com Bottom of Form Descriptive Programming in QTP . "Link 2" Browser("Browser").Link("Link 1").blogspot. it will show error: Browser("Browser").Link("Link 2").And now if we run this test it will click only Link 1.SetTOProperty "text".Back Browser("Browser").Page("Page").Link("Link 1").Page("Page").Page("Page").

chk_2 and so on. You don't know how many check boxes will be there based on the geographical information you provided. So in this case. efficiency. you can use a Descriptive programming to instruct QTP to perform a Set "ON" method for all objects that fit the description: HTML TAG = input. Only after the object is found in the Object Repository. TYPE = check box. based on the geographical information you provided and then after the email addresses are provided as checkboxes you have to send a rebate letter to them.Click window("Title:=Flight Reservation"). If you are dynamically creating test objects during the run session then also Descriptive Programming goes a long way to help you.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4b. Static is easier but Dynamic provides more power. QTP adds the test object to the Object Repository.close Examle 1b: uses OR . suppose there are 8 check boxes on a web page with names as chk_1.WinEdit("AttachedText:=Agent Name:").winbutton("Text:=OK"). SystemUtil.Whenever you record on any object using QTP. Dynamic: We have to add a collection of properties and values to a description object and then provide the statement with the description object's name.Set "mercury" window("Title:=Login"). who brought iPhone from you. First let’s take a look at Static: This below example uses Descriptive Programming to open Flight Application and does not use object repository at all. This implies that descriptive programming is very helpful if you want to perform an operation on an object that is not stored in Object Repository. QTP finds the object in the Object Repository and uses the stored test object’s description to identify the object in your application/website.g. We can also instruct QTP to perform methods on objects without referring to the Object Repository. directly. Descriptive programming can be done in two ways: Static: We provide the set of properties and values. So it’s not a good idea to put these in an Object Repository. Descriptive Programming is also useful to perform the same operation on several objects with certain matching properties e. For this time just read the script and move on. [ I have given Example 1a's recorded version (which uses Object Repository)in Example 1b just for your comparison of the two so that you can better understand both ] Example 1a: uses DP We can describe the object directly by specifying property: =value pairs. This is possible with the help of Programmatic descriptions or descriptive programming. QTP can perform methods on those objects.WinEdit("AttachedText:=Password:"). Suppose in a web site you have to generate a list of all the customer's email addresses. and flexibility. that describe the object. So one of the other advantages is you can copy this script and Run this from any other machine (other than on which it was created) and it is supposed to work fine. While running a test. We will see examples of both static and dynamic type of descriptive programming in QTP.exe" window("Title:=Login").Set "sachin" window("Title:=Login"). With the help of Descriptive Programming you can Set these check boxes ON or OFF according to your application needs. you will better understand it as you read more.

WebEdit("Author")."".WinMenu("Menu"). Page.close Or We can use 'With & End With' Statement like below: SystemUtil.Select "File.Page("Title:=Mercury Tours"). QTP cannot identify the object. However.Set "Sachin" Above line uses Object Repository for Browser object and Descriptive Programming for Page and WebEdit.exe" With window("Title:=Login") .Set "sachin" Dialog("Login")."open" Dialog("Login"). If the same programmatic description is being used several times then we can assign the object to a variable: E. WebEdit. in the above Example 1a script. you cannot use the following statement.WinEdit("AttachedText:=Agent Name:").SetSecure "476a9c021bc5a7422cf5a84ad08503823abcbaae" Dialog("Login").Page("Title:=Mercury Tours").WebEdit("Name:=Author".WinEdit("AttachedText:=Agent Name:").Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4b.close Now let’s take a look at the dynamic type: . but cannot locate it in the repository because the parent objects were specified using programmatic descriptions.WinEdit("Password:").Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.exe".g. since it uses programmatic descriptions for the Browser and Page objects but then attempts to use an object repository name for the WebEdit test object: Browser("Title:=Mercury Tours").Set "Sachin" Above line uses Descriptive Programming for all objects like Browser.Set "mercury" var.Set "sachin" var.Click window("Title:=Flight Reservation").WinEdit("AttachedText:=Password:").Exit" Note: When using programmatic descriptions from a specific point within a test object hierarchy.Page("Title:=Mercury Tours").winbutton("Text:=OK").WinEdit("Agent Name:").WebEdit("Name:=Author".Set "sachin" .WinEdit("Agent Name:"). For example.WinButton("OK"). If you specify a test object by its object repository name after other objects in the hierarchy have been specified using programmatic descriptions.winbutton("Text:=OK"). since it uses programmatic descriptions from a certain point in the description (starting from the Page object description): Browser("Mercury Tours").Type micTab Dialog("Login"). window("Title:=Login") is being used several times so we do this: Set var = window("Title:=Login") SystemUtil.WinEdit("AttachedText:=Password:").Click Window("Flight Reservation"). you can use the following statement since it uses programmatic descriptions throughout the entire test object hierarchy: Browser("Title:=Mercury Tours").Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4b.Click End with window("Title:=Flight Reservation"). "Index:=3").Set "mercury" . "Index:=3").Set "Sachin" QTP tries to locate the WebEdit object based on its name.SystemUtil.exe" var. you must continue to use programmatic descriptions from that point onwards within the same statement. You can also use the statement below."C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\".

Set mydescription=Description.Create" statement is used. In this Flight reservation window go to File.Create.Flight).value=20 myvar("width"). We use Description object to return a Properties collection object containing a set of Property Objects. Set Myvar = Description. remove and retrieve properties and values to or from properties objects can be entered during the run time.value=119 SystemUtil. For creating Properties collection "Description. returned properties collection.value="WinCheckBox" Set Checkboxes = window("text:=FLight Reservation").WinEdit("AttachedText:=Password:"). Then only in place of an object name.Set "sachin" window("Title:=Login").dialog("text:=Open Order").Understand it like this – A Property Object is a property name and value. In short we first of all need to create a description and then use a particular syntax to retrieve all child objects that match that description and manipulate them according to our own wish.Set "mercury" window("Title:=Login").Programs.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4b.exe" window("Title:=Login")."height:=20".QuickTest ProfessionalSample Applications.WinEdit("AttachedText:=Agent Name:". Lets take a complete example of this: [these extra values (height & width) are not important in our example.value="Agent Name:" myvar("height").winbutton("Text:=OK")."width:=119" ).ChildObjects(mydescription) a=Checkboxes.WinEdit(myvar ).WinEdit("AttachedText:=Password:").Click window("Title:=Flight Reservation"). statements to add. Set myvar= description.In the below script childobjects method is being applied to dialog object and childobjects method uses mydescription property object we created.Create() myvar("AttachedText").Set "mercury" window("Title:=Login").Create() mydescription("Class Name"). in real life you can use this count in some kind of loop.Click window("Title:=Flight Reservation"). I have just added those in order to make you understand this] SystemUtil. can be specified in a statement. This is just an example. Creating checkpoints programmatically: .Create() Once Property Object (Myvar) is created. edit.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4b. We will use this childobjects method to count the checkboxes in this 'Open Order' dialogbox.exe" window("Title:=Login").count msgbox(a) Just try to understand the above code. Our example can run without height and width properties.close Now modifying the above script using Description.Set "sachin" window("Title:=Login").winbutton("Text:=OK"). I will straightway show you an example of how to do this: Make sure that Flight Reservation window is open (Start.Open Order.close Retrieving child objects in Descriptive Programming: There is a ChildObjects method which can be used to get all objects located within a specific parent object or only those that match some criteria for programmatic description.

" button in Flight Reservation window is enable or disable. The value starts with 0.. QTP will search for the third object on the page (it can be any. just open the website (http://newtours.winbutton("Text:=FLIGHT").Run-time value of a specified object property can be compared with expected value of that property by using programmatic description. can assign a value to test object’s index property to uniquely identify it.ReportEvent Statement to send the results to the result window of QTP.com/) and make sure the cursor is in the “User Name” text box and write the following line in the Expert View of new test: browser("title:=Welcome: Mercury Tours").webelement("name:=password".WebEdit("Index:=1"). while learning an object. QTP also. If you use Index:=1 with WebEdit test object.. Definitely there are other ways also to get these]. Index property Index property is useful to identify a test object uniquely. just open the website (http://newtours. QTP will search for the second WebEdit object on a web page.com/) and write the following line in the expert view of new test: browser("title:=Welcome: Mercury Tours"). I have used a message box to show whether it is enable or disable.demoaut.' button to check the 'enable' property of the button. regardless of type) because WebElement object is general object that applies to all objects.page("title:=Welcome: Mercury Tours").Click It will just click the “Password” text box which just highlights that text box and places the mouse cursor in that box. ."index:=2"). DP is also useful in case of programming WebElement objects (A WebElement is a general web object which can represent any web object. For the below script make sure that Flight reservation window is open: a=window("Title:=Flight Reservation"). In the above line if you do Index:=0 then “hello” will be written in the “User Name” text box. Descriptive programming checks are helpful for the object whose properties you want to check but the object is not stored in Object Repository. [you can see an object's properties and methods from QTP help. For all the methods and properties of WebElement object please refer QTP User Guide.) As an example. On the other hand if you use Index:=2 to describe a WebElement object.GetROProperty("enabled") msgbox (a) If a = True Then msgbox ("button is enable") else msgbox ("button is disable") End If In the above script GetROProperty method is being applied to 'Flight.demoaut. As an example. I will show a small example here which checks if the "Flights. you can use the Report.page("title:=Welcome: Mercury Tours").Set "hello" This will write “hello” in the “Password” text box. Index property values are specific to an object and also the value is based on the order in which the object appears in the source code.

com Bottom of Form How we can parameterize Descriptive Programming statements? Open a new blank Notepad and type <title>Hello World1</title> And save it with . (I saved it as First.g. qtp.Notepad").Value = "Hello " & DataTable.html extension.exe") This example uses Run and CloseProcessByName methods to open and close the application (Notepad). .Run "Notepad. Instead of closing the Notepad with CloseProcessByName method.exe" wait(3) SystemUtil.Value("A") Browser(myBrowser). systemutil.html under c:\) 3. Open a new blank test in QTP and type the following code: Set myBrowser = Description.html under c:\) 2.html extension.Last but not the least SystemUtil object SystemUtil object allows you to open and close application by writing its code manually in the Expert view of QTP. Also enter World1 and World2 in Cell A1 and A2 in Global Sheet.exe" This opens an Internet explorer.close 4.Close For opening the application we can use complete paths also e. Below example shows how to open or close a Notepad using code: systemutil. we can use the below line also which is mostly used.Run "C:\Program Files\Internet Explorer\iexplore.CloseProcessByName("Notepad. Open another new blank notepad and type <title>Hello World2</title> And save it with .Create() myBrowser("opentitle"). (I saved it as Second.blogspot. window("title:=Untitled .

So we have used data table in this example to parameterize the values. (Differences between object repository and descriptive programming are not limited to what is shown below. there can be many more) . Double click on First.html in order to open them in Internet Explorer. Highlighting an Object in Your Application etc are couple of features you can’t just resist and of course there are many more). Running the test will close both the browsers. Above is a very small example that shows how we can data-drive a property value since the browsers have opentitle property values as “Hello World1” and “Hello World2” respectively. 6. Below you can find some of the differences between object repository and descriptive programming. Make sure that both First and Second are visible and run the test. qtp.com Bottom of Form QTP Object Repository Vs Descriptive Programming There is no specific answer as to which of the two (object repository or descriptive programming) is better. There are certain situations when using descriptive programming has its own benefits (with descriptive programming along with other features you also get code portability) while in some other typical situations object repository works like a charm (No need to adjust the script when an object properties change.html and Second.5.blogspot.

time and again can be time consuming. although you can use object spy to get help in selecting set of property/value pairs. If the mandatory and assistive properties do not uniquely identify an object. This below example clicks on File ->Open.WinMenu("menuobjtype:= 2"). Object repository is considered relatively faster It is considered relatively slower to create and if you take into account the performance for performance wise also in case of large large applications.<item 2="">") Or .Select ("<item 1="">. QTP uses an ordinal identifier. qtp.[Pp]ad" Window(myobj).. How to use regular expressions with descriptive programming? Regular expressions can be used with descriptive programming. In case of Descriptive Programming we bypass the Object Repository. So I have used regular expression for this where first four dots (.Object Repository With object repository QTP automatically resolves which properties and values are required to uniquely identify an object.blogspot. menu of either a new blank Notepad or WordPad which ever is open. It uses regular expression in the second line where value of regexpwndtitle in case of Notepad is Notepad and in case of WordPad is WordPad. Let us take a small example. Finding a set of automatically (manual creation is also possible) properties to distinctively identify the object as and when you record on the application.. So the Smart Identification mechanism is not used with Descriptive Programming or Programmatic Description. Descriptive programming statements need to be Object repository in QTP is created put into operation manually.com Bottom of Form QTP Descriptive Programming Questions Can Descriptive Programming be used with Smart Identification? Smart Identification works with the help of Object Repository. Descriptive Programming With descriptive programming set of property/value pairs are created by you and all are mandatory.Value = ". Set myobj = Description.) correspond to any four characters and after these four characters there can be capital or lower case p and then ad. You can write the below example in a new test in QTP and make sure either a new Notepad or a WordPad window is open and run the test.. applications. QTP can also use Smart Identification (if enabled).Create() myobj("regexpwndtitle"). QTP starts with predefined mandatory and assistive properties in that order.

..Select "File. Run the test. It will show an error.html under c:\ After it is saved just double click it to open it with Internet Explorer. Now in a new test in QTP type: Browser("text:=Welcome A* .Refresh Make sure that “Welcome A*” Internet Explorer window is open..[Pp]ad" Window(myobj).WinMenu("menuobjtype:=2").Microsoft Internet Explorer").Set myobj = Description..Open.. Ctrl+O" In this above code there can be issues if there is no proper spacing between File.Value = ".Open… and Ctrl+O Is there a way to use special characters in descriptive programming? Let’s understand this with a very simple example: Open a new blank notepad and type <title>Welcome A*</title>And save it with .Create() myobj("regexpwndtitle")..html extension as I saved it as sac.

check checkPoint("text:=sometext") .Now rewrite the above line with a backslash “\” in front of * Browser("text:=Welcome A\* .Refresh It will work fine.Exist Msgbox a Is it possible to use descriptive programming inside a checkpoint? No it is not possible to use descriptive programming with the checkpoint object as in the below line of code: Browser("Browser").Microsoft Internet Explorer").Microsoft Internet Explorer").Page("Page"). You can try another example: a=Browser("text:=Welcome A\* .