It shouldn't matter in respect to jmeter functionality, but server-side business logic could be an issue such as:
- caching of login credentials - only allowing x number of active session at a time. - logout logs the user out completely(close all sessions) I personally would question the usefulness of replicating a single login doing 30 different tasks at the same time. It is not the real way in which the server will be tested as it scales. A CSV file with credentials could give each thread its own credentials or simply use a once only controller in each thread to create a new user for the specific thread. Just my thoughts. Good luck Anthony From: Divya Singh Sent: 9/6/2012 6:49 AM To: [email protected] Subject: Simulating multiple threads using same login Hi All, I am executing a Jmeter test plan with 30 virtual users and using a single login ID for all threads. I also have added a CookieManger to my test plan. The e2e transaction I am executing is 1) Login to application 2) Conduct a Search for a Ticket number 3) view the ticket detail 4) update the Ticket and save 5) Run a report 6) Logout This is a basic test however I have a doubt if it is advisable to use the same login credentials for all the simulated threads? Are there any implications of using this approach? Per my understanding, Jmeter simply sends http requests to the server and for the server each incoming request is unique. So it should not matter if the threads are using the same login. Please correct me if I am wrong. Thanks, D --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
