Bug Fixes in ReadyAPI 3.4.5
In ReadyAPI 3.4.5, the following issues reported by our customers have been fixed:
Overall
In some cases, ReadyAPI did not load definitions from your local SwaggerHub On-Premise. (RIA‑14660)
You could not import the OpenAPI definition from the server that requires Windows Authentication. (RIA‑13948)
Users could set inacceptable values for HTTP > Max Connections Per Host and HTTP > Max Total Connections. ReadyAPI could not start because of the incorrect values. (RIA‑10631)
ReadyAPI Test
In some cases, the SQL Injection and XPath Injection scans overwrote the endpoint of an environment. (RIA‑14557)
The argument list of the command-line test runner shown by using the
-h
argument was not correct. (RIA‑13097)
ReadyAPI Performance
An error occurred when you opened a load test without a ReadyAPI Performance Pro license. (RIA‑13240)
The amount of total test steps in the load test report was incorrect. (RIA‑9662)
ReadyAPI Virtualization
SOAP virtual services could not handle requests with some attachments. (RIA‑13716)
ReadyAPI did not save values set to the Min Threads and Max Threads behavior settings of a virtual service. (RIA‑14391)