Creating A Load Test Script...

[mabe]

So I would have to enter in the same thing 150 times with a different user
name for each? Ok... I assume I would have to do the same with any ther
variables I have such as account numbers etc... if so, that is fine, I
just am trying to get an idea of how time consuming creating a test script
would be...

Thanks for your help.

[serverloading]

Yes, ultimately the variations have to be typed in somewhere.

A good technique is to use a spreadsheet, where you have a column
called $NAME and then one with "=" and then on with $VALUE and you
can then "print to a file" that then shows $NAME=value in the
right spots.

Or, just edit a simple text file -- all eValid files are text files.

Remember, once you have the 100+ wide scenario file created it
is very easy to edit it...any text editor will do...

[mabe]

1. When I set up the parameters, will a user use that parameter for every
iteration that the user does? What I mean is, if user1 uses parameter x,
if that user does 20 iterations, will it use parameter x every time? I
assume it does, but just want clarification on that...

2. This is the important one. If I want to run multiple iterations of a
process, but only want the user to login ONCE, is this possible? Is it
possible to only have the login part of a script executed once and then
have the "meat of the script" executed multiple times? In other words,
can one user, run multiple scripts? Or can I somehow make the user loop
throug only the meat of the script so that it isn't logging off then
logging back in 20 times?

Any information you can provide would be greatly appreciated.

Thanks in advance you have been a great help.

[serverloading]

(1) In a server loading script, a *evl script, a $NAME=value assignment
will apply to each repetition of the script. So if you run that
script 20 times, yes, the $NAME=value applies to each one just as
if you had manually run the script 20 times in a row.

(2) Each eValid launch -- one line in your *evl script -- is ONE
playback, possibly repeated entirely a specified number of times.

But to do what you want, think of your script this way, as having
three parts:

login
body
logout

If you split the script into three files you could just as well
do this by making a NEW script, call it topscript.evs, that contains
three references like this:

CallScript login.evs
CallScript body.evs
CallScript logout.evs

This would be identical to doing the first script, before cutting
up the file.

But if you did this:

CallScript login.evs
CallScript body.evs
CallScript body.evs
...20 times...
CallScript body.evs
CallScript body.evs
CallScript logout.evs

Then you would do the login once, the body 20 times, and the logout once.

[mabe]

The Callscript funtion you refer to, do I put that into the loadtest.evs
or do I create a new script that just has those lines within it? This is
very helpful by the way... One other thing.... if I do the call
script, will each script that is called open a new browser or will the
called scripts run in the same browser?

[serverloading]

Sorry, no, you have to make a new script, call it topscript.evs,
and have IT do the calling.

topscript.evs:

CallScript login.evs
CallScript body.evs
CallScript body.evs
...20 times...
CallScript body.evs
CallScript body.evs
CallScript logout.evs

So your loadtest.evl file will reference topscript.evs, which
in turn will to the multiple replacements.

CallScript simply strings together two pieces. But if you wish
you can apply $NAME=value instances so you could have something
like this:

CallScript login.evs
CallScript body.evs $LOCAL=value1
CallScript body.evs $LOCAL=value2
...20 times...
CallScript body.evs $LOCAL=value3
CallScript body.evs $LOCAL=some-other-value
CallScript logout.evs

Only time you get a new browser instance is when your loadtest.evl
file has an _eValid command in it...