Bug Fixes in ReadyAPI 3.67.0
In ReadyAPI 3.67.0, the following issues have been resolved:
Note
RIA-2xxx1 represents the Jira ticket number. It helps you track the bugs resolved in version 3.67.0.
Resolved an issue that prevented uploading ReadyAPI Performance Cloud images. This fix restores successful image deployment and use in cloud environments (RIA-26932).
Resolved an issue where large virtual services returned HTTP 500 responses under high traffic. This occurred when response writing exceeded gateway timeouts (more than 8 seconds), resulting in an error in the VirtServer logs. Code executed in a
parallelStreamlocked ForkJoinPool (FJP) threads, creating bottlenecks and head-of-line blocking under high concurrency. Refactored request processing to improve FJP thread usage (RIA-26115).Resolved an issue where running any project could trigger file compression errors in Azure integrations due to an outdated dependency. Updated the dependency to the latest version to ensure stable compression and compatibility. This fix will be included in Azure plugin version 1.9 (RIA-23793).
Note
After test execution, you may see a warning such as
“Failed to compress file”referencingMicrosoft.WindowsAzure.Storage.DataMovement, Version=0.7.0.0. This may be followed by a message like“Failed to upload run logs to LogStore, Trying to upload to FileService.”This warning can be safely ignored. It occurs when the Azure DevOps build agent is missing an optional compression library. In this case, Azure automatically falls back to an alternative upload method.
Test execution is not affected. All test results are still published correctly to Azure DevOps.
This is an Azure DevOps agent environment issue, not a ReadyAPI plugin issue. To verify correct behavior, check that your test results are available through the Published Test Run link in the logs.
Resolved an issue where importing multiple request-response (RR) pairs for the same endpoint did not retain query string and dynamic path parameters correctly. Data from the last imported request overwrote previously imported requests, causing inconsistencies in conditional matching. This prevented the virtual service from correctly differentiating requests and led to incorrect request matching and responses. ReadyAPI now preserves all imported request data, ensuring accurate request matching behavior (RIA-27253).
Resolved an issue where importing request-response (RR) pairs without additional parameters added empty parameters to request signatures and requests. This caused mismatches between imported data and actual request definitions. ReadyAPI no longer adds empty parameters during import, ensuring requests and signatures remain exactly as defined in the RR files (RIA-27297 and RIA-27477).