search

inspire-eu-validation / download-service

Abstract Test Suite for the Technical Guidance for the implementation of INSPIRE Download Services
Creative Commons Zero v1.0 Universal
2 stars 4 forks source link

Write ATS for TG requirement 39 #39

Closed thijsbrentjens closed 9 years ago

thijsbrentjens commented 9 years ago

"A simple service to perform the Describe Spatial Dataset and Get Spatial Data Set operations shall be provided and described by an OpenSearch description document."

thijsbrentjens commented 9 years ago

This requirement is in itself not automatically testable, because it does not provide enough technical details. However, requirement #8 does already require an OpenSearch Description to be linked from. What to do with this requirement? Still write an ATS? Or should we consider this specific requirement not testable?

ilkkarinne commented 9 years ago

Maybe the test for this requirement should just a test for existence of a valid OpenSearch Description document?

aquaglia commented 9 years ago

The OpenSearch description is essential to comply with the Network Service Regulation. There is a lot to test because of the sentence saying: "that provides the operations metadata for the Download Service".

ilkkarinne commented 9 years ago

The required operations are specified by requirements #41, #42, #43 #44 and #45, and the link to a valid OpenSearchDescription by requirement #8, so I think the tests for those should also cover this requirement.

aquaglia commented 9 years ago

Ah, right, so what is left is just that the link returns an OpenSearch document containing the inspire extensions.

thijsbrentjens commented 9 years ago

Requirement #8 already checks for existence of the document, see https://github.com/inspire-eu-validation/ats-download-atom/blob/master/A.08.IR222.TGR8.linktoOpenSearchDescription.md. Do we need another check for existence for #39? I'd say it is redundant and we just refer to #8 here

ilkkarinne commented 9 years ago

As long as #8 checks the existence of the OpenSearch Description link, it's resolvability and the structure of the returned document (the OpenSearch spec compliancy only), I think this requirement does not require any new test on top of what's already written for requirements #41, #42, #43 #44 and #45

thijsbrentjens commented 9 years ago

So I think we can close this one, right? Otherwise: please reopen and comment it :-).