This topic describes the changes made to ReadyAPI 2.2.
Built-in support for OpenAPI 3.0 specifications. This means you can –
Add OpenAPI 3.0 specifications to your ReadyAPI projects.
Create and run test requests based on these specifications.
Use assertions to verify the response contents according to your OpenAPI specs.
Create virtual services from OpenAPI 3.0 specs (and, if your spec contains example data for responses, ReadyAPI Virtualization will generate virtual responses based on these examples).
Support for the OpenAPI 3.0 format is built into ReadyAPI. No plugin is required for this.
We have also ported support for earlier Swagger versions to the product (Swagger 1.x and 2.0). So, the ReadyAPI Swagger plugin is not needed anymore.
JMS support no longer requires Hermes. Now, ReadyAPI does not require that you configure JMS provider connections, topics and queues with HermesJMS. You can specify all the needed settings in the ReadyAPI user interface:
You can create new JMS endpoints without HermesJMS (see JMS Manual Configuration).
Each ReadyAPI project now maintains the repository of JMS connections you created for this project. You can access it from the main toolbar:
This command opens a dialog box where you can create, edit and delete JMS server configurations. You will use them later to create JMS request test steps and JMS virtual services.
The Environment dialog now contains the new JMS Server tab where you can customize JMS server settings for different environments.
Memory and CPU usage monitoring during the test run. When you start a functional or load test run, ReadyAPI automatically starts monitoring memory and CPU usage. Heavy memory consumption or CPU usage can slow down the test engine and cause erroneous test results. If the ReadyAPI monitor detects too high memory or CPU usage, it displays a notification message to you warn you about possible problems. See Monitor System Performance for details.
Encrypting individual project properties. In addition to protecting the entire project with a password, you can now encrypt one or multiple custom project properties. Use the new Encryption mode project property to set an encryption scope. See Protecting Sensitive Data for details.
Increased performance and productivity. The product starts and works faster now.
The Logs button in the left-bottom corner has been renamed to Show logs and has an icon. All these will help you find logs faster.
Also, you can use the new Clear all logs command in the context menu to remove all the messages from all these logs at a time.
You can now activate your ReadyAPI license directly from the console while running a test from Maven.
Documentation now includes extensive instructions on integrating and running ReadyAPI tests from Microsoft Visual Studio Team Services
We have also fixed a number of bugs reported by our customers.
Extended authentication support. Version 2.2 supports the following authentication methods:
Validating data of Swagger 2.0 requests and responses at design time. You can now validate parameter values in requests and responses based on Swagger 2.0 JSON and YAML specifications. See Validate Requests and Responses.
Signing SOAP requests using HMAC signatures. To support this, we have added the Secret Key key identifier type to the Signature WSS entry.
The Get Data dialog now selects properties of the current test case by default. This new behavior helps you find and insert properties into requests and responses faster.
MongoDB server monitoring. Create monitors for your MongoDB server to check how your database works under a load. See MongoDB Monitor.
Support for the SNMP version 3 monitors on Unix servers.
Tighter and smarter integration with the Amazon cloud services:
LoadUI now gets information on Amazon EC2 regions dynamically. You can launch cloud machines in any geographical region, and they can be of any type that your Amazon account supports.
Cloud LoadUI Agents now terminate automatically if the computer, where you run the test, is unavailable for several minutes. This helps you save the money you would pay for running instances otherwise.
Now, when an error occurs during a test run, LoadUI displays a message below the Global Metrics graph:
Click the message to open the LoadUI Log tab with a detailed description of the errors.
The LoadTestRunner utility now posts the number of simulated virtual users and the number of transactions per second to the log.
Creating data source properties from properties of JSON response objects. See DataSources in Virts for details.
Support for the JSONPath expression in the Query Match dispatcher. Now, when you use the Query Match dispatch strategy, you can use the JSONPath expression to extract values from the REST request body in the JSON format.
More convenient script editing. When you use the Script dispatch strategy, you can enter Groovy script code in a separate pop-up editor window, not just in the text box in the panel on the right. Open this editor by clicking the new button.
A new toolbar command – Clear transaction log – helps you quickly remove all the messages from the Transaction Log.
Installing and running VirtServer as a service. The installation wizard has now options for installing and running VirtServer as a service on Windows. Also, we have added instructions to documentation on running VirtServer as a daemon on Linux systems. See Run VirtServer as Service.
Starting and stopping virtual services by tags. The new command-line parameters of the
virtserver-cli utility let you assign tags to virtual services, and start and stop virtual services by their tag values. See VirtServer Command-Line Arguments.
Clearer phrases and error messages in VirtServer logs and WebUI.