User rating:
4.8 (12 ratings)

The content on this page is related to a deprecated version of LoadUI, which has been superseded by LoadUI NG Pro in the Ready! API platform. Click here to learn more.

Most of the things you want to do within LoadUI will be done within the scope of a LoadUI Project. Create a new project by simply dragging a New Project from the toolbar in the Workspace View to the list of projects; you will be prompted for name, filename and whether to open the project directly.


Existing projects can be opened by simply double-clicking them in the Project List. Opening a project brings you to the Project View:

1. The Project View


This is the main working area in LoadUI; here you create and run your actual load tests. Main components of this view are:

  • The Component Toolbar 1_snag_evi to the left from which you add components to your project (or Scenario, see below) by dragging them on to the grid.
  • The Playback panel 2_snag_evi for starting/stopping your test and setting desired execution limits.
  • The Project menu 3_snag_evi to the top right with project-specific actions

At the bottom right of the Project View you have a Navigation panel that shows a zoomed out view of all components, allowing you to easily pan around a larger setup of components.

All you have to do now to get started with your load testing is drag the desired components from the Component Toolbar to the left on to the grid and connect them appropriately. The following component categories are available:

  • VU Scenarios: for creating scenarios for Virtual Users, that can be run locally or be deployed on LoadUI Agents (read more).
  • VU Generators : used for generating Virtual Users.
  • Runners : are the actual components that sample the system you are testing, for example by sending a web request (the Web Page Runner) or run complete SoapUI TestCases (the SoapUI Runner).
  • Flow : for controlling the flow of Virtual Users.
  • Scheduler : for scheduling the execution status (on/off) of other components (primarily Generators and Scenarios).
  • Output : for gathering, viewing and saving output from components.
  • Misc : miscellaneous components.

Learn more about components in the Component Overview and Using Components documents.

2. Limits

Now that you have started up your LoadUI Project and perhaps added some components, let's look at how you actually run your tests in LoadUI. The top of the Project View contains a Playback Panel for this purpose:


The buttons to the left start/pause and stop your test, the three counters show the total number of requests, execution time and number of failures and the right buttons let you reset the counters (“Reset”) and set execution Limits (“Limits”) if you don’t want the test to run for ever. Clicking the start button accordingly starts the timer and you will see the counters increasing;


If you have set limits for any of these counters a corresponding progress bar will be shown for each limit:


Starting the test sends a start-message to all components in your project, which will result them in taking according actions:

  • All components will reset their corresponding counters if the start is not after a Pause
  • Generators will start generating trigger messages in line with their configuration
  • Scheduler components will start sending start and stop messages as configured
  • Other components may behave as desired, for example the MockService component will start the contained SoapUI MockService as configured.

While the test is running you can add components and Scenarios, configure them , connect them, etc as you did previously. In fact, you can start a new LoadUI Project by running it (before adding any components at all) and see how things start working while you add and configure them, a practice we call “Exploratory Load Testing”.

You can pause a running test by clicking the run/pause button while it is running; this will suspend components actions until you resume the test by pressing run again. Alternatively you can click the Stop button which will finalize the test so you can create reports, etc. When stopping the test, all runners with running requests are allowed to finish, which will be displayed with a “Stopping Test” dialog containing an “Abort” button; clicking this will terminate any running actions immediately.


Quick tip:

A convenient way of moving around the Project Canvas is by holding down the Ctrl (or Cmd) key and grabbing & dragging the canvas using your left mouse button. You can also use the mouse scroll wheel.