Features Added to ReadyAPI 2.4

Quick search in the Navigator panel. The Navigator panel in Projects and SoapUI has a new search box at the top to help you quickly find test steps, cases, suites, resources and other items of your APIs and projects:          

Updated REST Discovery dialog. The REST Discovery dialog has been improved for better user experience.

Reader-friendly HTTP log. We’ve reformatted the data the HTTP log displays, so it is now easier to analyze HTTP traffic.

Updated reports:

• The names of the default report templates have become clearer.

• All the available report templates are visible in the Create Report dialog at once. So, you can easily examine the list and select the desired option:

  

• We have added the Report button to the SoapUI toolbar to make it easier to invoke the Create Report dialog:

  

Faster start for novice users:

• ReadyAPI displays hints that tell users how they can make their tests more powerful and flexible: use data in request parameters, use scripts, set up and change environments.

• A new Quick Tour in LoadUI will help new users learn the product faster.

More persistent UI. ReadyAPI now stores information on the width and height of the panels between sessions, which frees you from customizing the UI after restarting the product.

Upon creating a new project, ReadyAPI now inserts sample script code into the RequestFilter.filterRequest and TestRunListener.afterStep event handlers. This makes it easier for you to understand how to use these events.

You can now switch environments from the Projects toolbar:

Also, the Environments dialog now lists the environments in alphabetical order.

The Outline tab in the request editor uses a new font that supports special characters and emojis.

The search boxes in the Get Data dialog now have the X icon to help you clear the boxes faster.

Improved SwaggerHub support. You can now import private OpenAPI (Swagger) definitions from SwaggerHub via the Swagger plugin.

Better RAML support. ReadyAPI can now open RAML 1.0 specifications.

Improved ReadyAPI performance and Groovy script execution. They were improved by implementing support for the Java 7 invokedynamic feature.

Better support for custom libraries:

• You can now add any JAR files to the classpath when starting ReadyAPI. To do this, use the Custom Java Libraries option in the ReadyAPI Preferences dialog.

• The Code completion list now shows methods and properties from JAR libraries located in the /lib, bin/ext and custom Java libraries.

Version 2.4 offers new JVM options – Dhttpclient.spnego.usecanonicalname and Dhttpclient.kerberos.usecanonicalname – to help you avoid issues with SPNEGO/Kerberos authentication. These options control the use of host names during authentication steps and help you work around wrong reverse DNS lookups. See Additional Authorization Settings for details.

File names of project items now match the item names. Composite projects store project items (test cases, suites, and others) in separate files. Formerly, if you renamed a project item, for instance, a test case, the test case’s file name did not change. This could cause confusion when you added files to source controls or explored them in a file manager.

To avoid possible issues, version 2.4 establishes a match between the file name and the project item name. When you rename an item in your composite project, the item’s file is renamed as well.

Now, the Required attribute of REST requests is set to true when you add requests to your service manually, or when you create a service from a URL or with the Discovery wizard. If you create a service from its definition, the attribute is read from the definition file.

A number of libraries used in ReadyAPI 2.3.0 have been updated.

New Jenkins plugin. SmartBear offers a new SoapUI plugin for Jenkins. It will help you easily set up and run your SoapUI functional tests from Jenkins jobs. See Running ReadyAPI Tests From Jenkins for details.

Easier setup of command-line parameters. You configure parameters for the command line in the Launcher TestRunner dialog. In version 2.4, this dialog has been improved:

• It has the new General CLI button that generates a command line for the call, but does not launch the runner.

• It automatically populates the edit fields at the first launch:

  • The path to the TestRunner file is set automatically.

  • The Print Report, Export JUnit Results, Export All options are enabled by default.

  • The root folder defaults to $ {WORKSPACE} (this points to the Jenkins workspace folder).

  • The report format defaults to XML.

Easier request selection. The dialog, in which you pick requests for test steps, has a new look. Now it shows requests and resources in a tree-like structure. Also, it has a new search box at the top to help you find the needed request quickly:

Use of JSON Web Tokens during OAuth 2.0 authorization. You can now send JWT assertions in the JWT Profile for Authorization Grants, as well as attach JWT assertions to the Authorization Code, Client Credentials and Resource Owner Password Credentials grants.

New panels to display JDBC transaction data. The JDBC Request editor has new tabs to help you view data of JDBC transactions:

Click the image to enlarge it.

Support for SSL connections in MQTT test steps. For details, see the test step descriptions.

Easier file selection for the Swagger Compliance assertion. The Swagger Compliance dialog box has a new button that lets you visually select a definition file. In earlier versions, you had to type the file name.

The Excel data sink can now append data to Excel worksheets.

The Preferences > Default Test Case Options dialog has a new option to set the default value of the Discard PASS Results within Loop property of the newly created DataSource Loop test steps.

The button on the ReadyAPI toolbar can now run test cases, suites and projects, as well as individual requests and Groovy scripts. Formerly, it did not support running requests and scripts: