Bug Fixes in ReadyAPI 2.4

Previous ReadyAPI versions used an old version of the RAML parser and could not create a new project from a RAML definition in some cases. (RIA-6860)

ReadyAPI could not import a Postman collection if URLs in the collection contained variables. (RIA-7079)

ReadyAPI was unable to open a project if the Normalize line-breaks option was enabled when you saved that project, and if the project contained non-ASCII characters. (RIA-7092)

ReadyAPI did not save projects with environments if a user had added an encrypted custom property and set the Encryption Mode project property to Selected Properties. (RIA-6938)

It was impossible to refactor a definition if that definition was located on a server requiring an HTTPS connection. (RIA-7286)

When a user created a project from a Swagger definition, ReadyAPI generated an incorrect request body for the objects that used the additionalProperties keyword. (RIA-7025)

For JSON responses, the Outline editor did not show a descriptive error message if multiple JSON nodes within the response were named identically. (RIA-7127)

The JSONPath Existence Match assertion failed if it referred to an empty or null JSON node. (RIA-6930)

The JSONPath Match assertion returned a wrong value if it referred to an empty JSON node. (RIA-6994)

The JSONPath Match assertion returned a wrong value if the JSONPath expression used by the assertion referred to an array. (RIA-7115)

JSONPath returned no value if it referred to an array containing a single value. (RIA-7117)

The HTTP Header Equals assertion failed if the validated response had no body content. (RIA-7018)

It was impossible to send authorization headers if you used basic authentication and did not specify a password, or if you specified a password containing a space character. (RIA-7382)

Sometimes, an error occurred if a user tried to connect ReadyAPI to the c-treeACE database using the JDBC driver. (RIA-7086)

The dashboard could not represent test cases the names of which were longer than 150 characters. Now, it is limited to 300 characters. (RIA-6820)

If you had added an XML file to a folder of a composite project, the content of the file was included to the project’s settings.xml file during the next project load. (RIA-643)

When you added a new keystore, ReadyAPI reset the specified aliases for the WS-Security Signature and Encryption entries. (RIA-1840)

ReadyAPI showed the Save Project dialog each minute the Autosave interval option was set to 1. (RIA-7243)

If you imported a ReadyAPI project that had been saved in a previous version of ReadyAPI, the Property Wait test step was imported incorrectly. (RIA-6979)

When a user added a new element to a request body by using the Form tab, the changes were not applied to the request. (RIA-3737)

The Run Manual TestStep dialog was inconvenient for editing large text. (RIA-5036)

It was impossible to execute the Publish using MQTT test step within a Groovy script. (RIA-6939)

In the JDBC Request test step editor, it was impossible to clone the Contains assertion associated with the step. (RIA-7020)

Filters in JSONPaths were not working correctly. (RIA-4467, RIA-5225)

In some cases, it was impossible to call the Select XPath dialog from the configuration dialog for the XPath Match assertion. (RIA-7410, RIA-7531)

When you run a lot of test cases or test suites in parallel, you might face a number of exceptions. (RIA-5533)

When a response contained the Substitute character (\u001a), the IllegalCharacterDataException error occurred. (RIA-5590)

When you were using the HermesJMS connection, a request to an endpoint did not wait for a response from temporary queues. (RIA-6456)

ReadyAPI used too much CPU when the Add Assertion dialog was opened. (RIA-3718)

Sometimes, the Swagger Compliance assertion incorrectly failed with the “No resource matching in OpenAPI definition” message. (RIA-6559)

On a test case’s Compare tab, you could not archive a test case run nor set the run as a baseline. (RIA-5904)

It was impossible to filter the items on the History page of the project editor using the From and To edit boxes. (RIA-7801)

JUnit-style reports did not contain error data from the test steps that had been run by using the Run TestCase test step, even if the Complete Error Logs option was enabled. (RIA-6913)

If you had commanded test cases within a suite to run in parallel and then generated the JUnit-style reports, the Test Suite Time Taken field in these reports was containing a summary run time for all test cases (instead of actual time the test suite had been running). (RIA-7073)

The setAttachmentAt method is now available in the HttpTestRequest object again, and you can use it in your scripts. (RIA-7074)

It was impossible to create a JIRA issue if the Reporter field was set as required in JIRA settings. (RIA-3488)

The duration of load tests in JUnit-style reports was incorrect. (RIA-6828)

The MockRunListener.onMockResult event handler was not working. (RIA-3611)

The mockResponse.setResponseContent method was working incorrectly. (RIA-6517)