Questions on LoadUI

Hi!

Your use case sounds like a perfect fit for loadUI+soapUI (honestly!).

ValueLabs wrote:
1) Are SoapUI PRO / Load UI and Load UI agents' supported in Solaris OS (compatibility)

All of these should technically work in Solaris, but we don't officially support Solaris.

ValueLabs wrote:
2) What is the PORT used for communication between LoadUI controller and Load UI agent.

Port 8443 is standard, but it can easily be changed.

ValueLabs wrote:
3) How do we set up a Load Test scenario by importing multiple test cases from SoapUI Pro

Basically, the only thing you need to do is to use a soapUI Runner in loadUI and point it to your TestCase. Read more here.

LoadUI 2.0 will have larger focus on soapUI integration and features a new soapUI Runner that integrates even better (visually and technically). It will for example make it easier to transfer sessions between soapUI Runners (e.g. Login, Delay, Search, Loop, Split based on probability, Logout or Purchase etc.). The first beta of 2.0 will be released in about two weeks.

ValueLabs wrote:
5) How do we distribute the user load (virtual users) among these test cases

You do this by using Generator components and route wires to the soapUI Runners. All this is covered in the documentation. In time for the first beta of loadUI 2.0, the documentation will be extended and contain much more video -- but the current documentation should definitely cover your question.

ValueLabs wrote:
6) How do we set up Ramp up / down plans for performance test execution

There's a Ramp component and we're currently considering adding an additional component just for this.

ValueLabs wrote:
7) How do we pin (capture) the server counters (AUT) in LoadUI

In loadUI 2.0 Pro, server monitoring is built in. Statistics is automatically saved in local databases, can be compared and mixed with Virtual User statistics.

ValueLabs wrote:
8) How do we Add User Defined Transactions in scripts

Could you please clarify this? You can load test any soapUI TestCase in loadUI, and soapUI is very flexible and features a lot of scripting capabilities. You can also build your own components and server monitors in loadUI using the same scripting language.

ValueLabs wrote:
9) How do we access different graphs (for analsis of performance test Results) like: i. Concurrent users ii. Transaction summary iii. Hits per Second vi. Throughput v. Server Counters data capturing

These statistics are all accessed from the Statistics Workbench in loadUI. This is all covered in the documentation here.

Hope this answers all your questions!

Henrik
SmartBear Software

Thank You for prompt reply. Yes, most of my questions are answered.

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)

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)

Now, I am eagerly waiting for LoadUI 2.0's release . Sounds like this would make Performance testing even more interesting and exciting.

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)

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

Thanks for providing the clarifications.

Regarding the Analysis Graphs: I just had a glance at Workbench component and I felt there is no much information about statistics (graphs) on Errors during the execution e.g. Errors per sec, type of errors etc.

Actually I have note started working on Analysis part (Workbench Component). Only after digging into it completely I would be able to give proper feedback.

ValueLabs wrote:
I just had a glance at Workbench component and I felt there is no much information about statistics (graphs) on Errors during the execution e.g. Errors per sec, type of errors etc..

All Runners have Failures statistics (Total and Per Second) [Statistics Reference].

/Henrik

Now our new Ramp component is ready to be tested.

I would like you to try the Ramp Sequence Generator, which I have attached to this post, in loadUI 2.0 beta 1. That one has support for RampUp -> Constant -> RampDown.

To install the component, unzip its content into the script-components folder of your loadUI installation.

Please let me know how how it worked for you!

Henrik
SmartBear Software

Thank You for providing this component. I will give my feebdback about it in couple of days.

Regards.

Do we have custom component or loadui2.0 supports rendezvous point ?

Thanks

phanisrikar wrote:
Do we have custom component or loadui2.0 supports rendezvous point ?

Not currently, but I'm sure that it would not be hard to create as a custom component.

/Henrik, SmartBear

By the way -- what would be an example use case for this component?

/Henrik