Bug Fixes in ReadyAPI 3.5.1

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

In ReadyAPI 3.5.1, the following issues reported by our customers have been fixed:


  • In some cases, issues with JDBC Request test steps caused memory issues with ReadyAPI. (RIA‑14176)

  • Issues in the JDBC Request test step caused not closing TIME_WAIT network states. (RIA‑13718)

  • We have fixed an issue that caused increasing execution time of the JDBC test step in the recent release. (RIA‑14998)

  • Misleading labels of the Jira plugin preferences have been changed. (RIA‑9396)

  • The Jira plugin could not create an issue if the Assignee field is required. (RIA‑14059)

  • The Jira plugin did not support custom fields with predefined values. (RIA‑10405)

  • When a user removed an environment, ReadyAPI did not remove it from the project file. (RIA‑13100)

  • When a user canceled the creation of a global property, ReadyAPI created it in its preferences anyway. (RIA‑13104)

  • In some cases, ReadyAPI did not detect conflicts during a pull from Git repositories. (RIA‑14441)

ReadyAPI Test

  • Special characters in the template parameters of the REST Request test step worked incorrectly. (RIA‑7053)

  • Sometimes, the Content-Type header was ignored for the REST requests with the GET method. (RIA‑12992)

  • When a user created a REST request with more than one template parameter in a resource path, ReadyAPI ignored these parameters. (RIA‑11022)

ReadyAPI Performance

  • Load tests sometimes continued to run even after the specified time limit was over. (RIA‑7053)

ReadyAPI Virtualization

  • Virtual services created from OpenAPI/Swagger definitions with the parameterized path worked incorrectly. (RIA‑14757)

See Also

Version History
What's New in ReadyAPI

Highlight search results