Features Added to ReadyAPI 2.1

Overall Improvements

SoapUI

LoadUI

ServiceV

More

• The Dashboard includes a few improvements:

  • A new Test Case Status tile to help you oversee the statuses of test cases that ran recently. The tile shows results of individual test case runs, as well as results of test cases that were executed as part of a test suite or project run. All this data help you track the test execution status and estimate the quality of your APIs easier.

  • The Virtual APIs tile has the Search edit box now. It helps you find a virtual service in the list quickly: simply start typing the service name, location or port number, and the tile will filter the list of virtual services on-the-fly:

    

  • Now, after you generate a report in some tile, the Dashboard automatically opens this report for a preview. You can check the report data, and if it suites your needs, save the report to a file or print it. Earlier versions of the product did not support the preview.

  • Creating new tiles has become easier: you can now do this by right-clicking an empty space in the Dashboard. The “Add New Tile” toolbar button that existed in previous versions is still available, as well.

• Discovery feature improvements:

  • API Discovery uses a new algorithm for recording HTTPS traffic in proxy mode for external clients. It makes the recording more stable and issue-free.

  • Version 2.1 has a new setting – Hostname verification – that lets you turn off server name verification when recording HTTPS requests and responses. This helps you discover APIs that reside on servers whose names differ from the server names specified in the certificate.

• The user interface of ReadyAPI is DPI-aware now. This primarily concerns Windows machines. The UI elements and panels are scaled properly on monitors with non-standard DPI settings now.
  The DPI support is available only if you run the ReadyAPI executable. It is not available currently if you run ReadyAPI .jar modules.

• In version 2.1, we introduce the practice of updating the ReadyAPI Maven plugin for maintenance ReadyAPI builds. To use an updated plugin, specify its version in your Maven project. For ReadyAPI 2.1, the version is 2.1.0-m-SNAPSHOT.

• You can now specify property expansions in data cells of the Grid data sources. This makes it easier for you to update the test data for your test runs.

• To build and display reports, ReadyAPI now uses JasperReports Library version 6.4.0. You can use features and properties of this new library version in your custom reports.

• We have also fixed a number of bugs reported by our customers.

• Version 2.1 includes a new requestAccessToken method for automatic updates of OAuth 2.0 tokens. Earlier, to update these tokens, you had to use special editors and dialogs in the product UI. Now, you can update the tokens automatically by calling this method before the request simulation. You can call the method, for example, within the SubmitListener.beforeSubmit event handler that is executed before the test engine sends a request to the tested server. See the sample script below.

  Sample Script

  Sample ScriptSample Script

  Groovy

  Groovy

  import com.eviware.soapui.impl.rest.actions.oauth.OltuOAuth2ClientFacade;
  import com.eviware.soapui.support.editor.inspectors.auth.TokenType;
  import com.eviware.soapui.model.support.ModelSupport;
  
  def project = ModelSupport.getModelItemProject(context.getModelItem());
  def authProfile = project.getAuthRepository().getEntry("oAuth profile name");
  def oldToken = authProfile.getAccessToken();
  def tokenType = TokenType.ACCESS;
  def oAuthFacade = new OltuOAuth2ClientFacade(tokenType);
  oAuthFacade.requestAccessToken(authProfile, true, true);
  // sleep method can be used instead of while loop
  // sleep(3000);
  while(oldToken == authProfile.getAccessToken()) {
  }
  
  log.info("Set new token: " + authProfile.getAccessToken());

• You can now edit response data in the JSON and XML response editors of the REST and SOAP requests. This makes it easier to create and debug assertions that check response contents.

• You can now use property expansions in properties of the File Wait test step to specify the name of the file to wait for. This makes the test step more flexible as you can tweak property values in your tests.

• The properties of the Run TestCase test step also support property expansions now.

• A new Recreate command in the REST request editor helps you easily recreate the message contents from a representation defined in your API spec.

• According to our customer requests, we updated the DataGen test step – now, it uses the BigDecimal data type for numerical values. This lets you store larger values that could not be used earlier.

  To generate test data, we would recommend using the Data Source test steps of the Data Generator type rather than the DataGen test step. Data Generator is the future direction for enhancements in this area; the DataGen step will remain in the product, but will not evolve.

• The Shared setting of new DataSource test steps is selected by default now. This makes the data sources prepared for load testing in a better way. You can find the setting on the Load Testing tab of the DataSource Options dialog.

• Two new Statistics metrics – “The 95th percentile” and “The 98th percentile” – make the analysis of your load testing results easier.

• The ReadyAPI package includes a newer version of the Amazon Java SDK library – version 1.11.136. You can use classes and methods provided by this new library in your Groovy scripts in LoadUI.

• You can now configure JMS virts without using HermesJMS. The Add New JMS Route dialog that you use for creating JMS virtual operations has a new Manual tab, where you can enter the needed parameters:

  

  SmartBear provides plugins with pre-configured settings for some popular JMS brokers. You can also use libraries that broker creators provide.

• New and buttons help you import properties from an external file and clear all configured properties of ServiceV data sources.

• You can now create JMS virtual operations faster by duplicating existing JMS operations.

• We have changed the product and feature names: Ready! API has become ReadyAPI, SoapUI NG – SoapUI, LoadUI NG – LoadUI. We hope these changes will help our Marketing team position and promote the product.

• To help trial users shorten the learning time and start faster, ReadyAPI 2.1 includes Chats – a new built-in panel for chatting with SmartBear engineers. To start a conversation, click the Chats icon in the top-right corner:

  

  Click the image to enlarge it.

• The composite projects that you create in ReadyAPI 2.1 now use the 1.3 version of the project format by default. This format means that project items – functional tests, load tests, security tests, and other – are stored in separate files. This makes the projects friendlier to source control systems.

• The default project names now end with -readyapi-project, for example, Project-1-readyapi-project.xml. Earlier, the default names were ending with -soapui-project.

  Packed projects you import must end with -readyapi-project.xml.

• The URL field in the New Functional Test wizard has a context menu with the Copy, Cut and Paste items.

• To invoke the context menu in the Navigator panel, you can now press Shift+F10.