Forum Discussion

iacsinte's avatar
iacsinte
New Contributor
8 years ago
Solved

BUG? For nodes containing @ JSONPath Match works differently in SoapUI and SoapUI NG

We have names of the id fields starting with "@" char and each item created has existence check on that field.

JSONPath:          $.bean.@id

Expected result:  true

 

In Soap UI Pro 5.1.2 the "Select current value" function auto-completes with "true".

In Ready!API 1.7.0 SoapUI NG the same operation auto-completes with "false".

 

Also, the test steps from the test cases that are following are using the ID value. Using "Get Data" option, the @id element can be selected from a previously executed step but when executed it is resolved to null value.

 

For example, having a POST that has ($.bean.@id) in response, followed by a GET that uses the id:

(${POST - addItem#Response#$.bean.@id})

will result in executing the request:

GET http://localhost:6080/rest/v1/application/.... /item/null HTTP/1.1

 

Is there a workaround for this issue?

 

Thanks,

Ionut

  • Hi Ionut,

     

     

    From my understanding, Ready! API and SoapUI Pro should return the same result. First of all, I suggest that you update to the latest Ready! API version - v. 1.8 - and check if you see the same behavior. If you do, please submit this issue to our Customer Care Team: http://support.smartbear.com/product-list/

3 Replies

  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)

    Hi Ionut,

     

     

    From my understanding, Ready! API and SoapUI Pro should return the same result. First of all, I suggest that you update to the latest Ready! API version - v. 1.8 - and check if you see the same behavior. If you do, please submit this issue to our Customer Care Team: http://support.smartbear.com/product-list/

    • iacsinte's avatar
      iacsinte
      New Contributor

      After upgrading to Ready!API 1.8.0 the problem was not reproduced. Thanks.