Following the development of the OGC standard for API - Features, there was an interest from the INSPIRE community to adopt this specification. As a part of the proof of concept to adapt it, a task to create Executable Test Suites in the INSPIRE validator. The approach was to replicate the workdone for WFS Direct to define an INSPIRE ETS and a connector to the OGC TEAM Engine for executing validations of an API - Features endpooint. This EIP covers the adaptation of the TEAM Engine Test Driver for this API.
Proposed change
The changes needed to adapt the Test Driver would be:
Create a new Test Object Type for API Features, depending on the Web Services type
Define a new detection expression for this Object Type.
Load the ETS information from the TEAM Engine on loading the Test Driver (label, endpooint,version...)
Create a new Test Task for the TEAM engine to execute Test Runs against the TEAM engine endpoint.
Alternatives
The alternative considered for this task was to define a new Test Driver independent from the current one for integrating this development, however the changes would be roughly the same.
Funding
Is there full or partial funding available for implementing this proposal?
Funding is provided by JRC through the INSPIRE validator team.
Additional information
An experimental implementation of this EIP was developed by the JRC contractors and uploaded on their premises here. The code will be uploaded to a project fork of the ETF to prepare it for an eventual pull request.
Background and Motivation:
Following the development of the OGC standard for API - Features, there was an interest from the INSPIRE community to adopt this specification. As a part of the proof of concept to adapt it, a task to create Executable Test Suites in the INSPIRE validator. The approach was to replicate the workdone for WFS Direct to define an INSPIRE ETS and a connector to the OGC TEAM Engine for executing validations of an API - Features endpooint. This EIP covers the adaptation of the TEAM Engine Test Driver for this API.
Proposed change
The changes needed to adapt the Test Driver would be:
Alternatives
The alternative considered for this task was to define a new Test Driver independent from the current one for integrating this development, however the changes would be roughly the same.
Funding
Is there full or partial funding available for implementing this proposal? Funding is provided by JRC through the INSPIRE validator team.
Additional information
An experimental implementation of this EIP was developed by the JRC contractors and uploaded on their premises here. The code will be uploaded to a project fork of the ETF to prepare it for an eventual pull request.