Questions on LoadUI

ValueLabs wrote:
Clarification on My Question 8 (How do we Add User Defined Transactions in scripts): Basically what I mean is, are there any functions like "Start_Transaction {Admin-Login}" and "End_Transaction {Admin-Login}" which would have a set of requests (from LoadUI to AUT Server) in it. So in the final report I would hope to see like "Admin-Login = 0.96 secs" (Avg. response time)

If you design the transaction in soapUI, and use the soapUI Runner in loadUI, statistics are recorded both for the whole transaction and (optionally) the individual steps.

ValueLabs wrote:
Apart from this, can you please let me know how could we change the default port settings to change 8443 (PORT used for communication between LoadUI controller and Load UI agent) to a desired value (we still dont know what all PORTS are open on Environment Under Test)

It's explained here, in the Agents and Distribution page of the documentation.

ValueLabs wrote:
I am attaching a sheet comparing features of Loadrunner, WAPT, LoadUI/SoapUI (Just for reference, might help you guys getting new ideas ). To my knowledge, most of the information provided in it is correct (Sorry!! if you find any discrepancies)

It seems mostly correct to me A few comments/discrepancies though:

• Web recording is available in soapUI (and therefore loadUI), although it's limited.


• Regarding Transactions, see my comment above.


• Rendezvous points can be made as a custom component; but if that's not an option, loadUI doesn't support it yet.


• Ramp up/down plan can be achieved in loadUI by combining schedulers and generators (ramp and fixed rate). It's not as easy as it could be in the case of rampUp-steady-rampDown (implementing a component for solely this purpose is actually in our backlog, but I won't promise that it makes it into loadUI 2.0).


• I would definitely say that loadUI supports adding periodic load to the AUT, this can be done with either scheduler components, variance generators, or any combination of these.


• Adding HTTP headers can be done in soapUI (and therefore loadUI with the soapUI Runner).


• Regarding the comment Load UI
  [...] have very less no. of analysis graphs available -- have you had a look at the Statistic Workbench in loadUI (each runner component automatically records 28 statistics)? If so, what do you think is missing?

Regards

Henrik
SmartBear Software


Henrik
SmartBear Software