LoadUI NG is Ready! API's load testing tool. It uses SoapUI NG's TestCases to simulate massive load on the tested web site or web service. It helps you check how your server performs under load and estimate its limits.
Load Testing means running functional tests many times in parallel or consecutively to simulate the load on the server and see how the system behaves under these conditions. The load is not always high, the test can be in how a system handles base or expected load. For more information on different load strategies, see Testing Scenarios.
A good load test does not send random requests to the server. Instead, it tries to simulate user behavior. For example, if a web site provides API, you want to send API requests for it to handle and then check that it responded correctly and quick enough.
Good load tests also assert performance to provide insight into the causes for slow server responses. Because of the way servers operate there are many possible causes for test slowdowns or sudden spikes of poor performance. For more information about asserting performance in LoadUI NG, see About Assertions.
Sometimes the issue will be on the server side. A good load testing tool should be able to access all server-side metrics and display them to the tester during the test run, as well as storing the results. For more information about monitoring servers in LoadUI NG, see About Server Monitoring
For more information about load testing, you can read the What Is Load Testing? article on the SmartBear website.
LoadUI NG is a part of Ready! API and is available to all users of the product.
Base LoadUI NG functionality is available for free to any user who has a license for any tool of Ready! API (for instance, base load testing features are available for the SoapUI NG Pro users).
Pro licenses allow you to take advantage of all the features of LoadUI NG.
For information on differences between the licenses, see below.
Ready! API includes a number of sample projects that demonstrate various product features. You can find these samples in the <Ready! API installation directory>\tutorials\load directory. All samples include an example of how you can use Setup and Teardown scripts in your tests.
Note: The changes you make in the sample projects cannot be saved. This means that if you make some changes, you will have to save the project as a new one. The original file will remain unchanged.