1. 2016.3 Validation and Conformity testing – Status & next steps
Michael Lutz INSPIRE MIG-T meeting #38 Ghent March 2017

2. Status Testing of reference validator and ETSs ongoing
Several issues logged in Github  proposed governance process
Results collected from testers through EUSurvey
Initial results are on the wiki
Generally positive feedback
How important is for you that a common validator is made available and maintained by the EC?  Very important (5/5)
v1.0.0beta release being tested by JRC  new capabilities

3. New capabilities in the v1.0.0beta release

4. Support for SoapUI tool as test engine, Executable Test Suites for Download Services added

5. Test multiple Executable Test Suites during a single Test Run

6. REST API complete, using Swagger for documentation

7. More information about Executable Test Suites in the user interface
Other changes
Multiple XML files can be selected for a single Test Run (metadata and data tests)
More information about Executable Test Suites in the user interface
Many other improvements to both software and tests – see closed issues and commits on GitHub for details
Planned
Add test driver for OGC TeamEngine (support WFS 2.0 and GML 3.2 CITE tests of OGC)
Documentation (for users, for developers, for test developers, for administrators)
Address known open issues
Decision about hosting the reference validator
Software:
Tests:

8. Future work Complete ETS for
Annex II & III data themes
SOS & WCS-based download services
view services
metadata (TG v2.0)
Maintenance, further development and roll-out of the testing framework
Long-term sustainability & funding
Making our outputs available for others to build on: SMEs, MS organisations, OS community, etc.
Creating a dedicated INSPIRE resource or embedding this in the Interoperability Testing (led by ISA²)
Outreach and promotion

9. Dealing with feedback on ETS, ATS, TGs
Feedback in Github (indirectly) referred to
the INSPIRE test framework (the software implementation) (bugs, features/enhancements)
the test implementation in the ETS (bugs, features/enhancements)
the test definition in the ATS (errors, disagreement with interpretation)
the underlying requirements in the TG (errors, disagreement with interpretation)
Examples for TG-related comments:
Metadata ETS: md-iop.a.3 Encoding should not require specification
Metadata ETS: Using gmx schemas

10. Proposed Governance approach
All issues to be submitted via a common helpdesk, ideally as part of the Knowledge Base
Initial assessment and classification by JRC (triage)
Potentially supported by contractors
Minor issues/bugs to be fixed directly
Notable issues to be discussed in a MIG sub-group on validation (continuation of MIWP-5) and either fixed directly or submitted to MIG
Any changes with major impacts on the validator, or impacting on the TGs, would be discussed with the MIG
Clear and timely communication and release planning on changes/developments is crucial