Removed JSON-XML representation while there is no Json Assertions
I used to use free version of SoapUI 5.0.0. I've got a big JSON project whole covered by xpath assertions.
I had installed 5.1.3 and what i saw.. you've removed the JSON-XML representation, like so you did in pro version. But there is no Json Assertions in free version. And for what reason there is JsonPath property transfer then?
Will you add Json Assertion to free version? No hope? What will happen with existing xpath assertions in further versions? Should i be worried it will be no longer sustainable? I just want to understand how should I act now..
Re: Removed JSON-XML representation while there is no Json Assertions
I cannot answer for the SoapUI product changes that you are having an issue with (good to point them out though), but in terms of work-arounds a good alternative is to use a script assertion using either:
- JSONSlurper - I have written an article showing a simple example of this (please see https://www.packtpub.com/books/content/restful-web-service-mocking-and-testing-soapui-raml-and-json-...
- JSONPath - This is similar, I could probably knock you together a quick script on this if you need one? SoapUI pro uses JSONPath too. but its quite easy to script.
One advantage to the script alternatives is that they don't have any issues translating XML to JSON, which the SoapUI JSON representation did for certain types of XML documents.
Hope this helps,