Bug Fixes in Ready! API 1.9

When a user tried using online license activation without having an Internet connection, a non-informative message was shown. (RIA-4)

When obtaining the trial license key, in certain cases, you might get the "Internal Server Error". (RIA-34)

The NullPointerException occurred when importing some Swagger definitions. (RIA-64)

After importing a Swagger definition, parameters of the TEMPLATE type were displayed in the Method Parameters table of the request editor. (SOAP-5859)

In certain cases, the "Update Definition" command of the Navigator's context menu could clean request parameters' values. (RIA-90)

It is no longer possible to accidently edit response contents. (SOAP-4971)

Ready! API did not refactor RAML definitions. (SOAP-5233)

The Browse button in the Refactor Definition dialog did not work if the Definition URL edit box pointed to a non-existing file name. (SOAP-5281)

Ready! API documentation now describes constants that plugin authors can use for adding custom commands to Ready! API's menus. (SOAP-5963, CC-7171)

Sometimes, the Transaction Log did not open results of the TestCase test step. (RIA-61)

Long test case and property names were shorten in reports. (SOAP-5563)

Switching from the Form view to the XML view in the request editor changed the order of XML elements. (RIA-150)

Ready! API was unable to form an XML response view from JSON response data that contained double slash (//). (SOAP-4958)

In certain cases, the JSON and XML views did not display some JSON nodes. (SOAP-5729)

The "Certificates does not conform..." error occurred when setting an SSL connection to a server that used security certificates generated or signed with obsolete algorithms. (RIA-208)

Ready! API could hang if you simulated a request where"WS-Reliable Messaging" property was enabled. (RIA-264)

Ready! API could hang when running the DataSink test step if the response contained the $$ or ${ substrings. (RIA-392, SOAP-6246)

In some cases, the DataSink test step failed to import column names from an Excel file. (SOAP-5309, SOAP-5666)

Deleting the Target step in a cloned Data Loop cleared the Target property of the original Data Loop step. (SOAP-5246)

Sometimes, the DataSource test step failed to import property names from an Excel file: some column names were not imported. (SOAP-5732)

The DataSource test step that uses the Groovy source type stopped working after the test step editor was closed. (SOAP-5756)

When running a test case that had many DataSource test steps loading data from various sources, Ready! API could run out of memory. (SOAP-5911)

In certain cases, it was not possible to change the "Stored Procedure" property of the JDBC Request and DataSource test steps. (SOAP-5799, SOAP-6011)

The "Result column name case" property of the JDBC Request step was not saved. (SOAP-6004)

The JDBC Request test step removed trailing spaces in returned values. (SOAP-5632)

Column names returned by the JDBC Request step were not upper-case. (SOAP-5974)

The WS-Addressing actions did not support property expansions. (SOAP-4369)

Property expansions did not work for the folderPath property of the Create File test step. (SOAP-6099)

An error occurred when dragging an XML-RPC request from the APIs panel to a test case. (SOAP-5512)

If a REST VirtResponse test step has another test step specified in the "Start Step" property, and if this other step executed during the run, Ready! API also executed the VirtResponse step even if it was disabled. (SOAP-5559)

An error could occur when you were opening a request with an attachment for editing. (SOAP-5949)

The REST Request and HTTP Request test steps did not fail when they receive invalid response from a server for the first time. They failed only on subsequent runs. (SOAP-5746)

Ready! API did not display the Content-Length response header if the response was not compressed. (SOAP-6064)

Changing a property value from a Groovy script worked for certain environments only but not for the whole project. (SOAP-5798)

The NullPointerException could occur when you were trying to get an access token in the Auth Manager. (SOAP-5396)

The "Delete" command applied to multiple assertions did not remove all of them. (SOAP-5744)

Users had to reconfigure the Expected property of the Message Content assertion after they cloned the test step that contains this assertion. (SOAP-5787)

Applying the Message Content assertion to large responses could cause Ready! API to hang. (SOAP-5888)

The XPath Match assertion extracted wrong data from the RawRequest property value. (SOAP-5975, SOAP-5978)

JsonPath assertions did not work if the extracted JSON node started with a period. (SOAP-6136)

In certain cases, the JsonPath Match assertions did not work correctly. (SOAP-6231)

TestRunner logged the same assertion name for all the assertions. (SOAP-6061)

Coverage results were not rendered correctly in reports. (SOAP-6012)

The test step metrics always reported zeros for the JMS Request test step. (SOAP-4674)

LoadUI NG failed running load tests from the cloud region "Asia Pacific (Seoul)". (LOADUI-4441)

A Windows monitor failed connecting to any computer if you specified a non-existing host for it at first. (LOADUI-4656)

The Pro license was required to create assertions with the Add Assertion button in the load test editor. (LOADUI-4661)

The Load Agent tried running security scans if they were in the test project, and failed since it cannot run them. (RIA-52)

LoadUI NG could post the Socket Closed error messages to the log when a user stopped the load test running for a long time. (RIA-115)

LoadUI NG could lose a connection to a Load Agent computer while running the distributed load test. The error message said "Not possible to connect. Agent is in use by someone else...". (RIA-181)

Problems with starting Virts from Groovy scripts have been fixed. (API-5551)

It was possible to create multiple Virts with the same name. (RIA-367)

Now you can create Virts by right-clicking API definitions in the Navigator tree. (RIA-197)