How many types of Parameters are available in QTP? and Pls
Explain with example.

Answer Posted / 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.

Is This Answer Correct ?    35 Yes 5 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

Call to copy of an action and call to existing action… i know the diff but in real project how to use..? i want live scenario.pls help me..

1283


Which functionalities of QTP used in banking project? pls any say answer?

1447


How can you identify the browser and its information using the qtp script?

587


I want to test my vb.net solution file using qtp. Does Qtp test only .exe file?

1730


Where to use function or action?

669






How to analyzing the checpoint results?

522


What is accessibility check point?

659


Limitations in QTP?

1746


how to create flat file datasubmission in qtp

1905


What is difference between run time object and test object?

558


Explain how Selenium is different from UFT?

693


What the differences are and best practical application of Object Repository?

592


What is meant by a Check Point in UFT? Also, explain the applicable Check Points.

709


How you know that a test case is a regression test case

3061


What is debugging? How you debug your script?

612