I am worried there is a serious bug in XQuery assertions, but I am hoping this is just some config thing I'm missing. I just noticed that one of our test cases passed, even though it should be failing (related to Google socialgraph being retired recently). I ran the exact same test with soapUI 4.0.1 and it failed the assertion as expected.
I have this XML returncode:
And it passes this XQuery assertion:
count(socialgraph/confirmedMatch) > 0
With expected result:
Even though the result clearly is 'false'.
I was able to get it to work properly, by removing the xml tags from the expected result (it now fails the assertion) - but this is definitely different from 4.0.1. I can change those XML tags in the expected result to anything <BLAH>whatever</BLAH> and the assertion passes. The worst part is though, that if you use 'select from current' to prime the assertion as it were, it still puts in those xml-fragment tags around the true/false, but they make the assertion meaningless, it seems.
Am I just missing something basic here or is this indeed a serious bug? I'm concerned this invalidates a whole range of our tests.