Let's say a web service returns this part of response
<result>
<string>Good</string>
<number>10.0</number>
</result>
For any external reasons, sometimes the answer contains <number>10</number...
Radford Yes you understand it correctly. Contains assertion may be an idea. As you said it is not ideal solution and in my case I think it is better to have a single assertion for "//number" instead of "//result".
While not set in the "Expected Result" area, you can use the XPath function number() in the XPath Expression area. This will convert the different strings "10.0" and "10" into the same number.
