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

A.04.TGR4.conformtoOpenSearch1.1 #51

Closed jensscheerlinck closed 8 years ago

jensscheerlinck commented 8 years ago

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685

Comment

Validation of OpenSearch description document is more than a test case. There is no schema document or similar that could be used. (If a single test case would be ok here, there would be no need to break INSPIRE conformance classes down into test cases, just one test case 'test conformance against INSPIRE Technical Guidance' would be sufficient.)

Proposed Change

Define ATS for the OpenSearch description and identify the test cases to a level that unambiguously identifies the assertions to test.

thijsbrentjens commented 8 years ago

Similar to #48, #50.

For OpenSearch there does not seem to be a generally accepted test we could refer to. I think developing such a test would be out of scope for INSPIRE specifications. Therefore my proposal is to change this test to not testable.

What do others think of this?

(Compare this to XML or HTTP: I think it is out of scope to write an ATS for this kind of general standards/specifications for the INSPIRE TG.)

thijsbrentjens commented 8 years ago

Discussed in the call on resolution.

The Test Case refers to a specification maintained by a third party. The goal of the ATSes is to test the specific requirements of INSPIRE. For external specifications, ATSes will refer (recommended) test methods of the third party where applicable.

So the Test Case will require to validate the OpenSearch document (because that is the TG requirement); on the ETS level (Executable Test Suite level) a choice will be made how exactly this validation will be done.

So no changes for now.