SoapUI-4.5.1 changelog - XPath wildcard
Hello, in the SoapUI-4.5.1 changelog you describe the following: "Improved XQuery and XPath wildcard match handling to match whole or portions of values." Could you explain me what is improved ...
Forum Discussion
SmartBear_Suppo
Alumni
AlumniYes,
Basically we had complaints from users that using wild card when matching node value or attribute value. Wildcard was capable only to match whole value.
For example if XPath expression:
//DirectionsResponse[1]/route[1]/leg[1]/step[1]/start_location[1]/lat[1]
for result have "-34.9286900" if I put "-3*.9286900" for expected value and check "Allow Wildcards" then "-30.9286900", "-31.9286900", etc will be matched.
robert
/Smartbear
Basically we had complaints from users that using wild card when matching node value or attribute value. Wildcard was capable only to match whole value.
For example if XPath expression:
//DirectionsResponse[1]/route[1]/leg[1]/step[1]/start_location[1]/lat[1]
for result have "-34.9286900" if I put "-3*.9286900" for expected value and check "Allow Wildcards" then "-30.9286900", "-31.9286900", etc will be matched.
robert
/Smartbear