Forum Discussion

Flo's avatar
Flo
Contributor
6 years ago
Solved

JsonPath Assertion difference between ReadyAPI and SoapUI Community

Context : I develop my test using ReadyAPI/SoapUI Pro from my own computer. I launch tests in continuous integration process from Jenkins using testrunner.sh from free SoapUI.   ReadyAPI 2.4.0 (...
  • Flo's avatar
    Flo
    5 years ago

    You said it is a bug, but here is an extract of the documentation from json-match Documentation page

     

    Expression containing filters ([?(filter)] and array slices ([start:end] always returns arrays, even if the resulting array contains a single item.

     

    So, it seems like a featured-bug or so one !

     

Radford's avatar
Radford
Super Contributor

The JSONPath library that Ready API uses was updated in version 2.3, The JSONPath Reference documentation page talks about differences in the returned data before and after this version (see the end of the section headed "Usage Notes and Considerations").

 

I'm not a JSON expert so do not know if this applies to you or not, but worth a read I think. If SoapUI Community 5.4.0 was using the older version of this library, this could explain the difference?

 

I know this is not an answer, but hope it helps.

 

I you think it is a bug I would log a support case at:

 

https://smartbear.secure.force.com/support/WebToCase?showHeader=0&product=ReadyAPI

Flo's avatar
Flo
Contributor
6 years ago

This is a very nice point !

I checked : SoapUI Community is using JsonPath 0.9.1.

I tried to use json-path-2.4.0-fixed.jar for SoapUI Community, addind related dependencies but I am facing NoClassDefFoundError. I guess there are bad dependencies using 2.4.0 version.

  • Radford's avatar
    Radford
    Super Contributor
    6 years ago

    So looking at the versions of the JayWay JSONPath library ReadyAPI uses in its various different versions (from the JSONPath Reference doc page linked above):

     

    • ReadyAPI 2.3 and later – JayWay JSONPath 2.4.0
    • ReadyAPI 1.4.1 – 2.2 – JayWay JSONPath 2.0.0
    • ReadyAPI 1.1 – 1.4.0 – JayWay JSONPath 0.9.1

    You have to go all the way back to ReadyAPI 1.4 to match the JSONPath library version in the comunity edition.

     

    Sorry, I don't think I'm going to be able to help further. Please do update here if you find a solution.

    • Flo's avatar
      Flo
      Contributor
      6 years ago

      I opened a Support Ticket for this issue : Ticket URL

      It is confirmed as a bug but I don't know when it will be released. I am waiting for this

       

      • Radford's avatar
        Radford
        Super Contributor
        6 years ago

        If it's been confirmed as a bug by SmartBear I would ask to see if the fix can be included in the Maintenance Build. When I last upgraded Ready API I had to get multiple fixes released in the Maintenance Build, before I could successfully upgrade and run all of our test projects.