Cookie Handling SoapUI Runner
I believe I may have a series of bugs, and or mistakes on my part. We have a soapui 4.5 TestCase that works multithreaded within SoapUI because it appears that SoapUI is not respecting the "Maintain ...
Forum Discussion
Hi,
I am facing an issue that seems relevant to this thread.
My test case is using a data source, using which I am logging in multiple users. After login the user does “some action” and then logs out.
The load test of this test case in SOAPui 4.0.0 was working as expected without any problem.
We recently upgraded to 4.5.0 and since then the test case is failing.
The web application being tested requires http session to be maintained and this option is checked. The web application being tested is https.
Observed :
Say datasource has 10 user credentials.
In load test I am using 10 threads and doing one run per thread.
On execution, the login for all users is successful but the “some action” and logout is done by only one user (the user that logged in last)
Seems like only one session/connection is maintained between SOAPui and my application.
Is this in any way related to the issue discussed in this thread??
If no then sorry for spamming here but I still need help figuring this one out.
I am facing an issue that seems relevant to this thread.
My test case is using a data source, using which I am logging in multiple users. After login the user does “some action” and then logs out.
The load test of this test case in SOAPui 4.0.0 was working as expected without any problem.
We recently upgraded to 4.5.0 and since then the test case is failing.
The web application being tested requires http session to be maintained and this option is checked. The web application being tested is https.
Observed :
Say datasource has 10 user credentials.
In load test I am using 10 threads and doing one run per thread.
On execution, the login for all users is successful but the “some action” and logout is done by only one user (the user that logged in last)
Seems like only one session/connection is maintained between SOAPui and my application.
Is this in any way related to the issue discussed in this thread??
If no then sorry for spamming here but I still need help figuring this one out.