Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

Why do you create parameters?

Answer Posted / chethana

1.Right click on a value we want to parameterize (in our
case this is a username - "load1") and select "Replace with
a parameter" menuitem

2.Name the new parameter as "UserName" and click OK btn

3.the value "load1" will be changed with a UserName
parameter

4.Right click on the just added parameter and
select "Parameter properties"
5.By the way, this menu allows others operations with
parameters. You can:

"Restore original value (load1)"
In other words, rollback your changes
"Replace more occurrences" This menuitem will find for the
initial string ("load1") in the script and will propose to
replace it with the new parameter ({UserName}).

Tips: Please, use this feature carefully. For example,
let's there is "http://server/load1.htm" link in the
script. Here, "load1.htm" is a name of page, but
user. "Replace All" will produce incorrect link -
"http://server/{UserName}.

6.Parameter properties" will be shown.This dialog is
a "heart" of any parameter. You can here:

specify the type of the parameter
create the pool of values for any parameter (add new values
for any parameter)
specify, how the parameter will be changed against
interations and users
and other different settings...



7.After that perform the similar procedure for "Password"
parameter

8.Parameterizing allows simplify load/performance testing:

Instead of writing a separate LoadRunner VuGen script for
each virtual user, we added parameters for specific
information (username & password) and used the one script
for all users.
Parameterizing allows decrease maintenance cost. If
application under test is changed, one test should be
updated for 100 (e.g.) users, but 100 tests for each user
Supporting of tests is a real pleasure :) To add new user,
a test has to update dat-files only.

Is This Answer Correct ?    1 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

What are the element in the loadrunner controller?

1149


Which protocols are supported by loadrunner?

959


What is difference between manual scenario and goal oriented scenario?

1126


When a scenario run exactly what happened?

1087


What are the types of checkpoints is available in loadrunner?

1197


How many types of vuser are available?

1100


What is ramp up and ramp down?

1163


What is the difference between load, performance testing?

1113


How to schedule a scenario?

1171


Which web protocol recording level generates the web_submit_form function?

1544


What type of function generate and insert by the vugen to the script when you record a script?

1226


What is performance testing in loadrunner?

1016


Which loadrunner component does the recording of performance test scenario?

1108


What are the different sections of the script? In what sequence do these sections run?

1488


How load runner interacts with the application?

1408