Loaris Trojan Remover

What's new in this version:

ReadyAPI 3.46.0
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


ReadyAPI 3.45.0
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


ReadyAPI 3.44.1
- Fixes an issue affecting some users when activating trial licenses


ReadyAPI 3.44.0
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


ReadyAPI 3.43.1
- 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.


ReadyAPI 3.43.0
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


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


ReadyAPI 3.42.1
Fixed:
- an issue that prevented users from using the Git Pull feature in ReadyAPI. The issue was introduced in the 3.42.0 version
- three related security vulnerabilities reported in JRE (CVE-2022-21618, CVE-2022-21624, CVE-2022-21626) by upgrading to 17.0.5
- 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.


ReadyAPI 3.42.0
- 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


ReadyAPI 3.41.1
- 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.


ReadyAPI 3.41.0
- ReadyAPI was updated to support Java 17.0.4 (from Java 17.0.2)
- 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.
- You can now Search in the Navigator through Test Cases and Test Steps as well, not only through Test Suites
- Added the possibility to Save a Test Suite of a Composite Project. Saving a Test Suite will save all its Test Cases
- 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
- 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
- Now, it is possible to Add/Remove multiple Agents in a Load Test, at the same time
- 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
- The ‘Abort test if an error occurs’ is now set to Off by default, based on customers and community feedback


ReadyAPI 3.40.2
- Minor bugfix release that includes a few changes as compared to the previous version of the product