In ReadyAPI 3.3.1, the following issues reported by our customers have been fixed:
Overall
-
An error occurred when importing OpenAPI 3.0.1 definitions that didn't have the
contentType
field for theEncoding
object. (RIA-12786) -
Using a wrong activation key during offline headless activation resulted in a successful activation message. (RIA-3948)
-
Misleading warnings concerning custom libraries and the report directory were posted to the log on startup. (RIA-13207)
-
Several third-party libraries were updated to fix vulnerability issues. (RIA-13175, RIA-13176, RIA-13177, RIA-13178, RIA-13180)
SoapUI
-
The Allow Wildcards option for JSONPath Match Assertion sometimes worked incorrectly. (RIA-13507)
-
The
ClassCastException
error occurred when creating the JSONPath Match assertion. (RIA-9892) -
The AWS signature was not generated correctly when the query parameter value contained the colon character (
:
). (RIA-10873) -
TestRunner logged an error when it opened the generated coverage report after the test run. (RIA-10434)
LoadUI
-
LoadUI could take a long time to open a large project. (RIA-13456)
-
LoadUI could take a long time to turn an agent on. (RIA-13457)
-
LoadUITestRunner did not overwrite project properties. (RIA-13240)
-
The number of failed test cases in the load test report was higher than it was in fact. (RIA-13868)
Integrations
-
The error comment is now deleted from Zephyr when the test case passes. (RIA-10898)