sheela

• Mar 29th, 2006

 

1.Use For loop for executing same script for 100 times.2.It is not valid case.3. Not necessary.

vinsingh_2002

 Profile Answers by vinsingh_2002 

• May 8th, 2006

 

Hi Vivek,

1.)Is the same script runs 100 times for same UID/PWD what i have entered during Recording

Ans - Yes the same script is running.

2.)If my data base contains only 50 users.Selecting 100 Vusers is a valid case?.

Ans - Yes it is a valid case because it id not going to your DB to fetch records as it is only generating the load.

If you want to login as 100 different users then you have to paramterize the script and then pass 100 users in an excel.

3.)If i have selected 100 Vusers,is it necessary to enter 100 UID/PWD.
Ans - No it is not necessary.

Vivek it is a better practice that for any specific role(User Type) you may put the data in an XLS and then call that XLS in the program. This will imitate a real life condition.

Vimalkanth

• Jun 20th, 2006

 

1) it depends on your script settings. As best practice, you may want to have unique type selected for your parameterization.

2) Again, this depends on your requirement. If you have 50 users in DB, you can use the script in cyclic manner.

3) This is related to 1. if you have selected unique, yes.

Shaik

• May 8th, 2007

 

Question is :
1) Is the same script runs 100 times for same UID/PWD What I have entered during Recording.
Script doesn't run 100 times, 100 Vusers run the same script Concurrently .

2) If my data base contains only 50 users. Selecting 100 Vusers is a valid case?
If your controller supports 100 vusers
you can run with 100 vusers.
Database doesn't play any role here.

3) If i have selected 100 Vusers, is it necessary to enter 100 UID/PWD.
Not required, that the work of the load runner to look after

Regards,
Shaik

b.sainarayanarao

 Profile Answers by b.sainarayanarao Questions by b.sainarayanarao

• Oct 20th, 2007

 

To my knowledge, no. of vusers did not mean no. of times and it implies that the selected no. of vusers access the application at a time i.e. is called as Load. During the recording time what ever the inputs you used, the load runner also uses same set of inputs for all the vusers.

kranthikiran

• Oct 25th, 2007

 

1) Is the same script runs 100 times for same UID/PWD What I have entered during Recording.
Script doesn't run 100 times, 100 Vusers run the same script Concurrently

Anshoo_Arora

 Profile Answers by Anshoo_Arora 

• Oct 30th, 2007

 

There are different ways to look at this, but I will try my best to narrow it down.

Answer 1. If your script is running for 100 iterations with the same Username and Password, that means there is either no Parameterization or you have parameterized the script with the same Username/Password 100 times (but here, I will ask Why??) and set the script to run 100 times (100 iterations). I cannot go into depth as your question isn't particularly clear.

Answer 2. Yes, but again, it depends on what you are trying to achieve. You can use those 50 users can have the script run sequentially for 2 iterations. You can also create 50 different Vusers which will be production-like.

Answer 3. No, it is not necessary. Set your script to run 100 iterations.

Joe

• Nov 5th, 2007

 

You are just practising LR as I see here.
To test the load on the system you must have a requirement first.
You have selected 100 VUsers.  But you haven't mentioned how long you want to run and record the system performance.  Basically if you just want to stress the system, you don't need any parametrization, just run the script and increase the VUsers as you like.
However, if you are testing specific business scenarios and wants to get the performance readings, you need to use values from a parameter file.  If you give 100 user IDs and start LR with 100 VUsers, LR will divide 100 values for 100 users and each user will get only 1 value.  If your run setting says "Stop Vuser after the available values are finished", then your scenario will just run for a split of a second only.
So, please read the parametrization and related topics, before venturing anything further.
Joe