Http load test
Hi all,
I'm having the following problem:
I have a test case with some http requests. The test case logs in an user to a web app, makes a payment and logouts.
The login http request step allways returns a Set-Cookie header with a new session id. I want to use this session id for the rest of the test case. If I run this test case once, the result is the correct. It does everything correctly. The problem starts when I want this test case to be performed by multiple threads simulating concurrent users using the load test functionality from soapui. I want each thread to perform the whole test case and each thread handling it's own session id (obtained in the login step) through out the test case.
I've tried the following idea:
- When a thread gets the session id, it stores the value in a properties step keyed with the thread id and all the following steps where configured with a "Cookie" header that get the correct value from the properties step. But this approach has the problem that the request is being sent with two Cookie headers. One is the session id that I want, the other one is assigned by SoapUI.
How can I prevent Soapui from sending the second session id? Or more suitable: how can I make session ids private to threads?
To clarify:
-----------------------------------------------------------------------------------------------------------------------------
Execution order____+____Thread1 _________________+____Thread2_____________
-----------------------------+ ------------------------------------------------+-------------------------------------------
1________________+____login (get session id X1)____+_________________________
2________________+____________________________+____login (get session id X2)
3________________+____pay_____________________+________________________
SoapUI will make the pay request with session id X2.
I want it to use X1.
Thanks
J.J
I'm having the following problem:
I have a test case with some http requests. The test case logs in an user to a web app, makes a payment and logouts.
The login http request step allways returns a Set-Cookie header with a new session id. I want to use this session id for the rest of the test case. If I run this test case once, the result is the correct. It does everything correctly. The problem starts when I want this test case to be performed by multiple threads simulating concurrent users using the load test functionality from soapui. I want each thread to perform the whole test case and each thread handling it's own session id (obtained in the login step) through out the test case.
I've tried the following idea:
- When a thread gets the session id, it stores the value in a properties step keyed with the thread id and all the following steps where configured with a "Cookie" header that get the correct value from the properties step. But this approach has the problem that the request is being sent with two Cookie headers. One is the session id that I want, the other one is assigned by SoapUI.
How can I prevent Soapui from sending the second session id? Or more suitable: how can I make session ids private to threads?
To clarify:
-----------------------------------------------------------------------------------------------------------------------------
Execution order____+____Thread1 _________________+____Thread2_____________
-----------------------------+ ------------------------------------------------+-------------------------------------------
1________________+____login (get session id X1)____+_________________________
2________________+____________________________+____login (get session id X2)
3________________+____pay_____________________+________________________
SoapUI will make the pay request with session id X2.
I want it to use X1.
Thanks
J.J