Softpedia >Windows >Programming >Other Programming Files >ReadyAPI >  Changelog

ReadyAPI Changelog

What's new in ReadyAPI 3.52

Apr 18, 2024
  • PKCE flow for OIDC:
  • SLM Onpremise 2.0 now supports OIDC. When you configure OIDC and request a license from the SLM On-premise server, your login will undergo a PKCE flow. Remember, this requires SLM Onpremise License Server 2.0 with OIDC configured.
  • Support for Client Credentials in TestRunners and Plugins will come in future releases.
  • We added PKCE flow for users authenticating to VirtServer when VirtServer is configured for OIDC. This feature will be compatible with VirtServer 3.20.0 or later (3.20.0 releases at the end of April 2024).
  • We added vmoptions parameter that disables basic auth for Auth Profile verification that caused some issues during PKCE login.
  • ReadyAPI Feature Enhancement:
  • Some special characters like {, } will be replaced in automatically generated test case names based on request URLs due to compatibility issues with Groovy scripts.
  • By default, sniHostCheck is now set to false to prevent compatibility issues with the latest version of the Jetty library.
  • When selecting tags for custom arguments in TestRunner, you can now choose how to combine the tags using OR or AND operators.
  • Improvements:
  • We added a new vmoptions parameter to allow you to disable automatic product updates, product update notifications, and the option to check for updates.
  • We removed deprecated Windows .dll files that were used by the installer.
  • A warning will now appear when you close the script editor without saving changes.
  • We removed Optimizely, previously used for testing new features. Now, ReadyAPI startup should improve by approx. 10 seconds.
  • General Updates:
  • We updated TestEngine license location.
  • We updated the JDK to version 17.0.10.
  • ReadyAPI 3.52.0 includes newer versions of some libraries that version 3.51.0 used. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • Note:
  • It is recommended to skip version 3.52.0 if you're encountering the ReadyAPI freeze issue (RIA-21011) while retrieving the OAuth 2.0 token. The solution for this problem is not included in this version. Please wait for the next release for a fix.

New in ReadyAPI 3.51 (Feb 15, 2024)

  • Facilitated H2 Migration:
  • We introduced a migration tool enabling users to smoothly transition to the latest version of the H2 database. For more details, refer to H2 Migration page.
  • ReadyAPI Feature Enhancement:
  • We added the capability to bulk delete custom properties. Previously, users could only delete one custom property at a time. This enhancement enables users to select multiple items and perform a bulk action.
  • Improvements:
  • A warning is now displayed when deleting methods in ReadyAPI. It alerts users if the method they’re deleting is being used by any test steps.
  • Users can no longer delete a request if it’s used by any existing test step. To delete such a request, it is required to modify test steps.
  • In instances where ReadyAPI was unable to import a test step due to a missing request, a warning was previously shown separately for each test step. We have introduced an "OK to all" function, allowing users to close just one popup window for potentially many with larger projects.
  • Note: We have identified some use cases where ReadyAPI Windows users required broader character encoding through UTF-8. To set encoding to UTF-8, you need to make one configuration change to <readyapi-installation-folder>binReadyAPI.vmoptions. Insert a new line at the end and add -Dfile.encoding=UTF-8. Save, close the file, and open ReadyAPI. For additional details on setting the encoding to UTF-8, refer to this page.

New in ReadyAPI 3.49 (Oct 19, 2023)

  • GraphQL API from Introspection Query:
  • We implemented the capability to import GraphQL APIs from Introspection Query.
  • Improvements:
  • In ReadyAPI, transaction logs can be downloaded from REST, SOAP, TCP, JDBC and JMS virtual services hosted in VirtServer.
  • Enhanced privacy by concealing sensitive information under sun.java.command.
  • General Updates:
  • We have fixed a few blocker vulnerabilities javasecurity:S6096 reported by Sonarqube.
  • ReadyAPI 3.49.0 includes newer versions of some libraries that version 3.48.0 used. If your scripts refer to classes from these libraries, you might need to update the scripts.

New in ReadyAPI 3.48 (Sep 6, 2023)

  • Enhanced Authentication:
  • We introduced basic authentication with a username and password for SmartBear ID sign-ins. Click here to learn more.
  • ReadyAPI Feature Enhancement:
  • Added SSL support for AMQP.
  • Integrated JUnit 5 dependencies into the ReadyAPI project, allowing the creation of new tests using the latest JUnit version.
  • Optimized the authentication algorithm of automated scripts by extending the default time from 5000ms to 20000ms. Additionally, we added 5-second intervals to monitor authorization progress, enhancing the user experience and execution times of automated authorization.
  • General Updates:
  • Upgraded the Jira plugin to version 1.6.5. For more information, refer to this link.
  • Updated guava to version 32.0.1-jre in the axm repository.
  • Temporarily disabled the option to create a gRPC Virt Service.

New in ReadyAPI 3.47 (Jul 3, 2023)

  • Match TCP Requests:
  • ReadyAPI now offers the capability to match TCP requests using Groovy scripts, giving users greater flexibility and customization options. You can write scripts either for the entire TCP virtual service or for individual requests.
  • Jenkins Plugin:
  • ReadyAPI Jenkins plugin is extended to support SLM on-premise license server as well as the Smartbear SLM server and follows the same license authentication logic as the Azure plugin.
  • ReadyAPI Feature Enhancement:
  • You can download the local transaction log for HTTP Virtual Services from the ReadyAPI UI.
  • We added an “Uninstall” button that allows you to properly uninstall the Trial SLM Offline License. By doing so, we make it easier to uninstall your trial license and either use it on another machine or replace it with a production license.
  • General Updates:
  • ReadyAPI is updated to work with Java 17.0.7.

New in ReadyAPI 3.46.1 (May 31, 2023)

  • A Library update caused an issue for ProtectionLS floating license users while requesting a license. In this patch release, we have reverted to the original library.
  • We made some improvements to enhance the in-product trial request experience.
  • You can now configure your Vmoptions file to prevent it from being updated or overwritten during ReadyAPI upgrades.

New in ReadyAPI 3.46.0 (May 18, 2023)

  • Token Generation in AppDynamics:
  • We now offer the option to connect to AppDynamics using Client Name, Client Secret, and Account Name to generate a Token from within ReadyAPI. This is in addition to the existing method of providing a Token directly.
  • ReadyAPI Plugins
  • Maven Plugin:
  • We updated the ReadyAPI Maven Plugin to support ID-based or SLM licenses. To use this feature, we have added support for specifying SLM server parameters - accessKey (-K), username (-U), and password (-V).
  • Azure Plugin:
  • We updated the ReadyAPI Azure DevOps Plugin to support ID-based / SLM licenses.
  • Jenkins Plugin:
  • We updated the ReadyAPI Jenkins plugin that now enables ReadyAPI tests to be run on Jenkins in three different ways:
  • ReadyAPI Functional Testing plugin can now be used as a new Build step > ReadyAPI Test: Run functional Test (available from ReadyAPI 3.46.0 onwards).
  • Jenkins Pipeline can now be used with the SoapUI Pro Pipeline step (available from ReadyAPI 3.46.0 onwards).
  • Command-line runners can still be used, as before.
  • Starting from version 3.46.0, you can pass the Access Key as a "-K" parameter for the first two options listed above.
  • ReadyAPI Feature Enhancement:
  • If you set Access for Everyone on SLM on-premises, you no longer need to add Access Key credentials to your CLI command configuration for TestRunner, Performance Load Runner, Security Test Runner, and VirtRunner.
  • In that case, you can add the -D licenseApiAccessForEveryone=true flag to your CLI command.
  • Starting with ReadyAPI 3.46.0, SSL Connection parameters only require the CA Certificate as a mandatory field; the other fields are optional.
  • We updated the log4j logging functionality to prevent it from generating excessively large log files that could overrun available drive storage.
  • ReadyAPI now supports the setting and use of multi-value parameters as Media Type: multipart/form-data.
  • ReadyAPI 3.46.0 introduces the ability to configure an endpoint's proxy to not use any proxy and override the global proxy setting.
  • The configuration flag will be set to 'False/Unchecked' by default, indicating that the global proxy will not be ignored. However, when set to 'True/Checked', global settings will be ignored.
  • The setting is automatically saved when the corresponding project is saved.
  • Improvements:
  • In response to an error encountered while importing AsyncAPI from SwaggerHub, we have improved the error handling message.
  • We updated the default name of the generated JUnit reports from “SoapUI Test Results“ to – “JUnit Test Report“.
  • We updated the log messages displayed in ReadyAPI for Load Agents to show the source of the log messages.
  • General Updates:
  • ReadyAPI is updated to work with Java 17.0.6.
  • The License Management page is now automatically updated with the latest version of ReadyAPI.

New in ReadyAPI 3.45.0 (Apr 4, 2023)

  • Improved ReadyAPI UI VirtServer Panel:
  • We updated the ReadyAPI UI VirtServer Panel to improve the license expiry experience. If the license expires, the ReadyAPI VirtServer Panel will:
  • Enable the user to log into the VirtServer and view the:
  • Virtual Service details
  • Transaction Log
  • Activity
  • Metrics
  • Display the “VirtServer license has expired” message.
  • Prevent the user from deploying virtual services by showing a corresponding error message.
  • ReadyAPI Feature Enhancement:
  • We have added support for 'Brotli' compression in ReadyAPI. You can configure ReadyAPI to use this compression in the ReadyAPI HTTP Preferences panel. Please see more details on how to enable this feature.
  • The "Logout and release the licenses" button is now disabled when an offline license is installed for any ReadyAPI module. This update guides users to properly uninstall offline licenses to prevent them from remaining attached to the product and blocking other licenses.
  • You can configure the Commit message to be deleted once you have committed your changes in the ReadyAPI Git Preferences panel.
  • Update API Endpoints:
  • When updating an API, ReadyAPI now allows users to specify whether or not they also want to update API EndPoints. This is done by checking a new checkbox labeled "Update the EndPoints of the API."
  • By default, this checkbox is checked, and ReadyAPI behaves as it did before, updating the API's EndPoints.
  • If the checkbox is unchecked, the API's EndPoints will remain unchanged after the update.
  • Improvements:
  • We improved the main progress bar to ensure consistency across Load, Functional, and Security tests.
  • ReadyAPI now supports the import and usage of xlsm Excel file formats in data sources, with the same behavior as for xlsx files.
  • When using a specific value for the "content-type" metadata, ReadyAPI will now display the value in other test steps "content-type", saving time when filling out required parameters.
  • We updated ReadyAPI to allow the import of the latest Resolved AsyncAPI APIs from SwaggerHub. You can now filter the AsyncAPI APIs to be imported by selecting the "AsyncAPI" filter option.
  • General Updates:
  • We have fixed a few Security Vulnerabilities.

New in ReadyAPI 3.44.1 (Mar 16, 2023)

  • Fixes an issue affecting some users when activating trial licenses.

New in ReadyAPI 3.44.0 (Feb 23, 2023)

  • VirtService Deployment:
  • From now on, you can deploy the same VirtService on the same VirtServer multiple times in the ReadyAPI GUI by drag and drop. ReadyAPI will automatically create a copy of that service, assigning it a unique service ID and access port.
  • ReadyAPI Test Steps:
  • We added Webhooks, a new 'Test Steps' type for testing your async REST APIs. Also, support is available for the same.
  • Synchronization for Load Testing Virtual Services:
  • We added a feature flag that configures the 'Synchronization for Load Testing Virtual Services' setting. Now, you can prioritize processing speed over accuracy according to your needs.
  • ReadyAPI Improvements:
  • We improved the error message for saving a Test Case without a corresponding test suite. We made the text clear and easy to understand so you could respond appropriately.
  • To improve the readability of Smart Assertions in the Assertions tab, we have changed the default name from "Smart Assertion" to "Smart Assertion - Received Metadata" or "Smart Assertion - Received Data", depending on the assertion type.
  • General Updates:
  • We updated the ReadyAPI JPROD builds to use the latest JPROD version. For reference, please visit Productivity Protection - What's New in Protection.
  • When you attempt to create/update a JDBC connection with a connection string containing an unsupported character such as '_', a warning will appear in the
  • ReadyAPI GUI and the ReadyAPI logs:
  • From now on, you can import AsyncAPI 2.5.0 into ReadyAPI from file-based API definitions.
  • We have fixed a few Security Vulnerabilities.

New in ReadyAPI 3.43.1 (Jan 25, 2023)

  • ReadyAPI 3.43.1 is a Patch, released to address an important issue introduced in ReadyAPI 3.43.0. Some customers were restricted from using SmartBear-ID-based licenses with ReadyAPI and Virtual Machines. Now it is fixed.

New in ReadyAPI 3.43.0 (Jan 18, 2023)

  • Updated Plugins:
  • Postman plugin (Fixed Vulnerability Security issue)
  • GitHub – SmartBear/readyapi-postman-plugin
  • VirtService Deployment:
  • From now on, you can deploy the same VirtService on the same VirtServer multiple times in the ReadyAPI GUI by drag and drop. ReadyAPI will automatically create a copy of that service, assigning it a unique service ID and access port.
  • Enhanced Offline Key Request Process:
  • We streamlined the offline activation/deactivation key request process by using a web form instead of email. From now on, to activate/deactivate an offline license, please follow this link

New in ReadyAPI 3.42.2 (Dec 16, 2022)

  • Updated Plugins:
  • Jira plugin – updated to support Jira 8.2 and 9.1
  • AWS plugin (Fixed Vulnerability Security issue)

New in ReadyAPI 3.42.1 (Nov 28, 2022)

  • Fixed an issue that prevented users from using the Git Pull feature in ReadyAPI. The issue was introduced in the 3.42.0 version.
  • Fixed three related security vulnerabilities reported in JRE (CVE-2022-21618, CVE-2022-21624, CVE-2022-21626) by upgrading to 17.0.5.
  • Fixed an issue that prevented some Load Agents from having up-to-date project data at runtime, thus causing agents to not start or to fail during their runtime.
  • Now, if a Mac user receives ReadyAPI Update notifications, ReadyAPI will recommend the appropriate build to install (Apple Silicon CPU or Apple Intel x86-64) based on the user’s platform. In this case, ReadyAPI will ask the user to confirm installation or to select another version.

New in ReadyAPI 3.42.0 (Nov 8, 2022)

  • From 3.42.0, you can see the License Number and the Number of VUs corresponding to the license that you are about to install or that you have installed.
  • Added the possibility to stop a Load Test when one of its Data Sources is exhausted.
  • Added a new feature for the users to configure a Kafka subscriber to consume the messages published only after that subscriber was connected.
  • Added support for the users to invoke external test cases in isolation from within a Groovy script step. This will enable the users to use groovy scripts with shared resources in Load Test scenarios.
  • Created a public method (.getTestCaseCloneByName("Other Test Case Name")) to get a WsdlTestCase clone by its name in groovy scripts, allowing to invoke external test cases in isolation while running performance tests.
  • From this version, you can use and insert Property Expansions in the Authentication types via the Get Data menu.
  • The Jira plugin was updated to support the latest Jira versions (8.x and 9.2).
  • Updated Security Patch for the OpenSSL 3.0.7.
  • New Security updates for the Jira, Postman, and AWS plugins.
  • Added support for OAuth2.0 for Kafka in ReadyAPI.
  • Updated the Navigation Panel in ReadyAPI Documentation to make it easier to find the most commonly used topics.

New in ReadyAPI 3.41.1 (Oct 3, 2022)

  • The 3.41.1 patch was released to fix an installer issue for macOS introduced in 3.41.
  • In ReadyAPI 3.41, an issue was identified for macOS Monterey/M1 users updating to the latest ReadyAPI version by following the in-app update notification, or by downloading the ReadyAPI Trial version from the Trial Page. It is an issue related to the installation of Java Toolkit which resulted from the upgrade to the latest Java 17.0.4 version. Only M1 users encountered this problem. This was resolved.

New in ReadyAPI 3.41.0 (Sep 15, 2022)

  • ReadyAPI was updated to support Java 17.0.4 (from Java 17.0.2). (RIA-19888)
  • ReadyAPI has replaced the ‘Master’ Git terminology with the ‘Main’ naming. This update applies to the Git repositories which will be used from now in ReadyAPI. The existing Git repositories will continue to use their existing names. (RIA-19589)
  • You can now Search in the Navigator through Test Cases and Test Steps as well, not only through Test Suites. (RIA-18321)
  • Added the possibility to Save a Test Suite of a Composite Project. Saving a Test Suite will save all its Test Cases. (RIA-18003)
  • This is described further in Managing Test Cases and Managing Test Suites.
  • The OAuth2 process is updated to enable the users to add the Audience parameter within the OAuth2 requests, as an optional parameter. (RIA-19596)
  • This is described further in Enabling OAuth 2.0 Authentication.
  • Added vertical scroll bars to move more easily through the APIs for which you want to add a New Security Test for a Single Request. (RIA-19655)
  • Now, it is possible to Add/Remove multiple Agents in a Load Test, at the same time. (RIA-19569)
  • This is described further in Creating Distributed Load Tests.
  • Improved the Error Message provided when trying to connect to a Virt Server by providing an URL in an invalid format. (RIA-19126)
  • The ‘Abort test if an error occurs’ is now set to Off by default, based on customers and community feedback. (RIA-19419)

New in ReadyAPI 3.40.2 (Jul 27, 2022)

  • ReadyAPI 3.40.2 is a minor bugfix release that includes a few changes as compared to the previous version of the product

New in ReadyAPI 3.40.1 (Jun 13, 2022)

  • Fixed a bug which was introduced in 3.40.0 where the max memory available for Readyapi was not computed correctly and after 10 seconds of performance tests in 3.40.0 users were getting this false error message: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Performance tests now run without any error. (RIA-19505)
  • Fixed a bug in API Discovery where filtering the results by content type did not work properly on requests with a content-type header with a different case. (RIA-19481)
  • Fixed a bug where the HTTP Monitor did not start and the error log presented a NullPointer exception. Users can now start the HTTP Monitor and visualize a list of captured requests. (RIA-19493)
  • Fixed a bug where the Authorization Scope tree under Auth Manager was not displayed in 3.40.0. This has been restored. (RIA-19510)
  • Fixed issue with Virtualisation where mocked response did not work reliably when bulk request is made. (CC-27719)

New in ReadyAPI 3.40.0 (Jun 3, 2022)

  • ReadyAPI Core:
  • Upgraded spring Framework to 5.3.18. (RIA-19435)
  • Upgraded to Java 17. (RIA-19352)
  • Upgrade JMS 1.1 Jar to JMS 2.0. (RIA-19058)
  • Released ReadyAPI version to run on AppleM1 chip.
  • Note:
  • RIA-5xxx1 represents the Jira ticket number. It will help you track back the bugs resolved in version 3.40.
  • SmartBear License Management:
  • We have added support for offline licensing to support users operating in private networks where internet access is restricted. For more information, please go to ReadyAPI Licensing | ReadyAPI Documentation.
  • ReadyAPI Performance Improvements:
  • We have been implementing improvements to ReadyAPI Performance testing including increasing the number of virtual users which can be simulated from one computer. Up to now, we have recommended up to 1000 virtual users being simulated from one machine and using Load Agents to scale beyond 1000 VUs. ReadyAPI is now able to manage higher numbers of users from one machine and we are now recommending one machine can manage approx. 6,000-10,000 VUs.
  • We have also improved the stability and reliability of Load Agents for larger scale distributed testing.
  • We will continue to improve performance testing in upcoming releases and expect to publish more detailed recommendations with each release.
  • ReadyAPI Test - gRPC:
  • When importing proto3 Files, users can use all linked gRPC schemas while testing the gRPC service in that proto3 file and test gRPC services with external links. (RIA-18921, RIA-18885)
  • Added support for importing .proto files that contain Google wrappers. When importing .proto import using Google wrappers, the import line in the test_with_GoogleWrappers.proto is looking for the wrappers.proto. When the wrappers.proto is added to the correct folder structure, the import works properly. (RIA 19418)
  • ReadyAPI Test - JMS:
  • You can specify the JMSDeliveryMode for JMS messages in virtual services so the message won’t be missed. (RIA-19258)
  • Integrations:
  • We published a new version of 'ReadyAPI Test for Azure DevOps' extension. (RIA-19195)
  • ReadyAPI Test - File Upload:
  • When testing services that require files to be sent, users can easily upload a file and send it so that they can test their services accordingly. (RIA-17380)
  • When Creating New Environments:
  • When creating a new environment user has a checkbox to add Endpoints from "No Environment". If more than one endpoint with the same interface name exists, the user chooses the one on the list. We copy endpoints for REST, KAFKA, SOAP, etc. (RIA-17358)
  • More:
  • We have fixed a few bugs reported by our customers.

New in ReadyAPI 3.20.2 (Feb 22, 2022)

  • ReadyAPI now uses a newer version of the Protection! License Server – version 5.5.3.
  • We’ve improved the API Connection test step editor:
  • When you add the Path (Query) and Matrix parameters to a REST request, the editor shows them next to the resource:
  • Query parameter in the API Connection test step
  • When you are editing a REST request, the new API Request button opens the related API request for editing.
  • Now, when you use the dark theme on Windows computers, ReadyAPI uses the system color for the title bar.
  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers.

New in ReadyAPI 3.20.1 (Jan 26, 2022)

  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers.

New in ReadyAPI 3.20.0 (Dec 22, 2021)

  • Support for gRPC services:
  • You add a new gRPC definition to your project by using a .proto file. ReadyAPI uses the definition to serialize and deserialize gRPC messages
  • Use the API Connection test step to send and receive messages of gRPC APIs
  • ReadyAPI also supports sending gRPC messages over the SSL/TLS protocol with and without a Google OAuth 2.0 authentication token.
  • You can add a Smart Assertion to the API Connection test step to check incoming messages
  • Dark theme:
  • ReadyAPI now fully supports the dark UI theme
  • To use this theme, enable it in the Preferences > UI window
  • Masking encrypted properties:
  • Now, ReadyAPI masks values of the encrypted properties in all the logs and reports:
  • ReadyAPI Log panels.
  • ReadyAPI reports:
  • Printable
  • JUnit-Style
  • Data export
  • Allure
  • Logs of the command-line test runners.
  • More:
  • When you configure a SmartBear ID-based license, you can open the Proxy Preferences dialog from the License Manager.
  • The Docker image for running functional tests now supports SmartBear ID-based licenses.
  • We’ve introduced the Docker image for running security tests. To learn more, see Security Tests in Docker.
  • We’ve updated the Apache Log4j library to v. 2.16 to mitigate the CVE-2021-45046 issue.
  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers.

New in ReadyAPI 3.10.2 (Dec 14, 2021)

  • ReadyAPI 3.10.2 is a minor release that includes a fix of the Apache Log4j CVE-2021-44228 vulnerability issue.

New in ReadyAPI 3.10.1 (Oct 27, 2021)

  • Overall improvements:
  • There is a new Java virtual machine option - oauth2.access.token.retrieval.timeout. It configures the timeout of getting a new access token during the OAuth 2.0 automation process. It can be useful if the process of getting a new access token takes more than 5 seconds.
  • We’ve improved the dark UI theme.
  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers.
  • Discontinued support:
  • ReadyAPI no longer supports the following obsolete and rarely used tools:
  • Axis 1.xAxis 2.x
  • Apache CXF 2.x
  • JAX-RPC
  • JAX-RPC Wscompile
  • JBossWS WsConsume
  • JBossWS WsTools
  • JWSDP/JAX-WS Wsimport
  • GSoap
  • Oracle wsa
  • TcpMon
  • WADL2JAVA
  • Web Services Description Language Tool (Wsdl.exe)
  • XFire 1.x
  • XmlBeans

New in ReadyAPI 3.10.0 (Sep 22, 2021)

  • In the new version:
  • Dark theme
  • Now, ReadyAPI supports the dark UI theme:
  • When you enable it, all windows, dialogs, editors, and other UI elements will use dark colors that you may find more comfortable to work with.
  • Other improvements:
  • The Smart Assertion now can check if a value has a specific data type (string, number, boolean, or null).
  • We have fixed a few bugs reported by our customers.

New in ReadyAPI 3.9.2 (Aug 25, 2021)

  • Extended support for Kafka schemas:
  • Now, you can use Protobuf schemas to serialize and deserialize Kafka messages.
  • Also, you can specify schemas by using a file. It works for both Avro and Protobuf schemas.
  • Other improvements:
  • Now, ReadyAPI checks an endpoint format and posts an error message to the log in case the endpoint is invalid. It helps you find the cause of the test failing when you, for example, misprint the endpoint.
  • The JSON Schema Compliance and Swagger Compliance assertions now validate child objects even if the parent ones are not valid.
  • ReadyAPI now uses Java version 16. The new version improves thew security and stability of the product.
  • We’ve updated Microsoft JDBC drivers for SQL Server that are bundled with ReadyAPI. The new driver version includes new features and bug fixes.

New in ReadyAPI 3.9.1 (Jul 31, 2021)

  • ReadyAPI Test:
  • The Smart Assertion button in the REST Request, GraphQL Query, GraphQL Mutation, or SOAP Request test step now creates the Smart Assertion. Previously, it created the Message Content Assertion.
  • Check boxes that enable locally stored properties have been moved to the right:
  • Locally stored properties in ReadyAPI 3.9.1
  • ReadyAPI Performance:
  • Now, when you select an application for the AppDynamics monitor, you can filter the list of applications.
  • The Transaction Log for distributed load tests now shows raw data of the request and response messages.
  • ReadyAPI Virtualization:
  • When you inspect the JMS Bytes messages in the Transaction Log of JMS virtual services, you can use the Hex viewer to see the message in hexadecimal, decimal, octal, binary, and text representations:
  • Hex viewer in the JMS virtual services
  • Other improvements:
  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers.

New in ReadyAPI 3.9.0 (Jun 30, 2021)

  • REST support in the API Connection test step BETA:
  • Now you can test REST APIs by using the API Connection test step. It means you can send REST requests, get responses and validate them as you do with the REST Request test step, but with the cleaner and more convenient user interface
  • REST testing with the API Connection test step is close to that process with the REST Request test step:
  • You link an API request to a test step, so it synchronizes the resource path, REST method, and parameters.
  • You can validate the received response by using assertions.
  • The API Connection test step supports environments.
  • You can use property expansions in parameters and the request body.
  • However, there are some differences as compared to REST Request. For example, to set authentication, you select the needed Auth profile in the Authorization profile combo box instead of the Auth panel.
  • Smart Assertion:
  • ReadyAPI 3.9.0 introduces the Smart Assertion. It verifies one or more values of the body or metadata of API responses.
  • The assertion is similar to the Message Content Assertion but has a number of improvements:
  • You can use it to verify response metadata: headers, the HTTP status code, and Kafka key and partition values.
  • You can use additional conditions when comparing values.
  • You can specify whether a value to be checked should be case-sensitive or not.
  • You can configure the assertion quicker, because the configuration dialog has a cleaner interface.
  • Deprecated assertions
  • The Smart Assertion supersedes some existing assertions. Since ReadyAPI 3.9.0 they are deprecated in favor of the new assertion. These assertions will continue working, but we recommend that you replace them with the Smart Assertion:
  • Message Content Assertion
  • Valid HTTP Status Codes
  • Invalid HTTP Status Codes
  • HTTP Header Equals
  • HTTP Header Exists
  • Other improvements
  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers:
  • We optimized the smartbear/ready-api-soapui-testrunner Docker image. (RIA-16642)
  • TestRunner returned errors when it generated custom reports. (RIA-16272)
  • ReadyAPI could not handle an empty JDBC connection name. (RIA-15710)

New in ReadyAPI 3.8.1 (May 26, 2021)

  • Now, when you create a new REST API, ReadyAPI uses the OpenAPI format to store its definition in the project file. You can see it in the Specification panel:
  • REST API specification in ReadyAPI 3.8.1
  • The Data field of the API Connection test step looked like it was not editable. In version 3.8.1, we fixed it.
  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers.

New in ReadyAPI 3.8.0 (Apr 28, 2021)

  • Support for AsyncAPI definitions:
  • Now, you can add asynchronous APIs to your project by importing AsyncAPI definitions.
  • Extended Kafka support:
  • The Event-Driven test step has been renamed to API Connection.
  • Now, the API Connection test step in a data-driven loop reuses an existing connection rather than creates a new one for each iteration.
  • The Properties panel now contains the connection settings of the API Connection test

New in ReadyAPI 3.7.0 (Apr 2, 2021)

  • Kafka support:
  • ReadyAPI now supports testing of Kafka-based APIs:
  • You add a new Kafka API to your project and then add topics and operations to that API using special dialog boxes and editors.
  • You can add assertions to the Event-Driven test step working in Subscribe mode to check incoming messages.
  • ReadyAPI can also serialize and deserialize Kafka messages using connection to Schema Registries.
  • Use the new Event-Driven test step to send and receive messages of asynchronous Kafka APIs. The test step operates in one of the following modes:
  • In Subscribe mode, it connects to a Kafka topic and receives messages from it as long as the connection is open.
  • In Publish mode, it connects to a topic, publishes a message there, and disconnects.
  • Assertion groups:
  • Assertions in a functional test can now be grouped into an assertion group:
  • An assertion group behaves like a regular assertion: it can either pass or fail. Its status depends on the statuses of assertions included in it and the conditions applied (AND / OR).
  • More:
  • We’ve removed some rarely used tabs:
  • The Resources tab from the REST service editor.
  • The Objects tab from the GraphQL service editor.
  • The Operations tab from the SOAP and XML-RPC service editors.
  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers.

New in ReadyAPI 3.6.0 (Feb 17, 2021)

  • Endpoints & Environments:
  • The Endpoints & Environments dialog extends the functionality of the previous Environments dialog:
  • We redesigned the dialog for adding and editing endpoints. Now, you have the same experience when you add or edit endpoints in the Endpoints & Environments dialog and on the Endpoints page of the APIs editor. No matter which type of API you use: REST, GraphQL, or SOAP.
  • Now, you can remove endpoints from the Endpoints & Environments dialog.
  • You can copy and paste project properties from one environment to another.
  • Now, you can copy the entire environment to another project. The needed project properties and authorization profiles will be copied as well. To learn more, see Copy environments to another project.
  • Previously, you had to decide whether you create an environment from scratch or copy endpoints from the project. Now, you always create an empty environment.
  • If a request does not have an endpoint specified for the used environment, ReadyAPI will not use the default endpoint - you must specify the needed endpoint for each environment.
  • Default Environment has been renamed to No Environment. Now, this item is always at the top of the environment list.
  • In its turn, the Endpoints page of the API editor was completely redesigned:
  • Now, it lists endpoints across all the environments.
  • Instead of the obsolete Username, Password, and Domain fields, each endpoint uses an authorization profile.
  • You manage endpoints the same way you do it in the Endpoints and Environments dialog.
  • Assertions tab:
  • We improved the Assertions tab for the REST Request, GraphQL Query Request, GraphQL Mutation Request, SOAP Request, HTTP Request, and XML-RPC Request test steps. Now, it has a better and cleaner interface:
  • The new Assertions tab is now always visible in the request test steps.
  • The entire assertion's row is now highlighted to show if it passed or failed:
  • The assertions tab without assertions looks more informative.
  • API management:
  • To make the process of creating a new project more straightforward, we have removed the Create Project dialog. Now, after you create an empty project, you use the dialogs mentioned above to populate the project with the needed APIs.
  • The Overview tab for the REST, GraphQL, and SOAP APIs has been removed.
  • We also improved the way you manage APIs in your project:
  • The dialog for adding REST resources has become cleaner and easier to use.
  • We have split the functionality of the Add API dialog into three separate dialogs.
  • Use the Create API Definition dialog to create an API from scratch.
  • Use the Import API Definition dialog to import an API from a definition file: either local or remote file (OpenAPISwagger, WADL, WSDL) or a definition from SwaggerHub.
  • Discover API - use it to create an API by exploring an existing API. See Discovering APIs
  • More:
  • Locally stored properties are now available in security and load tests and in virtual APIs.
  • The Postman plugin now supports variables.
  • We have fixed a few bugs reported by our customers.
  • We’ve updated a few third-party libraries to make the product even more reliable and secure. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • GraphQL improvements:
  • GraphQL APIs in the Navigator menu now have a flyout menu:
  • You can generate a test suite from the GraphQL API.
  • When you add a GraphQL request to a test case, you have the same dialog as in REST and SOAP APIs.
  • We updated the Preferences dialog:
  • Tabs of the Preferences dialog are grouped into categories.
  • The interface of the Preferences dialog has become cleaner.
  • You manage GitHub, GitLab, and Bitbucket accounts in the Properties dialog.

New in ReadyAPI 3.5.2 (Jan 27, 2021)

  • We’ve improved stability of the product on macOS computers.
  • We’ve also fixed a few bugs reported by our customers:
  • In some cases, on macOS machines, ReadyAPI didn’t show menus. (RIA‑15257)
  • The ReadyAPI installer could not be run on macOS computers. (RIA‑12470)
  • An exception occurred when users ran tests with the test runner on the Linux headless machines. (RIA‑15414)

New in ReadyAPI 3.5.1 (Dec 16, 2020)

  • The possibility of storing values of project, test suite, and test case properties locally, that is, in the workspace file rather than in the project file.
  • If you don't see the image, upgrade ReadyAPI to the latest version.
  • The enhanced SQL Injection scan in security tests.
  • The possibility of selecting metrics for the AppDynamics monitors visually:
  • If you don't see the image, upgrade ReadyAPI to the latest version.
  • The updated UX and UI:
  • A better look on high-resolution screens.
  • The updated Environments Editor.
  • The delimiters between projects in the Navigator panel.
  • The “Disconnect Account” command in the Git dialog box.

New in ReadyAPI 3.5 (Nov 20, 2020)

  • The new version includes a number of improvements to make API testing easier and more powerful. Below is the list of changes relative to the previous version of the product – ReadyAPI 3.4.5. For information on the changes made to other versions, see Version History.
  • Performance testing:
  • The AppDynamics monitors have a new option – Update rate – that specifies how frequently a monitor pulls data from the AppDynamics server.
  • Load-testing-related options of data sources are now available right in ReadyAPI Performance. Besides that, when you do not share the data source between virtual users, ReadyAPI visually shows you that a virtual user will go through the data source loop. To learn more, see Data Source in Load Testing.
  • The PerformanceTestRunner utility now supports encrypted projects. To specify a project password, use the new -x argument of the command line.
  • Overall improvements:
  • ReadyAPI now uses OpenJDK 15.
  • Newer versions of some libraries used in version 3.5. If your scripts refer to classes from these libraries, you might need to update the scripts.
  • We have fixed a few bugs reported by our customers.
  • UI improvements:
  • You can import or create a new project in the workspace’s flyout menu.
  • Also, when your workspace is empty and has no projects, you can now create or import projects right from the Navigator panel.
  • We’ve also made a few minor visual improvements.
  • Discontinued support:
  • ReadyAPI no longer supports the following operating systems:
  • Windows 7
  • Mac OS X 10.7, OS X 10.8 - 10.11, macOS 10.12
  • macOS Server
  • Suse Enterprise Server 10 SP2
  • Ubuntu 10.04 - 18.04

New in ReadyAPI 3.4.5 (Oct 22, 2020)

  • Version 3.4.5. offers new features to streamline API test development and to make teamwork easier.
  • ReadyAPI 3.4.5 introduces support for Git repositories of GitLab and Bitbucket. This means you can:
  • Link your Bitbucket and GitLab accounts to ReadyAPI.
  • Import test projects from your repositories to ReadyAPI directly from within ReadyAPI.
  • Pull the changes you made to your ReadyAPI tests to repositories easily.
  • ReadyAPI supports all Bitbucket and GitLab editions:
  • Bitbucket Cloud, Data Center, and Server
  • GitLab SaaS and GitLab Self-Managed
  • You work with Bitbucket and GitLab repositories through the same editors and dialog boxes that you use to work with GitHub repositories. For complete information, see Git Integration.
  • ReadyAPI Performance:
  • ReadyAPI Performance Agents can now run load tests that use features provided by ReadyAPI plugins (like custom test steps). To learn how to use the plugins, see Creating Distributed Load Tests.
  • Overall improvements:
  • Support for the state parameter of the OAuth authentication.
  • We have fixed a few bugs reported by our customers.