Answer / saikrishna reddy.k

You can use the parameter feature in QuickTest to enhance
your test or component by parameterizing the values that it
uses. A parameter is a variable that is assigned a value
from an external data source or generator.

You can parameterize values in steps and checkpoints in
your test or component. You can also parameterize the
values of action parameters.

If you wish to parameterize the same value in several steps
in your test or component, you may want to consider using
the Data Driver rather than adding parameters manually.

There are four types of parameters:

Test, action or component parameters enable you to use
values passed from your test or component, or values from
other actions in your test.
In order to use a value within a specific action, you must
pass the value down through the action hierarchy of your
test to the required action. You can then use that
parameter value to parameterize a step in your test or
component.

For example, suppose that you want to parameterize a step
in Action3 using a value that is passed into your test from
the external application that runs (calls) your test. You
can pass the value from the test level to Action1 (a top-
level action) to Action3 (a child action of Action1), and
then parameterize the required step using this Action input
parameter value (that was passed through from the external
application).

Data Table parameters enable you to create a data-driven
test (or action) that runs several times using the data you
supply. In each repetition, or iteration, QuickTest uses a
different value from the Data Table.
For example, suppose your application or Web site includes
a feature that enables users to search for contact
information from a membership database. When the user
enters a member's name, the member's contact information is
displayed, together with a button labelled View <MemName>'s
Picture, where <MemName> is the name of the member. You can
parameterize the name property of the button so that during
each iteration of the run session, QuickTest can identify
the different picture buttons.

Environment variable parameters enable you to use variable
values from other sources during the run session. These may
be values you supply, or values that QuickTest generates
for you based on conditions and options you choose.
For example, you can have QuickTest read all the values for
filling in a Web form from an external file, or you can use
one of QuickTest's built-in environment variables to insert
current information about the machine running the test or
component.

Random number parameters enable you to insert random
numbers as values in your test or component. For example,
to check how your application handles small and large
ticket orders, you can have QuickTest generate a random
number and insert it in a number of tickets edit field.

Answer / shankar

A parameter is avariable that is assigned a value from an
external data source or generator.You can parameterize
values in steps and checkpoints in your test or component.
You can also parameterize the values of action parameters.
There are four types of parameters:

1. Test, action or component parameters
2. Data Table parameters
3. Environment variable parameters
4. Random number parameters

Answer / vikas choubey

Parameterization

A parameter is a variable that is assigned a value from an
external data source or generator.

You can parameterize values in steps and checkpoints in your
test or component. You can also parameterize the values of
action parameters.

You can use the parameter feature in QuickTest to enhance
your test or component by parameterizing the values that it
uses.

If you wish to parameterize the same value in several steps
in your test or component, you may want to consider using
the Data Driver rather than adding parameters manually.

There are four types of parameters:

Test, action or component parameters enable you to
use values passed from your test or component, or values
from other actions in your test.

In order to use a value within a specific action, you
must pass the value down through the action hierarchy of
your test to the required action. You can then use that
parameter value to parameterize a step in your test or
component.

For example, suppose that you want to parameterize a
step in Action3 using a value that is passed into your test
from the external application that runs (calls) your test.
You can pass the value from the test level to Action1 (a
top-level action) to Action3 (a child action of Action1),
and then parameterize the required step using this Action
input parameter value (that was passed through from the
external application).

Data Table parameters enable you to create a
data-driven test (or action) that runs several times using
the data you supply. In each repetition, or iteration,
QuickTest uses a different value from the Data Table.

For example, suppose your application or Web site
includes a feature that enables users to search for contact
information from a membership database. When the user enters
a member’s name, the member’s contact information is
displayed, together with a button labelled View <MemName>’s
Picture, where <MemName> is the name of the member. You can
parameterize the name property of the button so that during
each iteration of the run session, QuickTest can identify
the different picture buttons.

Environment variable parameters enable you to use
variable values from other sources during the run session.
These may be values you supply, or values that QuickTest
generates for you based on conditions and options you choose.

For example, you can have QuickTest read all the values
for filling in a Web form from an external file, or you can
use one of QuickTest’s built-in environment variables to
insert current information about the machine running the
test or component.

Random number parameters enable you to insert random
numbers as values in your test or component. For example, to
check how your application handles small and large ticket
orders, you can have QuickTest generate a random number and
insert it in a number of tickets edit field.

Answer / suhasairody

Thank you Saikrishna Reddy. I know there are 4 types but I
used only variable through Data Table.
I will try other 3 in the script. Thanks a lot once again.

Can anyone please explain me the process of automating an application using QTP as i am new to this?

1 Answers   Fidelity,

---

Did QTP prove efficient for your project? Yes or No, explain?

0 Answers  

---

Give me an example where you have used a COM interface in your QTP project?

1 Answers  

---

How to merge the two object repositories

3 Answers   Wipro,

---

What are the differences between QTP 9.2 and 10? please explain e indetail......

2 Answers   Wipro,

---

Hi, I Install QTP 9.2 in windows Vista. but it is not supporting IE. it is supporting only windows based application. could I change any setting in Vista for supporting IE.. ?? thanks in advance...

2 Answers  

---

How to supress warnings from the "Test results page"?

6 Answers   BirlaSoft,

---

Hello Everyone, Please provide me the practical example of business component concept of QTP.Like how to create business component,how to connect the quality center etc.... Thanks in advance, Gaytri

0 Answers  

---

I have two For loop, first For loop does is creates a customer and input the customer info and then the second for loop within the first for loop does the follows which is capture the customer name and verify the with the data within the datatable. The problem I am coming across is that when it goes through the second time creating another customer and then verify the second customer then it creates the following during runtime. I want is to have the customer2 below Customer1 under the Customer_from_Apps. Any help will be greatly appreciate it. Customer Customer_from_Apps Customer_from_Apps1 Customer1 Customer 1 Customer2 Customer2 Window("Customer Desktop").Window("Customer Tracking (Privacy").WinObject("TreeView20WndClass").Click 92,244 runtimevalue = .VbTreeView("vbname:=AppServerTree").GetROProperty("Selectio n") Customer_Val= Datatable.GlobalSheet.AddParameter ("Customer_from_Apps",runtimevalue) row=datatable.getsheet("Global").GetRowCount For x=1 to row datatable.SetCurrentRow(x) Data_Val=Datatable.Value("Customer",dtGlobalSheet) If (trim(Customer_Val)=trim(Data_Val)) Then Reporter.ReportEvent micPass, "Customer validation successful", "Actual Value: " &Data_Val&vbcrlf& "Customer Value: " &Customer_Val else Reporter.ReportEvent micFail, "Cusotmer validation unsuccessful", "Actual Value: " &Data_Val&vbcrlf& "Customer Value: " &Customer_Val End If Next

0 Answers  

---

who will distribute the project modules for testing in testing team ?

2 Answers  

---

How you r using QTP in u r project

1 Answers   IBM, Lehman Brothers,

---

i have 2 year experience in manual and automation testing, I have less percentages in X, Xii (Second grade), can i elgible to TCS interview (Or MNC's)

3 Answers  

---