Distributed Table Logs and SoapUI session Persistance
Hi I have just upgraded to LoadUI 2.0 beta 1 to get the new features, mainly the better SoapUI runner, and I have a couple of issues:
Firstly, I have a distributed test in which I use two SoapUI runners, one to do a log on, and one which is in a loop doing a more complex test of various actions (HTTP requests).
I have placed several Table Logs and connected them up to output both results and errors from the tests.
I have a similar local project, when I run that I get data in the Tables and the logging feature seemed to work.
Now I run the distributed project there is no data displayed and nothing gets saved to the specified logs on the agents.
Documentation seems to be for a much older version of LoadUI Table Log, the new component has an 'Enable in distributed mode' checkbox as well as a save button.
I have played with the checkbox and other settings and still get no saved file or display. When I add some folders to the path for the file it creates them but still no file. Is this a bug or am I missing something important, I believe I have run out of settings combinations to try.
At this stage I have no meaningful output for my test, saved or otherwise.
Secondly, I am having issues with the http sessions.
I love being able to pass the session from one SoapUI runner to the next, but it seems that each time a new trigger hits my first 'logon' runner it still has the session and so my logon fails (as it should) because it already has a session and thinks its logged on. If the same test is run just in SoapUI it always gets a new session. Is there anything we can do to fix this? I would desire to have a session per 'user' triggered.
Also, on the issue of generators, I would like to do a ramp up of 'fixed load' which is appropriate for this kind of test. At the moment I use the fixed load generator and ramp it manually. None of the other generators had the second input for the feedback on running requests, is there anything coming to help with this?
Thanks.
Firstly, I have a distributed test in which I use two SoapUI runners, one to do a log on, and one which is in a loop doing a more complex test of various actions (HTTP requests).
I have placed several Table Logs and connected them up to output both results and errors from the tests.
I have a similar local project, when I run that I get data in the Tables and the logging feature seemed to work.
Now I run the distributed project there is no data displayed and nothing gets saved to the specified logs on the agents.
Documentation seems to be for a much older version of LoadUI Table Log, the new component has an 'Enable in distributed mode' checkbox as well as a save button.
I have played with the checkbox and other settings and still get no saved file or display. When I add some folders to the path for the file it creates them but still no file. Is this a bug or am I missing something important, I believe I have run out of settings combinations to try.
At this stage I have no meaningful output for my test, saved or otherwise.
Secondly, I am having issues with the http sessions.
I love being able to pass the session from one SoapUI runner to the next, but it seems that each time a new trigger hits my first 'logon' runner it still has the session and so my logon fails (as it should) because it already has a session and thinks its logged on. If the same test is run just in SoapUI it always gets a new session. Is there anything we can do to fix this? I would desire to have a session per 'user' triggered.
Also, on the issue of generators, I would like to do a ramp up of 'fixed load' which is appropriate for this kind of test. At the moment I use the fixed load generator and ramp it manually. None of the other generators had the second input for the feedback on running requests, is there anything coming to help with this?
Thanks.
