Is JSON nonexistence a regression error in SoapUI 5.7.0?
I've seen several posts in different forums about a change in behavior that I've experienced myself at least between SoapUI 5.4.0 and the latest SoapUI 5.7.0. I have several test cases with assertions validating that elements in a JSON payload are not present. This is accomplished using either a JsonPath Existence Match assertion checking for a value of false or with a JsonPath Count assertion checking for a value of 0. But in SoapUI 5.7.0, checking for a JSON path that does not exist produces an error internally without checking anything. I've seen one viable workaround in which the internal XML representation of the payload can be validated with the exists() XPath XQuery function, but the point is the regression in behavior. SoapUI 5.4.0 successfully performs both types of JSON assertions for nonexistence. My SoapUI project has many such assertions and has proven very difficult to automate the migration from JSON assertions to XPath assertions. How is this change in behavior not a regression error, and if it is, should I log a bug against SoapUI 5.7.0?