Bug Fixes in ReadyAPI 3.20.1

Applies to ReadyAPI 3.41.1, last modified on October 03, 2022

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

Overall

  • We’ve updated the Apache Log4j library to the 2.17.1 version. (RIA-18876)

  • The HTTP Archive REST Discovery plugin did not work. (RIA-17951)

ReadyAPI Test

  • We’ve improved messages ReadyAPI shows when a wrong JSONPath causes an exception. (RIA-7255)

  • When you run a test case, ReadyAPI used a progress bar at the bottom of the window to show that a request was being sent. In some cases, it did not work. The correct behavior is that ReadyAPI uses it only when you send a single request, not a test case, test suite, or project. Now, it works as expected. (RIA-18911)

  • ReadyAPI TestRunner did not use the specified settings file when you generated Allure results. (RIA-18910)

  • ReadyAPI did not encode unsafe characters (for example, spaces) in REST resource paths. (RIA-18898)

  • The Smart Assertion was case-sensitive when checking header names, so it could not find headers written using different cases. (RIA-18797)

  • When ReadyAPI used the tabbed mode, the JDBC test step editor did not refresh the response panel when you run the entire test case. (RIA-9548)

  • In some cases, NullPointerException occurred when you performed the JSON Boundary security scan. (RIA-9376)

ReadyAPI Performance

  • The Used Memory value shown for each agent on the Distributed page was calculated in a wrong way. Because of that, on Linux machines, this value was higher than the actual memory used. (RIA-17980)

  • The newly added metric for the AppDynamic monitor was not available on the Statistics page until you run a test. (RIA-16823)

See Also

Version History
What's New in ReadyAPI 3.41.1

Highlight search results