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.

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

. QuickTest connects to your Web site or application and performs each operation in a test or component. 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. A checkpoint is a verification point that compares a recent value for a specified property with the expected value for that property. or tables you specified. Step Over. If we parameterized the test with Data Table parameters. This enables you to identify whether the Web site or application is functioning correctly. 4) Fourth step is Broaden the scope of your test or component by replacing fixed values with parameters. We can subsequently use this output value as input data in 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 run it. We can also set breakpoints to pause the test or component at pre-determined points. And Step Out commands to run a test or component step by step. We can use the Step Into. When you parameterize your test or component. We can also use output values to extract data from our test or component. Run test or component to check the site or application. When we run the test or component. checking any text strings. Run the test or component to debug it. We can then modify your test or component with special testing options and/or with programming statements. QuickTest repeats the test (or specific actions in your test) for each set of data values we defined. objects. 3) Third step is Inserting checkpoints into your test or component. 5) Fifth step is running the test After creating test or component. 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. To check how your application performs the same operations with different data you can parameterize your test or component. 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.

we can view the results. 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. QuickTest uses the stored information about the object during the run session to identify and check the object. or we can report them manually from the Test Results window. We can view a summary of the results as well as a detailed report. ➤ View the results in the Results window. If Quality Center is installed. ➤ Report defects identified during a run session. A run-time object is the real (actual) object in the application or Web site on which methods are performed during the run session. After running the test or component. 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. Properties and methods of objects: The property set for each test object is created and maintained by QuickTest. methods of test objects are methods that QuickTest recognizes and records when they are executed (performed) on an object while we are recording. 6) Sixth step is analyzing the results After we run test or component.We can view the value of variables in the test or component each time it stops at a breakpoint in the Debug Viewer. Netscape for Netscape objects). 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. Methods of Run-time object are the methods of the object in the . 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. Similarly. we can report the defects fond out to a database. we can view the results of the run in the Test Results window.

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.

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

Click anywhere on the white space on the Google. it was already open.in/ is open. Open a blank test. . broken links etc.) 3.(Now only QTP with blank test and www.google. 9. 10. Click on Record.Check CheckPoint("Google") We will explore this line later on.Bottom of Form QTP Tutorials 5 . 5. Go to "Web" tab and choose first option "Record and run test on any open browser.Page("Google"). The mouse pointer will become hand and QTP will be minimized. When you run it. 4. 1.co. Click on 'Page : Google' option which has a page icon on left of it with right corner of the page slightly folded. Go to Insert (menu)->Checkpoint->Standard Checkpoint (or press F12).google.Page Checkpoint Page checkpoint:It is for web applications only. I ran this test by opening www." and click ok.Checkpoint Properties" window.in should be open.in page. 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. Click on Stop in order to stop the Recording. 8.Common things to check with this are load time. on left hand side. 2.google.co. 7.google. In the Expert view it will add just one line: Browser("Google").co.in in offline mode (not on internet). "Record and Run Settings" window opens up. Click ok. A 'Page Checkpoint Properties' window opens up. 6.com it may fail. When we click on Record. Click ok.co. It will Open "Object Selection . Make sure thathttp://www. 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. in the results window. Let all the options be default.

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

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

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

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

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

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

as Standard Windows. Visual Basic. Go to Insert (Menu) ->Checkpoint->Text Checkpoint QTP will be minimized and the mouse pointer will change into pointing hand.00 in the above Flights Table. 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. With the pointing hand click on $110. . Open a New test in QTP and click Record. Text Checkpoint Properties window opens. Click Cancel. and ActiveX. (See Screenshot for Text Checkpoint Properties window below). Go to Insert (Menu) ->Checkpoint->Text Area Checkpoint QTP will be minimized and the mouse pointer will change into crosshairs.recording a test on Windows-based applications. 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. such or Web-based application. Click OK. Java.

if there is more than one line of text selected. You can then click Configure to view and manipulate the actual selected text for the checkpoint. (See Screenshot for Text Area Checkpoint Properties window below).00 in the above Flights Table. Text Area Checkpoint Properties window opens. Click OK. 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. the Checkpoint Summary area displays [complex value] instead of the selected text string. Click Cancel.] Text Area Checkpoint Properties window: .With the crosshairs select $110. Object Selection window opens.

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

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

When the value of an object property for a local object is parameterized. or statement. we can pass an output action parameter value from an action step to a later sibling action at the same hierarchical level. and Action4 are sibling actions at the same hierarchical level. 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. The highest level of the tree is actions. This column shows a hierarchical icon-based tree. all occurrences of the specified object within the action are parameterized. For example. Alternatively. for example.blogspot. Environment variable parameters allow us to use variable values from other sources during the run session. We can then use these parameters in the action step. These may be values that we supply. QuickTest uses a different value from the Data Table. We can parameterize a call to Action4 based on an output value retrieved from Action2 or Action3. function call. then run a test and then analyze the results. suppose that Action2. After recording all the operations. Data Table parameters allow us to create a data-driven test (or action) that runs several times using the data that we supply. Action3. 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. and that these are all nested actions of Action1. Values in steps and checkpoints can be parameterized while recording or editing the test. . or iteration. and generates them in a script (in an Expert View). QuickTest displays them as steps in the Keyword View. but before running the test we can also enhance it with checkpoints and parameters. and all steps are contained within the relevant branch of the tree. Random number parameters Enable us to insert random numbers as values in your test. we are amending the test object description in the local object repository.com Bottom of Form QTP (QuickTest Professional) keyword view In QTP (QuickTest Professional) we first of all record a test. 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. or values that QuickTest generates for us based on conditions and options we choose. The values of object properties can be parameterized for a selected step. In each repetition. utility object.from the external application). Click or Select. Therefore. 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.

For every action called in the test. and all objects in its local object repository.blogspot. An action has its own test script. Documentation It is a Read-only auto-documentation of what the step does in an easy-tounderstand sentence. 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. By breaking up the tests into calls to multiple actions. for example. we can record. we can design more modular and well organized and professional tests. This column is not visible by default. If you create a test in which you log into the system (email). and then log out of the system (email). When we create a new test. modify. and enhance the steps . check inbox. Comment Any textual information you want to add regarding the step. qtp. 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. for example. Assignment The assignment of a value to or from a variable for example. Reusable action Reusable actions are like functions in any programming language. An action is stored with the test in which you created it. the mouse button to use when clicking the image.Value The argument values for the selected operation. This column is also not visible by default. They also make it easier to re-record steps in one action when part of your application changes. 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.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. containing all of the steps recorded in that action. 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. it contains a call to one action. Click the "findFlights" image. If there is a process that needs to be included in several tests.

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

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

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

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

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

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

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

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

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

The Rnd function returns a value less than 1 but greater than or equal to 0.' For i= 1 to 3 x=rnd() msgbox(x) Next . 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 x=rnd(-1) msgbox(x) Next If the number is Greater than zero(> 0) then Rnd generates 'The next random' number in the sequence.var1 = Int((6 * Rnd) + 1) ' Generate random value between 1 and 6. 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. Rnd(number)If the number is Less than zero (< 0) then Rnd generates 'The same number' every time.lowerbound + 1) * Rnd + lowerbound) likewise Int((6 * Rnd) + 1) ' Generate random value between 1 and 6. MsgBox var1 next Some light on Rnd: The following formula is used to produce a random number in a given range: Int((upperbound . using number as the seed. For i= 1 to 3 randomize var1 = Int((6 * Rnd) + 1) ' Generate random value between 1 and 6. 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.

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

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

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

in cell(A. Insert two actions.com Bottom of Form QTP Output Values This is a very small tutorial on output values. In the Action2 Data table. 2) 'accessing data from action1 data sheet from action2 msgbox rc qtp. Go to Insert (Menu)->Output Value->Standard Output Value.Value("A". dtGlobalSheet) 'accessing data from Global data sheet from action1 msgbox rc rc = DataTable.1) type 'Action2 Data'. Open a new test and also open a sample Flight application (Flight Reservation window) 2. otherwise it will be fast and some people may not able to understand.1) type 'Action1 Data'.Value("A". In the Global Data table. 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.blogspot. Now Run the test.Value("A". In Expert View of action1 type: msgbox("I am in action 1") rc = DataTable.20. For complete understanding of Output values please see QTP User Guide. 4. Open a new test. 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. 3. dtGlobalSheet) 'accessing data from Global data sheet from action1 msgbox rc rc = DataTable.1) type 'Global Data'. 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.Make sure that both (new test and Flight Reservation window) are open and visible. Click on Record in order to record a test.Value("A". just to make you familiar with the process so that you can start on your own. 1. . in cell(A.

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

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

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

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.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. also create one output variable out_a1_1 with Type as Number (To create an output variable. it may give you a warning that it will make Action1 reusable. just click on Ok) RunAction "Action1". Go to Parameters tab and create input variable in_a1_1 with Type as Number. Now we have Action1 and Action2 in this test. Rest everything be default. qtp.In the Parameters tab. also create one output variable out_a1_1 with Type as Number (To create an output variable. it will have Action1. 2. same as above. you have to click on ‘+’ sign which is on the right hand side of Input parameters section). Create another input variable in_a1_2. In the Keyword View. right click on Action1 and choose Action Properties. 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. oneIteration. (To create an input variable.2. By default. Open a new test. In the Parameters tab. you have to click on ‘+’ sign which is on the right hand side of Output parameters section). just click on Ok) . you have to click on ‘+’ sign which is on the right hand side of Output parameters section).blogspot. 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. Go to Insert (Menu) -> Call to New Action. it may give you a warning that it will make Action1 reusable. to add a new action at the end of the test.

Go to Insert (Menu) -> Call to New Action. Rest everything be default. it will have Action1. in the 'Variable type' dropdown choose User-defined. oneIteration. In the Expert view of Action2 type: (When you copy this below code in Expert view of Action2. It will open Change Parameter Name box. 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. same as above. double click on A.blogspot. Go to Parameters tab and create input variable in_a1_1 with Type as Number. right click on Action1 and choose Action Properties. Environment tab. In the Parameters tab. Click on the + sign which is on the right side. just click on Ok) RunAction "Action1". 2. oneIteration. Create another input variable in_a1_2. 2. In the Keyword View. DataTable("Action1_out".RunAction"Action1".dtGlobalSheet) In the Global Data Sheet. also create one output variable out_a1_1 with Type as Number (To create an output variable. Environment ("env_var") msgbox Environment ("env_var") . Open a new test. 2.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. 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. qtp. By default. to add a new action at the end of the test. where you have column names as A. you have to click on ‘+’ sign which is on the right hand side of Output parameters section). (To create an input variable. B and so on. Now we have Action1 and Action2 in this test. you have to click on ‘+’ sign which is on the right hand side of Input parameters section). ‘Add New Environment Parameter’ window opens. it may give you a warning that it will make Action1 reusable. Enter the parameter name as Action1_out and click Ok. Enter the Name of the parameter as env_var and let the 'Value' field be empty and click on Ok. 2.

Go to Parameters tab and create output variable out_a1_1 with Type as Any. Go to Parameters tab and create input variable in_a2_1 with Type as Any. Then Action1 passes the sum (i.blogspot. In the Keyword View. right click on Action1 and choose Action Properties. always go to Action4 and then. 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.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 ‘Store In’ column enter var1. Go to Insert-> Call to New Action.com To Run this test. In the Keyword View. . to add a new action at the end of the test. right click on Action2 and choose Action Call Properties.e. 4) along with another number (3) to Action2 by calling Action2 in its last line. Action1 sums those values (2+2=4) and assigns the sum to out_a1_1 (Action1’s output parameter). Go to Parameters tab and in the Value column enter var1. right click on Action1 and choose Action Call Properties. right click on Action2 and choose Action Properties. In the Keyword View. Automation (Menu) ->Run Current Action What these Actions will do: Action4 will call Action1 with two input values 2. qtp. 2. By default it will have Action1. Open a new test.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. In the Keyword View.blogspot. Now we have Action1 and Action2 in this test.

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

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

WinButton("Cancel").com Bottom of Form QTP Optional Step By default. At the end of the Run session. Enter Username. 3. 2. You can also add an optional step in the Expert View by adding OptionalStep to the beginning of the VBScript statement. 5.qtp.If a Step in an optional dialog box does not open. 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.Click This is an Optional step icon A simple example for Optional Step: 1. However if QTP does not find an Object from the optional step in the Object Repository.Browser("Browser"). To COMPLETE a Run session an optional step is not necessarily required. Enter Password. then the Run fails with an error message. QTP avoids that step and continues ahead during a Run session. 2. 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.blogspot. Go to Start-> Programs-> QuickTest Professional->Sample Applications-> Flight.Dialog("AutoComplete"). In QTP click on Record in order to start recording. 3. 4. For example: OptionalStep. Here remember that the step does not cause the Run to fail. .

I created a test in QTP with the name "twra".. I created another test in QTP with the name "call twra". check the ‘Reusable action’ checkbox in the General tab and click OK.blogspot.twra" 3. The idea is when you run the above test without IE. In the Action Properties dialog box that opens. Now make sure that "call twra" test is open and go to Insert ->Call to Existing Action. (E. Hit the enter key.g. But it shows you the warning in the test results. 7. At present it also has just one line of code: Msgbox "I am going to call a reusable action in a test . 8. 2. qtp. right click on Action1 and choose Action Properties. . It has just one line of code: Msgbox "I am a reusable action" In the Keyword View. 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. for better understanding “test with reusable action"). Select Action window opens. follow the below steps: Finally it looks like this Now before you run the test make sure Internet Explorer window is NOT open. 9. In the Keyword view.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. Click Stop to stop the test recording.6. When the Flight application is open go to File->Exit. it will not show any error message or fail. it will just bypass the ‘browser closing’ step as we have marked it Optional and it will ignore any error for the optional step. Close the Internet explorer window also from the Cross button which is on the extreme top right.

Click on + to add a Path. Now without doing anything on Select Action window. The paths that you specify here can be a full path or a relative 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. just close (Cancel) it. 4. The relative path is relative to the location of the test currently being edited. . In our case we will add C:\Program Files\Mercury Interactive\QuickTest Professional\Tests. because all the tests are stored in Tests folder. Now go to Tools -> Options and go to Folders tab.

After entering the path click OK.g.) as relative path. QuickTest searches for the file in the folders listed in . then during the run session. [If you enter any path (e. path for Function Library or path for Object Repository etc. Now again go to Insert ->Call to Existing Action. 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. Select Action window opens. 5.

Above you saw just one way of doing things.] Note: Use of relative path is possible anywhere in QuickTest Professional. we can simply write .the Folders pane of the Options dialog box. . in the order in which the folders are listed. [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. Path of current test (<current test>) is always there in search list (Tools -> Options -> Folders tab).\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. since both “twra” and “Call twra” are stored under Tests.

.\ and type twra.Locate ("twra")) See how much you have learned about QTP Relative & Absolute Path by answering these Multiple Choice Questions .\ and then type twra (so in all we have to type .\.. so to find twra which is under C:\Program Files\Mercury Interactive\QuickTest Professional\Tests\ we go one step back with . 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).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.Locate You can use a PathFinder.. 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).\twra and it will find it. PathFinder is an object which lets you to find file paths.. 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 .\twra) in ‘From test:’ dropdown in Select Action window. since we are in test C:\Program Files\Mercury Interactive\QuickTest Professional\Tests\call twra. So in all we type .and our current path is C:\Program Files\Mercury Interactive\QuickTest Professional\Tests\call twra... Msgbox (PathFinder. . Script on How to add any path in the Search List '(Tools -> Options -> Folders tab) through a script.\.

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

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. a different value at each test run. select 'Action Call Properties'. Type as Number. In the Numeric Range enter 0 against From and 100 against To. Make a single click under 'Value' column in the 'Input Parameter's' area. 2. Click on 'Name' Checkbox and choose arg_a from the dropdown. 7. It will open 'Value Configuration Options' window. 9.EndNumber]) EndNumber is optional above. Again Click ok to come out of 'Action Call Properties' window. 1. 4. select 'Random Number' from the dropdown. 11. Go to 'Parameters' Tab. 3. 10. Go to 'Parameter Values' Tab. 'Action Properties' window opens. 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. 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. but different values if you run it next time i. and Default value as 1. In the 'Input Parameters' area click on the '+' sign and enter the Name of the input parameter as 'a'. 'Action Call Properties' window opens. Now in the Expert View of action1 type: x=RandomNumber("arg_a") msgbox(x) . Again right-click on Action1 in the keyword View . In the 'Generate New Random Number' area. select 'Action Properties'. Click Ok. If we select the second option 'For each test iteration' then a message box will show same values. RandomNumber(ParameterNameOrStartNumber [. 6.(It would be better if you run it by activating the expert view. select first option-For each action iteration. In the keyword View right-click on Action1. Click ok. Click on 'Parameter' radio button. 5.e. Open a new test. 8.) RandomNumber is an Object. Click on this button. it will become a button '<#>'. 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.

And Run the Test. If the number is omitted. 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 randomize var1 = Int((6 * Rnd) + 1) ' Generate random value between 1 and 6. MsgBox var1 next Some light on Rnd: The following formula is used to produce a random number in a given range: Int((upperbound .lowerbound + 1) * Rnd + lowerbound) likewise Int((6 * Rnd) + 1) ' Generate random value between 1 and 6.12. 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. using number as the seed. 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. giving it a new seed value. the Rnd function (with no arguments) uses the same number as a seed the first time it is called. For i= 1 to 3 x=rnd(-1) msgbox(x) Next . 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. In simple terms Rnd is a function and Randomize is used to initialize this function. If Randomize is not used. The Rnd function returns a value less than 1 but greater than or equal to 0. the value returned by the system timer is used as the new seed value. Rnd(number)If the number is Less than zero (< 0) then Rnd generates 'The same number' every time.

pwd = "sachin" e_pwd = Crypt. pas = "Sachin" MsgBox Crypt_Pass(pas) . use the Randomize statement without an argument to initialize the randomnumber generator with a seed based on the system timer. Before calling Rnd. You can also write the function (Crypt_Pass) in library and call it from a QTP test.If the number is Greater than zero(> 0) 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.Encrypt(pwd) msgbox e_pwd Example 2 of Crypt Object Type the below text in a new test in QTP and run it. Example 1 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() msgbox(x) Next Remember: For any given initial seed. 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. QTP Crypt Object Crypt Object is used to encrypt strings.

"open" Dialog("text:=Login").WinEdit("attached text:=Agent Name:"). Set a=CreateObject("Mercury.WinEdit("attached text:=Password:"). For example type the below lines in a new test in QTP and run them. For example I saved it as "a.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."".Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a. pwd = "sachin" e_pwd = Crypt.WinEdit("attached text:=Password:").WinEdit("attached text:=Agent Name:").exe".Encrypt(pwd) SystemUtil."C:\Program Files\HP\QuickTest Professional\samples\flight\app\".Encrypter") Msgbox a.vbs extension and run it from command prompt. 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.Encrypt(epas) End Function Example 3 of Crypt Object Use Encrypt outside of QTP in VBScript. Write the below 3 lines in a notepad and save it with .Function Crypt_Pass(epas) Crypt_Pass = Crypt.Set "mercury" Dialog("text:=Login").vbs" under c:\ and ran it from command prompt by typing just "a" and pressing enter.SetSecure e_pwd Dialog("text:=Login").Type micTab Dialog("text:=Login").Type micReturn Source .

User-defined functions can be stored in a function library or within an action in the test. 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. 2.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. User-defined functions will make your tests look shorter. User-defined functions can be registered as a method for a QTP test object.blogspot. Advantages of Function Library (functions) 1. Functions in an associated function library are accessible: .qtp. [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. A user-defined function can then be called from within an action. read and design. easier to maintain. in theStep Generator dialog box choose Built-in functions from Library Combo box. Time and resources can be saved by implementing and using user-defined reusable functions. 3.

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

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

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

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

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

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

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

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

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

WinRadioButton("Business").WinRadioButton("Business").Name Prop_Value = a(i). 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. Object Repository window opens. For GetROProperty & GetTOProperty you have to specify the property whose value you want to retrieve. Click on Business radio button as shown below It will show all the properties which QTP recorded for Business radio button. set a=Window("Flight Reservation").Set Go to Resources (menu)->Object Repository.1 Prop_Name = a(i).GetROProperty("checked") msgbox a Select Economy radio button and then run the above code again to see a different value.Count For i = 0 To count_of_prop . In the same test delete or comment all of the above code (GetTOProperties) and write the below code for GetROProperty and run the test.WinRadioButton("Business").GetTOProperties count_of_prop = a.Window("Flight Reservation").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. . GetROProperty a=Window("Flight Reservation").

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

WinButton("7"). x=Window("Calculator").html file.Click Window("Calculator").WinButton("="). (See screenshot above) Example 2 of SetTOProperty Open a new Notepad.WinButton("+").WinButton("3").Activate Window("Calculator").Click Window("Calculator").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("7"). Window("Calculator").SetTOProperty "text".Close below statement retrieves a value of the text property of a button named "7" using GetTOProperty from memory.WinButton("7").WinButton("7").Click Window("Calculator"). "seven" below statement retrieves a value of the text property of a button named "7" using GetTOProperty from memory.GetTOProperty("text") msgbox x the following statement would set the button's (named "7") text property value to seven (remember temporarily) Window("Calculator"). x=Window("Calculator"). Write the below text in the Notepad and save it as .'QuickTest refers to the temporary version of the test object during the run session. I saved it as a.html .Click Window("Calculator").

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

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

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. SystemUtil. You don't know how many check boxes will be there based on the geographical information you provided. you will better understand it as you read more.Whenever you record on any object using QTP. directly.close Examle 1b: uses OR .WinEdit("AttachedText:=Password:").winbutton("Text:=OK"). 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. TYPE = check box. 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. 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. For this time just read the script and move on. We will see examples of both static and dynamic type of descriptive programming in QTP. While running a test. This is possible with the help of Programmatic descriptions or descriptive programming. So in this case.exe" window("Title:=Login"). Static is easier but Dynamic provides more power.Click window("Title:=Flight Reservation").WinEdit("AttachedText:=Agent Name:"). [ 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. suppose there are 8 check boxes on a web page with names as chk_1.Set "sachin" window("Title:=Login"). Suppose in a web site you have to generate a list of all the customer's email addresses.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4b. 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. who brought iPhone from you. QTP adds the test object to the Object Repository. efficiency. Only after the object is found in the Object Repository. Descriptive programming can be done in two ways: Static: We provide the set of properties and values. Descriptive Programming is also useful to perform the same operation on several objects with certain matching properties e. If you are dynamically creating test objects during the run session then also Descriptive Programming goes a long way to help you. and flexibility. 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. that describe the object. So it’s not a good idea to put these in an Object Repository. chk_2 and so on. QTP can perform methods on those objects.Set "mercury" window("Title:=Login"). We can also instruct QTP to perform methods on objects without referring to the Object Repository. 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. With the help of Descriptive Programming you can Set these check boxes ON or OFF according to your application needs.

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

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

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

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

Double click on First. Running the test will close both the browsers.html in order to open them in Internet Explorer. Make sure that both First and Second are visible and run the test.5. So we have used data table in this example to parameterize the values.html and Second. Below you can find some of the differences between object repository and descriptive programming. 6. (Differences between object repository and descriptive programming are not limited to what is shown below.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. Highlighting an Object in Your Application etc are couple of features you can’t just resist and of course there are many more). there can be many more) .blogspot. 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. qtp. 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.

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

Run the test.. It will show an error.Microsoft Internet Explorer"). .Select "File.Create() myobj("regexpwndtitle").WinMenu("menuobjtype:=2").Open.html extension as I saved it as sac.Set myobj = Description.Refresh Make sure that “Welcome A*” Internet Explorer window is open....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 .Value = ".[Pp]ad" Window(myobj).html under c:\ After it is saved just double click it to open it with Internet Explorer. Ctrl+O" In this above code there can be issues if there is no proper spacing between File.. Now in a new test in QTP type: Browser("text:=Welcome A* .

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"). You can try another example: a=Browser("text:=Welcome A\* .Now rewrite the above line with a backslash “\” in front of * Browser("text:=Welcome A\* .Microsoft Internet Explorer").Page("Page").Refresh It will work fine.check checkPoint("text:=sometext") .Microsoft Internet Explorer").