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
The complete Teamengine test report (XML) included as an attachment.
List of errors and interpretation (incomplete)
test-method status="FAIL" signature="getCapabilities_missingServiceParam()
GetCapabilities without SERVICE=WFS should yield http 400 error. https://demo.mapserver.org/cgi-bin/wfs?VERSION=2.0.0&REQUEST=GetCapabilities
Mapserver is sending http 200 and traditional mapserv(): Web application error. Traditional BROWSE mode requires a TEMPLATE in the WEB section, but none was provided.
test-method status="FAIL" signature="getFullCapabilities()
GetFeature: the 'resolve' parameter must contain 'local' as an allowed value.
Whatever it means but this is what Geoserver has in the GetCapabilities
7.6.4 Standard resolve parameters
7.6.4.1 Parameter Semantics
Servers that conform to this International Standard shall implement the ability to resolve local resource
references etc.
test-method status="FAIL" signature="describesBasicWFS(org.opengis.cite.iso19142.ProtocolBinding)
The filter constraint 'ImplementsSorting' must be 'TRUE' for all conforming Basic WFS implementations.
The demo server has
This may be due to the data layers in the demo service which do not support sorting (shapefiles?)
"FAIL" signature="inconsistentFeatureIdentifierAndType(javax.xml.namespace.QName)
Error appears at line 1868 of the report. By the description Mapserver should send a http 400 error status but it sends OK. <![CDATA[Unexpected HTTP status code. expected [400] but found [200]]]>
<test-method status="FAIL" signature="getFeaturesByType(org.opengis.cite.iso19142.ProtocolBinding, javax.xml.namespace.QName)
Line 2695: Test report contains many schema related warnings and one error:
Severity: ERROR
Message: src-resolve: Cannot resolve the name 'xlink:simpleAttrs' to a(n) 'attribute group' component.
Location: line=251 column=52
<test-method status="FAIL" signature="implementsTransactionalWFS(org.testng.ITestContext)
I do not understand what is wrong. Server does not need to support WFS-T. Still the report shows this:
[Unexpected result evaluating XPath expression with context node #document:
//ows:Constraint[@name='ImplementsTransactionalWFS']/ows:DefaultValue = 'TRUE' expected [true] but found [false]]]
The text was updated successfully, but these errors were encountered:
Some CITE tests fail.
Service used in the test: https://demo.mapserver.org/cgi-bin/wfs?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetCapabilities
The complete Teamengine test report (XML) included as an attachment.
List of errors and interpretation (incomplete)
GetCapabilities without SERVICE=WFS should yield http 400 error.
https://demo.mapserver.org/cgi-bin/wfs?VERSION=2.0.0&REQUEST=GetCapabilities
Mapserver is sending http 200 and traditional
mapserv(): Web application error. Traditional BROWSE mode requires a TEMPLATE in the WEB section, but none was provided.
GetFeature: the 'resolve' parameter must contain 'local' as an allowed value.
Whatever it means but this is what Geoserver has in the GetCapabilities
Corresponding part of the WFS 2.0. standard
The filter constraint 'ImplementsSorting' must be 'TRUE' for all conforming Basic WFS implementations.
The demo server has
This may be due to the data layers in the demo service which do not support sorting (shapefiles?)
"FAIL" signature="inconsistentFeatureIdentifierAndType(javax.xml.namespace.QName)
Error appears at line 1868 of the report. By the description Mapserver should send a http 400 error status but it sends OK.
<![CDATA[Unexpected HTTP status code. expected [400] but found [200]]]>
<test-method status="FAIL" signature="getFeaturesByType(org.opengis.cite.iso19142.ProtocolBinding, javax.xml.namespace.QName)
Line 2695: Test report contains many schema related warnings and one error:
I do not understand what is wrong. Server does not need to support WFS-T. Still the report shows this:
The text was updated successfully, but these errors were encountered: