soapUI 3.6 introduces a number of loadUI integration points for running soapUI TestCases from inside loadUI instead of using the Load Testing functionality in soapUI. Before we look at these different options, lets take a quick look at the major benefits provided by loadUI over soapUI for Load Testing:
- Distributed Load Testing : loadUI allows you to easily distribute your Load Tests to any desired number of loadUI Agents by simply dragging and dropping the tests as required which makes it easy to simulate load or traffic not possible from a single machine.
- Run multiple TestCases simultaneously : in loadUI you can run any number of soapUI TestCases in any combination required, with different load generators, schedules and agents. For example you might want to divide load betwsoapUI TestCase when triggered:een 3 TestCases, all ramping up from one load to another.
- Long-running Tests : loadUI tests can be run for weeks without consuming your memory or CPU, allowing you to have base-line tests executing in the background with as advanced configurations as neccessary
- Interactive Load Testing : change and load-related parameters in real-time to see how your service and response times are affected.
Head straight over to the loadUI website if you want to know more about loadUI, now let's have a look at the integration points available in soapUI.
Note: both loadUI and soapUI have artifacts named "TestCase", in soapUI it is a functional test containing a number of TestSteps (as you probably know by now), in loadUI it is a collection of loadUI components that can be deployed on a loadUI Agent (read more).
loadUI Integration Overview
loadUI provides a "soapUI Runner" component that runs the configured soapUI TestCase when triggered:
(more details on this component are at the loadUI website)
You can add as many of these components as desired to your loadUI Project, each for running different (or the same) soapUI TestCase with different loads, assertions, etc. The soapUI Runner stores a pointer to the target soapUI project file and contained TestCase which will be read into loadUI memory upon execution (internally loadUI uses the same execution engine for the soapUI TestCase as is used in soapUI), if the project file is updated on disk while loadUI is running it will automatically reload the project to ensure that the latest version is being used.
The integration wizards in soapUI basically all generate pre-configured soapUI Runner components for you, either on their own or together with other components, depending on the wizard used. All the wizards need a running loadUI instance for communicating the actual creation of components, projects, etc, so the first thing you will need to do is configure the path to your local loadUI installation in the global loadUI settings tab:
Once configured you can simply launch (or switch to) loadUI by pressing the loadUI button in the main toolbar (soapUI will automatically launch loadUI if required).
Run TestCase with loadUI
This is the simplest integration available; it adds a soapUI Runner for the current TestCase to the selected loadUI Project and TestCase:
- In case there is a Project opened in loadUI that project will be pre-selected and its contained TestCases will be pre-populated in the list.
- In case there is no project opened you will be asked to confirm if that project should be closed and soapUI runner will be possible to add only to the project level.
Also you can select existing soapUI runner in which case it will be updated with selected soapUI Project and TestCase.
Generate loadUI Tests
This is an option available at TestSuite level for adding multiple TestCases contained in selected TestSuite to loadUI.
For each of selected TestCases a soapUI runner is added on the level you choose.
Converting a LoadTest to loadUI
This is the basic option for converting a soapUI LoadTest to loadUI. Depending on LoadTest strategy additional components corresponding to the soapUI TestCase configuration are added to loadUI project or TestCase;
- a soapUI runner is created or updated
- a Load Generator component is added and configured corresponding to the selected strategy
- a Statistics component is added
- assertion components are added corresponding to the assertions in soapUI
Convert multiple LoadTest on TestCase level to loadUI TestCases
This is an option available on TestCase level of converting selected multiple LoadTests to loadUI TestCases
Convert multiple LoadTest on TestSuite level to loadUI TestCases
This is an option available on TestSuite level of converting selected multiple LoadTests to loadUI TestCases