yakari
New Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
JSON path assertion fails with dots in object name
Hi, this issue is about the JSON assertions for objects containing dots in names. I use SoapUI Pro 5.1.2. I have an JSON response as follows: { "abc.efg.someName": {"check": true}, "abc.efg.otherName": {"check": true} } When I add an assertion for 'JSONPath Existence Match' with node selector I get $.abc.efg.someName.check and an error 'Invalid JsonPath expression'. To fix this I adapted the assertion to get it working. $.['abc.efg.someName'].check Please open a bug for it. ThanksSolved2.2KViews0likes1CommentRe: XPATH assertion fails with SoapUI NG
Hi, thanks for the answer. But that does not really solve the problem. The results differ each time and could be [C,A,B] and the next time [B,C,A]. So how should the assertion then be? Is there a possibility to sort the results before the assertion or use wildcards? Thanks yakari3.9KViews0likes1CommentXPATH assertion fails with SoapUI NG
Hi together, I want to migrate our projects from SoapUI Pro 5.1.2 to SoapUI NG. Within SoapUI NG the following XPATH assertion fails, which passes within 5.1.2. As result of a REST request I check the returned codes, that have always different order. <codeCategories> <codeCategory>A</codeCategory> <codeCategory>B</codeCategory> <codeCategory>C</codeCategory> </codeCategories> XPATH Assertion example Expression //codeCategories[1]//codeCategory Expected result B Returned error XPathContains comparison failed for path [//codeCategories[1]//codeCategory], expecting [B], actual was [[A,B,C]] Why does the assertion under SoapUI NG fail with the returned error? Thanks to allSolved4KViews0likes6Comments