Bug Fixes in ReadyAPI 3.46.0

Applies to ReadyAPI 3.53, last modified on May 15, 2024

In ReadyAPI 3.46.0, we fixed the following issues reported by our customers:

Overall

Note:
RIA-5xxx1 represents the Jira ticket number. It will help you track back bugs resolved in version 3.46.0.
  • Fixed:
    • An issue causing a Read Timeout exception (java.net.SocketTimeoutException: Read timed out) and preventing the Socket Timeout from functioning correctly when executing an HTTP request. (RIA-20601, RIA-20362)

    • An issue that caused ReadyAPI to create a test in a test suite with a POST method despite the user selecting a DELETE method initially. (RIA-20560)

    • An issue with API export to an unspecified or invalid location path. Now, you need to specify a valid path to export an API. (RIA-20614)

    • An issue preventing Swagger API import into ReadyAPI when path attributes were missing. (RIA-20740)

    • An issue leading to inaccurate performance data reports in certain cases, attributed to primary key violations. (RIA-20354)

    • An issue causing exported Swagger API definitions to not include schema fields for request body parameters. Now, the exported API can be imported into SwaggerHub (RIA-20613)

    • An issue causing duplicate parameters in exported Swagger API definitions. (RIA-20760)

    • An issue preventing the closing of a pop-up error message displayed when resizing the column of an empty Test Case Property name. To close the pop-up, users had to press the OK button three times instead of once. (RIA-19898)

    • An issue causing the UI to move slowly when moving and re-ordering test suites of a test project. (RIA-20116)

    • An issue that resulted in URL malformation when changing a parameter's type from TEMPLATE to QUERY. It was caused by an unnecessary forward slash in the address. (RIA-20814)

    • A bug that prevented some test cases from being imported into ReadyAPI. (RIA-20543)

    • An issue that prevented some users from pulling changes from GitHub. (RIA-20639)

    • A problem that caused TestSuites to be cloned within the same target project, causing ReadyAPI to restart and erasing data within the original TestSuite. (RIA-20603)

    • A transaction log issue. Earlier, when a SOAP request was accounted for, nothing was recorded in the transaction log, and the request-response mapping was not created. (RIA-20629)

  • When you call a Test case in Thread-Safe mode with the "Store Values Locally (exclude from saved projects)" option selected, it will now return Thread-Safe properties. (RIA-20746)

See Also

Version History
What's New in ReadyAPI

Highlight search results