LoadUI NG 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 NG yet. This topic highlights difference between these two products.
For information on the difference between LoadUI NG and LoadUI of earlier Ready! API versions, see Migrating to LoadUI NG.
Due to the difference between LoadUI NG and LoadUI Pro, projects are not fully compatible. Support for importing projects to LoadUI NG is limited.
If your project contains elements not implemented in LoadUI NG yet, the import will fail.
If you have a complex load test, you will need to recreate it in LoadUI NG. To learn how to create load tests in LoadUI NG, see the Creating Your First Load Test tutorial.
LoadUI Pro has one workspace that contains multiple LoadUI Pro projects.
In Ready! API, you can have as many workspaces as you want. See Working With Workspaces.
In LoadUI Pro, you create tests in the Design tab. In LoadUI NG, you do this in the Load Test editor. Here, you can configure your test parameters, control test execution and page the results:
In LoadUI Pro, you can specify test limits by using items of the Main Toolbar of the Project page.
LoadUI NG offers more powerful functionality:
You set the maximum test duration in the edit box of the Load Test editor. See Test Duration:
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.
The Runners test component is similar to the LoadUI Runner component in the Target setting. Currently, LoadUI NG 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.
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.
LoadUI NG 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.
LoadUI NG only supports the Loop flow. To add a loop to your load test, click on the toolbar and select the start and end targets.
Instead of the LoadUI Pro SoapUI Mock service, use ServiceV.
Instead of the Statistics tab, in LoadUI NG, 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.
As for the global statistics metrics, in LoadUI NG, you can see them on the Global Metrics graph of the Load Test editor:
The Report button on the LoadUI NG main toolbar is the same as the LoadUI Create Summary Report button.
In LoadUI NG, 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 NG Agent on your Agents similarly to how you install it for LoadUI Pro distributed tests.
In LoadUI NG, you create assertions in the Load Test editor. For more information, see Test Assertions.
LoadUI NG 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.
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.
You can run LoadUI Pro tests from the command line. LoadUI NG does not support this feature so far.