Test Case -> Session ID -> Heartbeat
Hi All,
I am a new user for SOAP UI Pro and trying to evaluate this tool for my current project and today is my last day for trial license.
I am stuck at one place but before that i will explain the scenario which i am trying to do
-> I want to do load testing on my application where user logs into the application and each user keeps on sending heartbeat (xml) to the server and until the heartbeat is sent . So what i want is that if a user login to the application then there is a request which should go on continuously until the user log out.
What i am able to do is
-> Create a test suite with name "Multiple login request" with two test cases "Login" and "Heartbeat"
-> In "Login" i have created the following steps:
1. Create a unique guid by script using Data gen
2. Transfer this property to Suite Level i.e. at "Multiple login request"
3. Send the Login request using webmethod with the session id generated above
4. Call Heartbeat - this function will call the test case "Call Heartbeat"
-> In "Heartbeat" i have create the following steps:
1. Kept a variable "flag" at the test case level which will act as the looping condition for heartbeat
2. Groovy Script - This script calls the test step "GetDataChangedTimestamps - Request 1" which takes the Session ID from the test suite level and sends the request.
Problem - When i run the load test, the load test runs on the test case Login and it calls the heartbeat. The load test creates multiple threads of login but the test case heartbeat has only one thread which is running because the heartbeat can not be stopped. Is it possible to make multiple threads of Heartbeat too with respect to the Login
I am a new user for SOAP UI Pro and trying to evaluate this tool for my current project and today is my last day for trial license.
I am stuck at one place but before that i will explain the scenario which i am trying to do
-> I want to do load testing on my application where user logs into the application and each user keeps on sending heartbeat (xml) to the server and until the heartbeat is sent . So what i want is that if a user login to the application then there is a request which should go on continuously until the user log out.
What i am able to do is
-> Create a test suite with name "Multiple login request" with two test cases "Login" and "Heartbeat"
-> In "Login" i have created the following steps:
1. Create a unique guid by script using Data gen
2. Transfer this property to Suite Level i.e. at "Multiple login request"
3. Send the Login request using webmethod with the session id generated above
4. Call Heartbeat - this function will call the test case "Call Heartbeat"
-> In "Heartbeat" i have create the following steps:
1. Kept a variable "flag" at the test case level which will act as the looping condition for heartbeat
2. Groovy Script - This script calls the test step "GetDataChangedTimestamps - Request 1" which takes the Session ID from the test suite level and sends the request.
Problem - When i run the load test, the load test runs on the test case Login and it calls the heartbeat. The load test creates multiple threads of login but the test case heartbeat has only one thread which is running because the heartbeat can not be stopped. Is it possible to make multiple threads of Heartbeat too with respect to the Login