 |
Important Notice for ReadyAPI Customers |
ReadyAPI has moved to SmartBear License Management. From October 2023, ReadyAPI will no longer provide file-based licensing. You need to migrate as soon as possible so your service remains uninterrupted. Please view this 45-minute webinar to learn:
-
What is SLM?
-
Why are we doing it?
-
What options are available?
-
What is our SLM readiness checklist?
-
What are the next steps?
-
Demo
-
Live Q&A
Contact your SmartBear Account Manager to plan your migration or contact support if you require assistance.
ReadyAPI 3.46.0 includes a few changes compared to the previous version of the product – ReadyAPI 3.45.0. For information on the changes made to other versions, see Version History.
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.
Click the image to enlarge it.
Click the image to enlarge it.
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 or 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.
| Note: | 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=trueflag 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.
More
-
ReadyAPI 3.46.0 includes newer versions of some libraries that version 3.45.0 used. 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.
