Hi I am running a Rest API in both ReadyAPI (pro version of SoapUI) and also in postman. The response pattern in json in postman valid while in ReadyAPI for some fields zeroes are appended after decimal value even for a integer type field like for example
"PackSize": 60 (this is in postman which is right)
"PackSize" : 60.0000000000000000 (this is in ReadyAPI response which is incorrect)
Also for some fields values are returned as hex decimal pattern for example
"PrivateTax" : 0E-16 (this is in ReadyAPI which is incorrect)
"PrivateTax": 0(this is in postman which is right)
I have attached json files of the responses in both postman and ReadyAPI for your reference. Am I missing any setting in ReadyAPI which is causing this issue
The version of ReadyAPI I am using is ReadyAPI 2.3.0
Build Date: 2018-03-06T16:28:42Z(433)
It works just fine for me.
But how do you get your response? Where do you look for it? Is it in a groovy script? Is it in the JSON response tab? And what kind of request are you making? Is it a POST HTTP Request? Could you give more details? I am curious about this.
Maybe it's a bug? It works fine for me. I don't see why there would be a property to convert your JSON response to hexadecimal.
I created a mock service with the JSON you posted. This is how I could test it. Maybe just ask for smart bear support?
I am attaching the screenshots of API called in Postman and ReadyAPI. they both are exactly the same API's with same input parameters,exactly same environments and no extra logic has been applied in either of them. Has anyone had this kind of experience before or am I missing any setup in ReadyAPI which is causing this. Can someone please share some knowledge.
I am not sure if there's a setting that directly controls this, but I've seen similar issues where ReadyAPI will pretty-print or format a response. If you inspect the RAW of the response, is it still the same?
I am experiencing the same issue after installing 2.3 last week. I am using a simple built in assertion on the response, comparing to the expected result stored in SQL DB. I have both 2.2 and 2.3 installed so can easily run the same test in both to see the different assertion result; success in 2.2 and failure in 2.3. I have opened a support case. But has anyone already successfully resolved this?