In ReadyAPI 3.42.0, we fixed the following issues reported by our customers:
Overall
Note: |
-
Fixed a bug that caused the XPath assertions that contain an "exists" construction (that allows checking if the response contains a certain element) to not be displayed in the Transitions log. Now, those XPath assertions are included in the Transaction Log. (RIA-19219)
-
Fixed an issue related to running Testrunner with the -accessKey parameter on the same machine in ReadyAPI after the license has been released at the end of the previous test run. The encounter error was “No license found Error” in the command line. Now it is fixed. (RIA-19556)
-
Fixed an issue that prevented the users from using the agent availability script located within the C:\Program Files\SmartBear\ReadyAPI-3.40.1\bin. Now that script works as expected. (RIA-19745)
-
Fixed an issue where an Int value was passed as a String value in a REST request. Now, the Int values are passed as Int values in the REST requests. (RIA-18946)
-
Fixed an issue that caused some Load Agents to fail to start/run in a Load Test. (RIA-20011)
- Note: When you run a Load Test configured to run on Load Agents, your project is automatically saved and pushed to the configured agents.
- Note: Whenever you save a project, the corresponding project files gets updated. If and when you connect to Git, Git will detect that change and ask you to commit and push it.
-
Fixed an issue that caused a Test Case to fail to run when using the ReadyAPI docker image, where the error was java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1. (RIA-19564)
-
Fixed an issue where the Install License dialog was not properly scaled after startup on Linux Ubuntu 22.04.1 LTS x86_64 with the 1920x1080 (scaling 100%), and 2560x1440 (scaling 100%) resolutions. (RIA-19987)
-
Fixed an issue that prevented users to use property expansions to generate the Access Token for the OAuth profile in the corresponding test steps. (RIA-19289)
-
Fixed an issue where some JDBC parameters were changed to question marks when using a string constant for a Stored Procedure’s parameters/local variables (parameters started with the “@“ sign). (RIA-19395))
-
Fixed an Assertion Cloning bug where the assertions were cloned twice instead of once when closing the Clone Assertion pop-up window. (RIA-19765)
-
Fixed an issue where the ‘json.data’ construct applied on a ‘responseContent’ content of a Script Assertion could not be used due to a Null Pointer Exception. Now it works as expected. (CC-28102)