Projects and TestCases

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 component bar in the Workspace View to the list of projects; you will be prompted for name, filename and if to open the project directly;

(You can of course open an existing project by simply double-clicking it in the Project List).

Opening a project brings you to the Project View:

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

• The Component Toolbar to the left from which you add components to your project (or TestCase, see below) by dragging them on to the work area
• The Project menu to the top right with Project-Specific actions
• The Runner toolbar for starting / pausing / stopping your test and setting desired execution limits
• A number of toolbar buttons to the top right for reports, settings, etc.

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 Project Canvas and connect them appropriately. The following component categories are currently available:

• TestCase : for creating LoadTests that can be deployed on loadUI Agents (read more)
• Generators : used for generating trigger messages sent to runner components that actually sample the system you want to test.
• Runners : are the actual components that sample the system you are testing, for example by sending a web request (the Web Page Runner) or runner a complete soapUI TestCase (the soapUI Runner).
• Analysis : used for analyzing and asserting response data from runners
• Flow : for controlling Load Test execution and load generation when there are multiple generators or runners involved
• Scheduler : for scheduling the execution status of other components (primarily Generators) during the execution of your Load Test.
• Output : for gathering, viewing and saving output from components
• Misc : miscellaneous components

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

Adding TestCases

loadUI further allows you to create any number of TestCases in your project; a TestCase is basically a separate collection of components that can be executed indecently of your test and that can be deployed to a remote loadUI Agent (this is the core of the distributed testing functionality).

Add a new TestCase to your project by simply dragging it from the component bar on to the Project View:

Once created as in the screenshot above, double-click the TestCase to open it for editing, which will open the following view:

This is basically the same view are as you had at the project level, the only differences being;

• The Project menu at the top has been minimized and the project run toolbar compressed to just showing the counters and start/stop buttons
• A TestCase menu has been added at the top of the window together with a dedicated TestCase runner toolbar for controlling the TestCase execution
• The TestCase Category is no longer available from the Component toolbar (since you cannot nest TestCases)

When you add components and close the TestCase, it will display a miniature of its setup in the project view:

(The toolbar on the TestCase component at this level allows you to control TestCase execution just as you can with the toolbar inside the TestCase View)

As mentioned above, one of the main reasons for setting up your load scenario in a TestCase instead of at the project level is that you can distribute it to any desired number of remote loadUI Agents, read more about distributed testing in Agents and Distribution.