Applies to ReadyAPI 2.1, last modified on August 1, 2017

LoadUI offers a new load testing engine and user interface relative to LoadUI Pro. The products differ significantly: some features have been changed, some other features have not been implemented in LoadUI yet. This topic highlights difference between these two products.

For information on the difference between LoadUI and LoadUI of earlier ReadyAPI versions, see Migrating to LoadUI.

LoadUI Pro Projects

Due to the difference between LoadUI and LoadUI Pro, projects are not fully compatible. Support for importing projects to LoadUI is limited.

If your project contains elements not implemented in LoadUI yet, the import will fail.

If you have a complex load test, you will need to recreate it in LoadUI. To learn how to create load tests in LoadUI, see the Creating Your First Load Test tutorial.

The Workspace Page

LoadUI Pro has one workspace that contains multiple LoadUI Pro projects.

In ReadyAPI, you can have as many workspaces as you want. See Working With Workspaces.

The Design Tab

In LoadUI Pro, you create tests in the Design tab. In LoadUI, you do this in the Load Test editor. Here, you can configure your test parameters, control test execution and page the results:

API load testing in ReadyAPI:  The Load Test Editor

Click the image to enlarge it.

Limits

In LoadUI Pro, you can specify test limits by using items of the Main Toolbar of the Project page.

LoadUI offers more powerful functionality:

  • You set the maximum test duration in the edit box of the Load Test editor. See Test Duration:

    API load testing in ReadyAPI: Test Duration

    Click the image to enlarge it.

  • To limit the maximum number of simulated requests, add the Requests – Total load test assertion, specify the Max value for it and enable its Stop load test on failure property.

  • To stop the test after a certain number of failures occur, add a Failures – Total load test assertion, specify the Max value for it and enable its Stop load test on failure property.

  • You can also limit the test by the number of simulated SoapUI test cases by setting the Max Target Runs property.

You can use more assertions to control the test execution and validate the server performance.

Test Components

  • Generators

    Instead of generators, in LoadUI, you use the load type and load profile settings that let you configure the load generation parameters in a more flexible manner.

    API load testing with ReadyAPI: Load Type and Load Profile Settings

    Click the image to enlarge it.

  • Runners

    The Runners test component is similar to the LoadUI Runner component in the Target setting. Currently, LoadUI supports the following targets:

    • The TestCase target corresponds to SoapUI Runner.

    • The URL target corresponds to HTTP Runner.

    • A new SingleRequest target that runs a single request to the API. This is equivalent to using SoapUI Runner with a single REST Request test step.

      API load testing with ReadyAPI: Single Request Target

      Click the image to enlarge it.

  • Scenarios

    All load tests are now parts of scenarios. Your tests will always have at least one scenario. You can add as many scenarios as you need.

    API load testing with ReadyAPI: Scenarios in Load Tests

    Click the image to enlarge it.

  • Schedulers

    LoadUI currently supports the Interval scheduler only. This scheduler works in the same way as in LoadUI Pro. To configure it, switch to the Scheduler page.

    API load testing with ReadyAPI: The Scheduler Page

    Click the image to enlarge it.

  • Flow

    LoadUI only supports the Loop flow. To add a loop to your load test, click on the toolbar and select the start and end targets.

    API load testing with ReadyAPI: The Target Loop Editor

    Click the image to enlarge it.

  • Service Mocking

    Instead of the LoadUI Pro SoapUI Mock service, use ServiceV.

Statistics Tab

  • Instead of the Statistics tab, in LoadUI, you use the Statistics page of the Load Test editor. It allows you to create custom graphs and reports, compare results of different test runs, and export results to CSV or PDF files.

    API load testing with ReadyAPI: The Statistics Page

    Click the image to enlarge it.

  • As for the global statistics metrics, in LoadUI, you can see them on the Global Metrics graph of the Load Test editor:

    API load testing with ReadyAPI: The Global Metrics Graph

    Click the image to enlarge it.

Summary Report

The Report button on the LoadUI main toolbar is the same as the LoadUI Create Summary Report button.

API load testing with ReadyAPI: The Report Button

Distributed Tests

In LoadUI, you use the Distribution page to create and edit your load tests. You use this panel both to create load agents and work with them. You will also need to install the LoadUI Agent on your Agents similarly to how you install it for LoadUI Pro distributed tests.

Assertions

In LoadUI, you create assertions in the Load Test editor. For more information, see Test Assertions.

LoadUI displays the minimal and maximum values of an assertion as horizontal lines in the Global Metrics chart in the Load Test editor. In LoadUI Pro charts, assertion limits are displayed as vertical lines.

Server Monitoring

Instead of the Monitors tab, you use the Monitoring page of the Load Test editor. Using this page, you can create servers, add monitors to them, and configure runtime metrics similarly to the way you did it in LoadUI Pro.

API load testing with ReadyAPI: The Monitoring Page

Command-Line Interface

You can run LoadUI Pro tests from the command line. LoadUI does not support this feature so far.

See Also

Migrating From SoapUI Load Tests
Workspaces
Setting Up Load Tests
Distributed Load Testing
Test Results