INSPIRE Test Framework Clemens Portele Jon Herrmann interactive

INSPIRE Test Framework Clemens Portele / Jon Herrmann interactive instruments Gmb. H

Scope and objectives § ARE 3 NA project of JRC with Pw. C and interactive instruments, until mid 2017 § Support and accelerate ongoing work in the MIG (MIWP-5) § Conformance testing of INSPIRE Metadata, Network Services and Data Sets § Supporting interoperability of applications and services § Currently different validators with different tests are used in Member States § Development of a reusable open source reference validator § The tool should test the overall functioning of the infrastructure while offering configurable software and test rules for organisations to test conformance § Build upon existing solutions in the Member States and European projects to create a ‘reusable’ testing infrastructure for INSPIRE

Approach § Requirements are derived from the IR and TG § For each requirement a corresponding conceptual test is created as an Abstract Test Suite § A Executable Test Suite (ETS) is derived from an Abstract Test Suite (ATS) and works on a sufficiently detailed level to interact with the test object § A Executable Test Suite is executed in a test engine

Requirements § Initial requirements, use cases and ideas gathered in MIWP-5 Validation & conformity subgroup § Key requirements for the first version of the INSPIRE validator determined in the MIWP-5 Briefing and Planning meeting on INSPIRE validator implementation with JRC and MIWP-5 subgroup leaders in December 2015 § Only key requirements listed on next slides § Additional requirements with a lower priority may not be realized within this project, but may be subject to future developments

Requirements § Architecture § Deployable centrally and in the user’s environment § Based on a generic test engine that can process one or more ETS § Test engine and ETSs are open source § Support different types of tests § Data tests (XML, potentially very large) § Metadata tests (XML, smaller, together with the Network Service tests) § Network service tests (Web Service) § Potentially different test components required § Test engine interaction through GUI and API § Provide test progress information § Multilingual (GUI only, not the ETSs)

Requirements § Test projects and management § ETS should allow easy modification § Enable validation against specific schema versions / versions of ETS § Severity or weight of individual rules § Requirement error § Recommendation warning § ETS rules link to ATS rules / requirements they test § Test results § Human-readable HTML § Machine-readable XML or JSON § Multilingual § Timestamped

Central deployment LMO, SDI User JRC Software User Service INSPIRE Test Framework Data Set ETS ATS

Local deployment, e. g. by an LMO Software User INSPIRE Test Framework Service Data Set Additional ETS (eg national profiles) ETS ETS ATS

Specification Test Framework Test Suites Requirements now Initial Design ATS Demonstrator (based on ETF) 04/2016 Baseline Design Alpha release Testing and Validation Updated Design Incremental releases Release 1. 0 (dates to be confirmed) ETS (1 theme, 1 DLS, MD? ) 07/2016 ETS (…) ETS (Annex I, 3 DLS, MD, +) 03/2017

Initial Design § Based on key requirements (“must-have”), considering also ”nice-to-have” capabilities, if possible § Evaluation of existing test engines against requirements § Coverage of requirements § Effort for implementing required features § Continued development and maintenance § Analyse integration of the basic OGC CITE tests with a pre-defined test dataset and accessible via an API

Demonstrator § To illustrate and discuss design options and requirements § Based on ETF and existing INSPIRE network service tests as used in the ELF project and existing Schematron for data tests § Fastest option for a demonstrator § Initial deployment in February § Add additional data and metadata tests until April § ETF meets most requirements

Alpha release § First release based on ATSs and design report § ETSs: § One annex I theme (v 3 and v 4) § One download service option § Metadata (current technical guidance) § Not all requirements will be supported § Date will depend on implementation decisions

Potential contributions from the MIG-T (MIWP-5 sub-group) § Highest priority § Discussion of requirements and conceptual model of the INSPIRE validator § Provision of test objects (data, metadata, network services) for testing the Test Framework and its Executable Test Suites during the development and for use in unit tests § Testing of draft versions § Lower priority, but very welcome § Development of an Executable Test Suite, in particular if the test suite is not included in the list of test suites with the highest priority § Contributions to the development of the Test Framework, in particular, if the implemented requirement is not part of key requirements § Translations for linguistic texts used in the web application and the online documentation

Potential contributions from the MIG-T (MIWP-5 sub-group) § How to manage? § Development of Test Framework and Executable Test Suites will use Git. Hub § Contributors will get write access to the repositories