Opened 14 years ago
Closed 13 years ago
#3493 closed defect (fixed)
msautotest/wfs_simple - several failures
Reported by: | warmerdam | Owned by: | assefa |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | msautotest | Version: | svn-trunk (development) |
Severity: | normal | Keywords: | wfs |
Cc: | assefa, tomkralidis |
Description
I am seeing the following items with the wfs_simple test fail:
- wfs11_get_feature_id.xml - looks like an axis order change.
- wfs11_get_feature_maxfeatures.xml - getting Nova Scotia instead of Quebec, lots of geometry diffs, apparent axis order issue.
- wfs11_get_feature_srsname.xml - only difference is that numberOfFeatures is no longer in the collection, ok?
- wfs11_get_feature.xml - looks like an axis order difference.
Could someone confirm that the altered axis order is ok? And that the numberOfFeatures should not longer be present? Also, can someone check into why the maxfeatures test is getting different results?
Let me know if you aren't seeing difference like those I describe, in which case I can provide additional details.
Change History (7)
comment:1 by , 14 years ago
Owner: | changed from | to
---|
comment:2 by , 14 years ago
- wfs11_get_feature.xml - updated the expected result (axis order): corrected
- wfs11_get_feature_hits.xml: test removed as explained in the #3309 a timestamp must be generated if the request is a hit. So we can not really have an exact match.
- wfs11_get_feature_id.xml axis change : updated the expected result
- wfs11_get_feature_srsname.xml : updated the expected result (number of features is optional as explained in #3309)
looking into the max feature test a bit later ...
comment:3 by , 14 years ago
Assefa,
I neglected to mention it, but I've added logic in the tests to remote the contents after timeStamp= so that timestamps don't impact the tests. You just need to use [RESULT_DEVERSION] instead of [RESULT] in the test.
I have re-enabled this test with RESULT_DEVERSION (r10371).
Thanks for the other checks/fixes.
Leaving open for the maxfeature test.
comment:4 by , 13 years ago
Reviewing...
I see wfs11_get_feature.xml and wfs11_get_feature_id.xml are still failing for me with what appears to be axis order issues. Perhaps a regression somewhere?
I'm also seeing an axis order failure with wfs11_get_feature_id_gml2.xml.
wfs11_get_feature_maxfeatures.xml is also failing.
Is this something you will have time to look into?
comment:6 by , 13 years ago
This is related to corrections on the axis order #3574. The correct expected results are committed.
looking into this ... the test I believe were not updated after the axis order changes. I will possibly commit new tests