Features Added to Ready! API 1.5

Improved Plugin Manager. The Plugin Manager dialog has two tabs that let you easily see installed and available plugins, and install, update or remove a plugin.

Changes in the licensing subsystem: Ready! API will remind you to renew the license in 60, 30 and 5 days before expiration.

Improved project creation from URL. Ready! API will suggest to create a SoapUI NG TestCase immediately after you create a REST project.

Optimized memory consumption on start.

The Start Page has been improved.

Tutorials were moved to installation folder (API-1802)

Optimized memory consumption.

Test Suites run from project level will highlight whether they passed or failed. (SOAP-1828)

You can configure and store multiple connection setups for JDBC TestStep. (SOAP-2137)

You can define TEMPLATE parameters in the HTTP Request TestStep. (SOAP-2196)

The error message when importing invalid WSDL contains the line on which the error occurred. (SOAP-3160)

A number of bugs have been fixed.

Cloud testing. You can run Ready! API on your computer and use Amazon EC2 machines to simulate virtual users. Version 1.5 makes the cloud testing really easy. All you need is an Amazon account and Internet connection. SmartBear offers a number of publicly available pre-configured Amazon machine images, so you do not have to create and set up the images yourself. In your load test, you simply create Load Agents that will run on Amazon EC2 computers and then define the machine's region, image type, and other parameters.

When you run a test, Ready! API automatically starts cloud computers (instances), runs scenarios on them, gets results and terminates the instances if they are no longer needed. All these actions are done automatically, without asking you additional questions and without writing any script code. See Creating Distributed Cloud Tests for complete information.

Also, Ready! API estimates the cost of a cloud test run and displays a notification before you start the test helping you to keep expenses under budget.

Conditional logging capabilities. The load test editor has a new Log page, where you can view information on simulated requests: start time, duration, size and so on. By default, this log is empty. You create special rules to log only those requests that you are interested in. Creating the rules is scriptless, you do this visually in a special dialog. Using the new functionality, you can easily create rules, for example, for logging requests that run slowly. See Transaction Log Page.

Setup and Teardown scripts. In version 1.5, you can create Groovy scripts that will run at the beginning and at the end of the test run. You can use these scripts to perform various initialization and finalization actions in your tests like opening and closing files, or locking and unlocking resources you use. You create these scripts on the new Scripts page of the load test editor. See Setup and Teardown Scripts.

Skip the first minutes of a Load test. When a load test starts, there are often very high Time taken values in the results, due to startup time for the API services. In order to avoid these numbers being included in hte reports, you can set LoadUI NG to wait a while before collecting results. See Metrics.

Optimized memory consumption and improved performance.

A number of bugs have been fixed.

Better reporting: Ready! API does not truncate error descriptions in reports anymore. (API-1933)

A number of bugs have been fixed.

New Parameter dispatch strategy for REST Virts. Using the new strategy you can easily define what response a Virt will return depending on the incoming request parameters. In earlier versions, to create this functionality you had to write scripts. See Parameter Dispatching.

A number of bugs have been fixed.