You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the fix in #34 also decimal types are handled and properties with this type are updated. This leads in our case to another problem. The test fails with the following reason:
Unexpected result evaluating XPath expression with context node app:osm_protected_area: tns:way_area[1] = "515609.00"
The feature contains "515609.0" after the update (and before reset):
It seems, that a the differences in the notation of the decimal (with/without second 0) causes the assertion failure.
The text was updated successfully, but these errors were encountered:
lgoltz
changed the title
assetrion of the test "update Simple Property Value" is too strict
Assertion of the test "update Simple Property Value" is too strict
Jul 14, 2016
A string comparison is being done here, not a numeric one. The assert should be modified to include datatype info so a cast can be performed if necessary.
e.g. number(tns:way_area[1]) eq 515609.00 evaluates to true
Since the fix in #34 also decimal types are handled and properties with this type are updated. This leads in our case to another problem. The test fails with the following reason:
The feature contains "515609.0" after the update (and before reset):
It seems, that a the differences in the notation of the decimal (with/without second 0) causes the assertion failure.
The text was updated successfully, but these errors were encountered: