-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test validateCollectionsMetadataDocument_Links fails #36
Comments
The same applies to the test FeatureCollectionsMetadataOperation.validateFeatureCollectionsMetadataOperationResponse_Links() as well as |
As already documented in #7 (comment) the second test method of A.4.4.6. Validate a Collections Metadata document does not match the Requirement 13: Test method:
Requirement 13:
Expected test method:
|
Fixed with #37. Following tests still fails: WFS: http://cloudsdi.geo-solutions.it/geoserver/wfs3/
WFS: https://www.ldproxy.nrw.de/rest/services/kataster/
|
Test is still failing, but in a different way. However, the API document does not declare "text/xml" nor "application/x-yaml" for the items endpoints, but only for the collection one. One is data, the other is description, they are different documents with different encodings. Debugging the code, the test is picking the media types to be supported from "/collections/", so somewhat assuming whatever format can be used to encode a collection description, but it's not the case, see: |
I did test the master, yes.. thought everything was ready and merged already, I have missed the PRs were yet to be integrated |
PR is merged now. However, as described in #36 (comment), the test is still failing with http://cloudsdi.geo-solutions.it/geoserver/wfs3/. In our opinion, the test failure is correct. |
The test FeatureCollectionsMetadataOperation.validateCollectionsMetadataDocument_Links() currently fails against http://cloudsdi.geo-solutions.it/geoserver/wfs3 multiple times with the failure
Collections Metadata document must include links with relation 'item' for each supported encodings. Missing links for types [text/xml application/x-yaml]
The tests checks for each collection in the collections metadata response if there are links for alternative encodings in every other media type described in the API definition.
Expected are "Alternate encodings of this document in every other media type as identified by the compliance classes for this server.", as described in https://rawgit.com/opengeospatial/WFS_FES/master/docs/17-069.html#_validate_the_feature_collections_metadata_operation_response
Known conformance classes and expected media types:
text/html
application/geo+json
for feature collections and featuresapplication/json
for all other resources.application/gml+xml; version=3.2;profile=http://www.opengis.net/def/profile/ogc/2.0/gml-sf0
for feature collections and featuresapplication/xml
for all other resourcesapplication/gml+xml; version=3.2;profile=http://www.opengis.net/def/profile/ogc/2.0/gml-sf2
for feature collections and featuresapplication/xml
for all other resourcesThe text was updated successfully, but these errors were encountered: