38. Explanation for the Keyword scripts:

ð First add the sheets in the Runtime Datatable.

Datatable.addsheet”Module”
Datatable.addsheet”Testcase”
Datatable.addsheet”Teststep”

ð Delete the Global Sheet and Action 1 Sheet.
Datatable.deletesheet(1)

ð Import the data from external excel sheet.
Datatable.importsheet” path of the excel sheet file”

ð Count number of rows in the module sheet.
Mod_rc=datatable.getsheet(1).getrowcount

ð Number of iterations.
For i=1 to mod_rc
Datatable.setcurrentrow(i)

ð To displaying number of rows in the mod_rc.
Msgbox mod_rc

ð Specifying the location of modexe value in 3rd column and first sheet.
Modexe=datatable.value(3,1)

ð If condition is true, module id will be stored in the modid.
If modexe=”Y” then
Modid=datatable(1,1)
(end of first sheet code)

ð Count number of rows in the test case sheet.
Tc_rc=datatable.getsheet(1).getrowcount

ð Number of iterations.
For j=1 to tc_rc
Datatable.setcurrentrow(j)

ð If condition is true, tcid will be stored in the tcid.
Tcmodid=datatable(5,2)
Tcexe=datatable(3,2)
If tcmodid=modid and tcexe=”Y” then
Tcid=datatable(1,2)
Msgbox tcid
(end of second sheet code)

ð Counting number of rows in the test steps sheet and storing number of rows in ts_rc variable.
Ts_rc=datatable.getsheet(3).getrowcount
Msgbox ts_rc
(displaying number of test steps)

ð Number of iterations.
For k=1 to ts_rc
Datatable.setcurrentrow(k)

ð Specifying the location of modexe value in 3rd column and first sheet.
Tstcid=datatable(5,3)

ð If condition is true keyword will be selected.
If tcid=tstcid then
Keyword=datatable(3,3)
(specifying the location of keyword)
Msgbox keyword

ð Selecting the keyword.
Select case keyword

ð Case is openapp it will call launchapp function.
Case “openapp”
Call launchapp(strur 1)

ð Case is adminlogin it will call adminlogin function.
Case”adminlogin”
Call adminlogin(str_uid,str_pwd)
Click to add text

ð Adminlogin function case “adminlogin” call
Admin (str_uid,str_pwd)
Click to add text

ð You add all the cases in the application.
And call respective functions.

37. Keyword Driven Testing:

Step 1: Open the Excel sheet and modify the Sheet 1 as Module, Sheet 2 as Test Case and Sheet 3 as Test Step.
Step 2: In Module sheet enter the Template as Moduleid, Modulename and Moduleexecution and enter all the values in the templates.
Step 3: In the Test Case sheet enter the Template as Testcaseid, Testcasedescription, Testcaseexecution, and Moduleid and enter all the values in the templates.
Step 4: In Test Step sheet enter the Templates as Teststepid, Functionname, Keyword, and Testcaseid and enter value in all the Templates.
Step 5: Save the Excel sheet as .xls.
Step 6: Open the Test in the Qtp.
Step 7: Enter the Script as

E.g:
Nextdatatable.AddSheet"module1"
datatable.AddSheet"testcase1"
datatable.AddSheet"teststep1"
datatable.ImportSheet"C:\Documents and Settings\arcus infotech\Desktop\key.xls","module","module1"
datatable.ImportSheet"C:\Documents and Settings\arcus infotech\Desktop\key.xls","testcase","testcase1"
datatable.ImportSheet"C:\Documents and Settings\arcus infotech\Desktop\key.xls","teststep","teststep1"
mcount=DataTable.GetSheet("module1").getrowcount
For i=1 to mcount
DataTable.SetCurrentRow(i)
mexec=DataTable.Value("moduleexecution","module1")
If mexec="Y" Then
modid=DataTable.Value("moduleid","module1")
MsgBox modid
tccount=DataTable.GetSheet("testcase1").getrowcount
For j=1 to tccount
DataTable.SetCurrentRow(j)
tcexec=DataTable.Value("testcaseexecution","testcase1")
modid1=DataTable.Value("moduleid","testcase1")
If modid1=modid and tcexec="Y" Then
tcid=DataTable.Value("testcaseid","testcas MsgBox tcid
tscount=DataTable.GetSheet("teststep1").getrowcount
For k=1 to tscount
DataTable.SetCurrentRow(k)
tcid1=DataTable.Value("testcaseid","teststep1")
If tcid1=tcid then
keyword=DataTable.Value("keyword","teststep1")
MsgBox keyword
Select Case keyword
Case "la"
Call la
Case "lo"
Call lo
Case "clo"
Call clo
Case "la1"
Call la1
Case "lo1"
Call lo1
Case "fr"
Call fr
Case "capp"
Call capp
End Select
End if
Next
End If
Next
End If
Step 8: Create a New Function Library Page by using File>New>Function Library.
Step 9: Shortkut Key to open Library page is Shift+Alt+N.
Step 10: In the Library page Enter the Function Syntax and its Script like this.

E.g:
Function la
SystemUtil.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.exe"
End Function

Function lo
Dialog("Login").WinEdit("Agent Name:").Set "sdfgsdfg"
Dialog("Login").WinEdit("Password:").SetSecure "4ae135406e68f334ebd94cbccf67f62f249df683"
End Function

Function clo
Dialog("Login").WinButton("Cancel").Click
End Function

Function la1
SystemUtil.Run "C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.exe"
End Function

Function lo1
Dialog("Login").WinEdit("Agent Name:").Set "sdfgsdfg"
Dialog("Login").WinEdit("Password:").SetSecure "4ae135406e68f334ebd94cbccf67f62f249df683"
Dialog("Login").WinButton("OK").Click
End Function

Function fr
Window("Flight Reservation").ActiveX("MaskEdBox").Type "111111"
Window("Flight Reservation").WinComboBox("Fly From:").Select "Frankfurt"
Window("Flight Reservation").WinComboBox("Fly To:").Select "Paris"
Window("Flight Reservation").WinButton("FLIGHT").Click
Window("Flight Reservation").Dialog("Flights Table").WinButton("OK").Click
Window("Flight Reservation").WinEdit("Name:").Set "fsdgsdfgs"
Window("Flight Reservation").WinButton("Insert Order").Click
End Function

Function capp
Window("Flight Reservation").Close
End Function

Step 11: Save the Function Library Page.
Step 12: Now we want to link the Function Library Page with the Test Page in the Qtp by File>Settings>Resources.
Step 13: Test Settings dialog box appears. Click on + symbol to browse the Saved Library file.
Step 14: After the browsing the library file click on Ok.
Step 15: Execute the Script to analyse the Result.

36. Descriptive Programming:

It is nothing but a technique using which operations can be performed on the AUT object. Which are not present in the Object Repository.
There are two Types of Descriptive Programming.
1. Static Descriptive Programming.
2. Dynamic Descriptive Programming.

36.1. Static Descriptive Programming:
We provide the set of properties and values, which describes the object, directly.
Step 1: Open the Test in the Qtp.
Step 2: Open the application that you want to write the Script.
Step 3: Identify the properties for the applications option by using Object Spy.
Step 4: Enter the script as, this below Example uses Descriptive Programming to open Flight Application and does not use object Repository at all. So one of the other advantage is you can copy this script and run this from any other machine (other that on which it was created) and it is supposed to work fine.
E.g: Dialog(“text:=Login”).winedit(“attached text:=Agent Name:”).set “Arcus”
Dialog(“text:=Login”).winedit(“attached text:=Password:”).set ”mercury”
Dialog(“text:=Login”).winbutton(“text:=OK”).click
Step 5: Execute the script to analyse the Result.

36.2. Dynamic Descriptive Programming:
Step 1: Open the test in QTP.
Step 2: open the application that you want to write the Script.
Step 3: Identify the properties for the applications option by using Object Spy.
Step 4: Enter the script as, This below Example uses Descriptive Programming to open Flight Application and does not use object Repository at all. So one of the other advantage is you can copy this script and run this from any other machine (other that on which it was created) and it is supposed to work fine.
Step 5: Enter the Script as
Set dianame=Description. create
Dianame(“text”).value=”Login”
Set agname=Description.create
Agname(“attached text”).value=”Agent Name:”
Set pwd=Description.create
Pwd(“attached text”).value=”Password:”
Set but=Description. create
But(“text”).value=”OK”
Dialog(dianame).winedit(agname).set”Arcus”
Dialog(dianame).winedit(pwd).set”mercury”
Dialog(dianame).winbutton(but).click
Step 6: Execute the Script and analyze the Result.

35. Flat Files:

It is another method to apply the multiple no of inputs to the Script through the Notepad.
Step 1: Open the Notepad, and Enter all the Templates and Inputs for the Templates that you want to apply the input for Script.
Step 2: Save the notepad as .txt.
Step 3: Open the Test in Qtp.
Step 4: Enter the Script as
E.g.: Set fso=createobject ("scripting.filesystemobject")
Set f=fso.opentextfile (" ", 1)
f.skipline
While f.atendofline<>true
s=f.readline
arr=split (s," ")
Dialog ("Login").WinEdit ("Agent Name :") .Set arr (0)
Dialog ("Login").WinEdit ("Password :") .Set arr (1)
Wend
Step 5: Execute the Script to analyze the Result.

34. Database Connections:

We can connect to database & update data & Read data from database using Below Classes.
1. Adobd.Connection: we can use this class to establish the connection to the database.
2. Adodb.Command: we can use this class to execute any SQL statement like Insert, Update and delete Commands.
3. Adobd.Recordset: we can use this class to select the record from database.
By using Database connection we are applying the Multiple no of inputs to the Script.
We can apply the input by 3 ways.
· MS-Access.
· SQL Server.
· Oracle.

34.1. MS-Access:
By using MS-Access we are applying the multiple no of Inputs to check the functionality.
Step 1: Open the MS-Access.
Step 2: Create the Database by clicking on the New Button option in the Menu Bar.
Step 3: Select Blank Database at Right side of the MS-Access.
Step 4: File New Database dialog box opens, in the File Name field just enter the Database Name and click on Create.
Step 5: Database (Access 2000 file format ) dialog box opens.
Step 6: In that dialog box Double click on Create table by Entering Data to create a new data table in the database.
Step 7: Now Data Table opens, In the Field Row just Enter the Template name e.g. AgentName and Password.
Step 8: Then Enter the multiple number of inputs in the Table.
Step 9: Save the Table, and close the Database.
Step 10: Open the Test in the QTP.
Step 11: Enter the script as

E.g.: Set con=createobject ("adodb.connection")
Set rs=createobject ("adodb.recordset")
con.open "provider=microsoft.jet.oledb.4.0; data source=""
rs.open"select * from orders", con
While rs.EOF<>true
Dialog ("Login").WinEdit ("Agent Name :") .Set rs ("agent name")
Dialog ("Login").WinEdit ("Password :") .Set rs ("password")
rs.movenext
Wend

Step 12: Execute the Script to Analyse the Result.

34.2. SQL Server:
Through the SQL Server we are applying the multiple no of inputs for the application.
Step 1: Open the SQL Server.
Step 2: Create the Database and Create the Data table.
Step 3: Enter all the Templates and Inputs in the Data table.
Step 4: Open the Test in QTP.
Step 5: Enter the Script as

E.g.: Set con=createobject ("adodb.connection")
Set rs=createobject ("adodb.recordset")
con.open"provider=sqloledb.1; server= ; uid= ; pwd= ; database= "
rs.open"select * from orders", con
While rs.EOF<>true
Dialog ("Login").WinEdit ("Agent Name :") .Set rs ("agent name")
Dialog ("Login").WinEdit ("Password :") .Set rs ("password")
rs.movenext
Wend

Step 6: Execute the Script to analyse the Result.

34.3. Oracle:
Through the Oracle applying the multiple no of inputs for the application.
Step 1: Open the Oracle
Step 2: Create the Database and Create the Data table.
Step 3: Enter all the Templates and Inputs in the Data table.
Step 4: Open the Test in QTP.
Step 5: Enter the Script as

E.g.: Set con=createobject ("adodb.connection")
Set rs=createobject ("adodb.recordset")
con.open"provider=oraoledb.1; server= ; uid= ; pwd= ; database= "
rs.open"select * from orders", con
While rs.EOF<>true
Dialog ("Login").WinEdit ("Agent Name :") .Set rs ("agent name")
Dialog ("Login").WinEdit ("Password :") .Set rs ("password")
rs.movenext
wend

Step 6: Execute the Script to analyse the Result.

33. Data Driven Testing:

· Data table Method.
· Environment Variable.
· Random Numbers.
33.1. Environmental Variable:
When we want to use the same variable in different actions then we can use envionment variables we can load the set of environment variables from a XML file directly

33.1.1. Types of Environmental Variable:
· User-Defined Internal.
· User-Defined External.
· Built-in.

a. Build-In Variables:
Build-in variables are the name suggests are predefined by QTP. Examples of such variables are OS, OS Version, ActionName which are for Operating System, Operating System Version and Name of the action which is currently running, respectively.
Step 1: Open a new test.
Step 2: Go to the File (Menu)>Settings, a Test settings window opens.
Step 3: Go to the Environment Tab. By default Built-in variable type is selected and you will be able to see Name and Description of the Build-in variables below variable type Dropdown box.
Step 4: You can click on any of those variables to see their current value.
Step 5: Now close the Test Settings window and go to test.
Step 6: In the Expert view type:
a=Environment (“actionname”) & “is running on” & environment (“OS”)
msgbox (a)
Step 7: Run the Test.

b. User Defined Internal:
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.
Step 1: Open a new test.
Step 2: Go to File menu> Settings, a Test Settings window opens.
Step 3: Go the Environment Tab. From Variable Type dropdown select User- Defined.
Step 4: Click on the ‘+’ which is on the right of Variable Type dropdown.
Step 5: Add New Environment Parameter’ window opens up, type the Name and Value of the Variable e.g. in Name type ‘Agentname’ and in Value type ‘arcus’ (without quotes, I have added quotes just for clarity) and click on OK. It will add the variable with its type as ‘internal’.
Step 6: Click Apply and OK to come out of the Test Settings window.
Step 7: Open the Test in QTP, and Enter the script as
E.g.: lv_agentname=Environment.Value ("agentname")
lv_password=Environment.Value ("password")
systemutil.Run"C:\Program Files\Mercury Interactive\QuickTest
Professional\samples\flight\app\flight4a.exe"
Dialog ("Login").WinEdit ("Agent Name :") .Set lv_agentname
Dialog ("Login").WinEdit ("Password :") .Set lv_password
Dialog ("Login").WinButton ("Cancel").Click
Step 8: Execute the Script and analyse the Result.

c. User Defined External:
User Defined External Avriables are the variables which are defined in the file outside of test. These act as read only for the test. You can create as many files for environment variables as you want and choose them for your test.
Step 1: Open a new NotePad .
Step 2: Enter the Value as


Agentname
arcus


And save this notepad as .xml file.
Step 3: Open the New Test in the QTP.
Step 4: Go to File menu> Settings, a Test Settings window opens.
Step 5: Go the Environment Tab. From Variable Type dropdown select User- Defined.
Step 6: Click on “load Variables and values from external file “ check box and import the external xml file that we created above. As soon as it is imported the complete path of that file will be shown in the File text box and the variables in it will show under Name, Value and Type heading (in our case it will show Agentname under Name, arcus under Value, and External under Type).
Step 7: Click on Apply and Ok to come out of it.
Step 8: Open the test in the QTP, and type Script as
Environment.LoadFromFile”Enter the path of the Xml file you saved”
lv_agentname=Environment.Value ("agentname")
lv_password=Environment.Value ("password")
systemutil.Run"C:\Program Files\Mercury Interactive\QuickTest Professional\samples\flight\app\flight4a.exe"
dialog("Login").WinEdit("Agent Name:").Set lv_agentname
dialog("Login").WinEdit("Password:").Set lv_password
dialog("Login").WinButton("Cancel").Click
Step 9: Execute the Script and Analyze the Result.

33.2. Data Table Method:
By using the Data Table method we are Checking the Functionality for the application with Multiple number of inputs.
There are two types of Data Table Testing.
· Internal Data Table Testing.
· External Data Table Testing.

a. Internal Data Table Testing:
It is nothing but just applying the multiple number of inputs through the Defined Time Data Table in the Qtp.
Step 1: Enter all the Scripts for the Application in the Expert View.
Step 2: Go to the Keyword View and Parameterize the Templates and Its Values to the Defined Time Datatable.
Step 3: Through the Defined Time Data Table just apply the Multiple No of Inputs.
Step 4: Execute the Script to analyse the Result.

b. External Data Table Testing:
It is nothing but just applying the multiple number of inputs through the External File i.e. Excel Sheet.
Step 1: Open the Excel sheet, and enter the Templates and its Value that you want to check the functionality of the application.
e.g. agentname and its value, and Password and its value.
Step 2: Save the Excel Sheet as .xls.
Step 3: Open the Test in the QTP.
Step 4: Enter the Script as
E.g.: datatable.AddSheet"Arcus"
datatable.ImportSheet"path","Name of the Sheet in Excel","Arcus"
rc=datatable.GetSheet("Arcus").getrowcount
msgbox rc
For i=1 to rc
datatable.SetCurrentRow (i)
dialog("Login").WinEdit("AgentName:").Setdatatable.Value("agentname","roles")
dialog("Login").WinEdit("Password:").Setdatatable.Value("password","roles")
Dialog (“Login”).WinButton (“Cancel”).click
Next
Step 5: Execute the Script two analyze the Result.

32. Breakpoint:

Breakpoint instruct Quick test to pause a run session at a predetermined place in a test or function library and quick test pauses the run (a breakpoint) before executing the step.
You can
· Examine the effects of the run up to the breakpoint.
· Make any necessary changes.
· Continue running the test or function library from the breakpoint.
· Suspend a run session and inspect the state of your application.
· Make a point which to begin stepping through a test or function library using the step commands.
You can set breakpoints.
You can temporarily enable and disable breakpoints.
After you finish you breakpoints, you can remove breakpoints from your test or library function.
Breakpoints are applicable only to the current Quick test session and are not saved with your test or function library.

32.1. Insert Breakpoint/Remove Breakpoint:
You can easily insert and remove breakpoints in the Keyword View. When you place a breakpoint in a step in the Keyword View, it is also displayed in the Expert View, and vice versa.
You insert a breakpoint in the Keyword View by clicking in the left margin at the point where you want to insert the breakpoint, or by selecting a step and pressing F9, or choosing
Step 1: Generate the Script for the Application.
Step 2: Debug > Insert/Remove Breakpoint.
Step 3: Red breakpoint icon is displayed.
Step 4: You can remove a breakpoint by clicking the breakpoint icon, or by selecting a step and pressing F9 or choosing. Debug > Insert/Remove Breakpoint.
Step 5: Execute the Script to see the Result.

31. Object Identification:

You can view and modify the object class properties in the Object Identification dialog box.
Use the Object Identification dialog box to:
. View the mandatory and assistive properties of an object class.
. Modify the mandatory and assistive properties of an object class.
. .Select the ordinal identifier for an object class.
. Create a user-Defined object class.
. Reset the properties of an object class.
. Quick test has a predefined set of properties that it learns for each test object. You use the object Identification dialog box to view and modify the predefined set of properties of all object classes.

31.1. To open the Object Identification dialog box:
Step 1: From the Quick test professional menu bar, select Tools>Object Identification.
Step 2: Object Identification dialog box appears.
In the Object Identification dialog box, from the Test Object Classes list, select the object class whose properties you want to view.

31.2. Identifying Types of Object Class Properties:
An application uses multiple instances of an object class. For Example, the flight Reservation application uses the Fly From and Fly To Combo box, which are objects of the WinComboBox object class.
Quick test Professional assigns a set of mandatory and assistive properties to the Wincombobox object class to help the class recognize the combo box. These properties help create a unique description of each object in an object class.
Mandatory properties are the properties that Quick Test always recognizes for a test object class. Quick Test recognizes assistice properties if the mandatory properties are not sufficient to create description for an object in an object class.
In the flight Reservation application, the Attached Text property uniquely identifies the object of the Win Combo box object class. Therefore, Quick Test assigns the Attached Text property as a mandatory property to the Win Combo box object class. However, there may be instances of applications where the attached text may be the same for different combo box. In such case, Quick test assigns additional mandatory and assistive properties to create a unique description of an object.
Step 3: In the Object Identification dialog box, below the Mandatory Properties list, click Add/Remove.
Step 4: in the Add/Remove Properties dialog box, clear the properties that you do not require and check the properties that you require.
Step 5: If the available property are not sufficient, click New to create a new property.
Step 6: In the Name Property dialog box, in the New Property Name field, type a name for the property, and click Ok.
Step 7: Click on Ok to close the Add/Remove Properties dialog box and apply the new properties to the object class.

Note: You can modify the assistive properties of an object class in a similar manner.

Step 8: Quick test uses an Ordinal Identifier to identify an object if the mandatory and assistive properties are insufficient to identify the object. You select the Ordinal Identifier as Location Or Index from the Ordinal Identifier list in the Object Identification dialog box.
BY default, the location of an object is used as an ordinal identifier to identify an object.

Note: when you run a test, Quick Test searches for an object based on the description it learned for the object. If Quick test cannot find any object that matches the description, or if it finds multiple objects that match, Quick Test uses the Smart Identification feature to identify the object.

31.3. To modify the Smart Identification Properties:
Step 9: In the Object Identification dialog box, click Configure. The Smart Identification Properties-Browser dialog box appears. The Smart Identification Properties-Browser dialog box displays the Base Filter Properties and Optional Filter Properties lists for an object class.
Step 10: Click Add/Remove to modify a property.
Step 11: Click on Ok in the Object Identification dialog box.
Step 12: After you modify the Smart Identification properties and update a test, you run the test and view the test result.

30. Parameterization:

We can parameterize the value by two methods
1. Parameterize through Data Driver Wizard.
2. Parameterize through the Keyword View.


30.1. Parameterize Through Data Driver Wizard:
The Data Driver enables you to quickly parameterize several (or all) property values for test objects, checkpoints, and/or method arguments containing the same constant value within a given action.
(Or)
Data Driver Wizard is used to convert the Templates and it’s Input from the Script to the Data table (Designed Time Data Table).

To parameterize a value using the Data Driver:
Step 1: Generate the Script by Using the Record Button for Particular application.
Step 2: Choose Tools > Data Driver.
Quick Test scans the test for constants before the Data Driver opens (this may take a few moments).

Note: If the action being scanned contains a large number of lines and constant values, Quick Test warns you that loading the constants may take some time. You can choose whether to wait for the constants to load, or to open the Data Driver wizard quickly without constants.
The Data Driver displays the Constants list for the action. For each constant value, it displays the number of times the constant value appears in the action.

Step 3: If you want to parameterize a value that is not currently displayed in the list (such as an object property value), click Add Value. The Add Value dialog box opens.
Enter a constant value in the dialog box and click Add. The constant is added to the list.

Note: You can add only constant values that currently exist in the test action.

Step 4: Select the value you want to parameterize from the Constants list and click Parameterize. The Data Driver Wizard opens.
Step 5: Select the type of parameterization you want to perform:
Step-by-step parameterization. Enables you to view the current values of each step containing the selected value. For each step, you can choose whether or not to parameterize the value and if so, which parameterization options you want to use.
Parameterize all. Enables you to parameterize all occurrences of the selected value throughout the action. You set your parameterization preferences one time and the same options are applied to all occurrences of the value.
Step 6: If you selected Step-by-step parameterization, click Next. The Parameterize the Selected Step screen opens.
If you selected Parameterize all, the Parameter option is enabled in the Configure value area. Select your parameterization preferences the same way that you would for an individual step.
Step 7: Data Driver Wizard-Parameterize the Selected Step dialog box appears.
Step 8: Select Parameter Radio button and click on browse button (Parameter option).
Step 9: Parameter Option dialog box appears, in the Name field enter the Template Name.
Step 10: In Location in the Data Table select the Global Sheet or Current action sheet (local) to insert the data, and click on Ok.
Step 11: Click Next, and Click on Finish to insert the data.
Step 12: Do the same step to insert the new datas.
Step 13: Through the data table (Designed Time Data table) apply the multiple no of Inputs.
Step 14: Execute the script to check the Result.

30.2. Parameterizing through the Keyword View.
When you test your applications, you may want to check how the application performs the same operations with multiple sets of data. Forexample, suppose you want to check how your Web site responds to ten separate sets of data. You could record ten separate tests, each with its ownset of data. Alternatively, you can create Data Table parameters so that your test runs ten times, each time using a different set of data. this way of setting parameters is called parameterization.
Step 1: Enter the Script for the particular application.
Step 2: open the keyword view, select the Input (that you want to parameterize) in the value field.
Step 3: Now it shows parameter option button, just click on it to open the Value Configuration options.
Step 4: In the Value Configuration Options just select the Parameter Radio Button.
Step 5: In Value Configuration Option dialog box select Name field and modify the name which you want enter as a template in the Data Table.
Step 6: In the Location in Data Table select the Data Table you want to insert (Global Sheet and Current Action Sheet (local)).
Step 7: Click on Ok to insert the selected value in the Selected Data Table.
Step 8: Do the same step to apply for more no of Templates.
Step 9: Enter the Multiple number of inputs through the data table for the Particular Script.

29. Synchronization Point:

Synchronization is used to instruct Quick Test to wait for the application process to complete before proceeding to the next step in the test.
Quick Test Professional has a default global synchronization timeout. This timeout indicates that during text execution, Quicktest waits for an object to achieve a specific status or for the timeout of the object synchronization to occur before moving on to the next step.
If a process takes considerably longer to complete, the global synchronization timeout may not sufficient for the step to complete and the next step might fail. To give these longer steps in a test enough time to complete, add a synchronization point.
Quick test Professional displays an error message if it proceeds to the next step before completing the previous steps.

29.1. Add a Synchronization Point While Recording:
A Synchronization Point must be inserted while recording.
To add a Synchronization Point:
Step 1: Click on Record Button.
Step 2: From the Quick Test Professional menu bar, select Insert>Synchronization Point. The cursor changes to a pointing Hand.
Step 3: Use the pointing hand cursor to select the object in the Flight Reservation window for which you want to add the Synchronization point. The Object Selection-Synchronization Point dialog box appears.
Step 4: Click OK. The Add Synchronization Point dialog box appears.
Step 5: From the Property Name list, select the property name and in the Property Value field, type the property value for which Quick Test should wait before moving to the next step.
Step 6: in the Timeout field, type the synchronization point timeout in milliseconds. This time will be added to the global timeout. Click Ok.

Note: we can insert the Synchronization point manually by wait (time). E.g.: wait (5).

28. Function Definition Generator:

Quick Test provides a Function Definition Generator, which enables you to generate definitions for new user-defined functions and add header information to them. You can then register these functions to a test object, if needed. You fill in the required information and the Function Definition Generator creates the basic function definition for you. After you define the function definition, you can insert the definition in your function library and associate it with your test, or you can insert the definition directly in a test script in the Expert View. Finally, you complete the function by adding its content (code).
To open Function Definition Generator:
Step 1: Make sure that the function library or test in which you want to insert the function definition is the active document. (You can click the document's tab to bring it into focus.) This is because the Function Definition Generator inserts the function in the currently active document after you finish defining it.
Step 2: we need to open new Function Library Page to insert the Function Syntax and to execute the Function.
Step 3: Choose Insert > Function Definition Generator or click the Function Definition Generator button . The Function Definition Generator opens.
Step 4: In the Name box, enter a name for the new function. The name should clearly indicate what the operation does so that it can be easily selected from the Step Generator
Step 5: From the Type list, choose Function or Sub, according to whether you want to define a function or a subroutine.
Step 6: From the Scope list, choose the scope of the function—either Public (to enable the function to be called by any test, or component whose application area is associated with this function library), or Private (to enable the function to be called only from elsewhere in the same function library). By default, the scope is set to Public. (Only public functions can be registered to a test object.)

Note: If you create a user-defined function manually and do not define the scope as Public or Private, it will be treated as a public function, by default.

Step 7: In Preview Screen we can able to see the Functions.
Step 8: Click on OK to insert the Syntax.