DG DGIT is developping specifications for the OOTS (eWallet) project. Conformance tools have been developped using the GITB framework, and more especially the Test Bed’s XML validator.
In this context, DG DGIT want to use the Gazelle Test Bed to execute the peer-to-peer test cases. To ease the verification of the exchanged messages, the Gazelle Proxy shall be able to call the Conformance tools through EVSClient. In other words, EVSClient shall be extended to call the GITB SOAP API (or alternatively the REST API).
Time constraints: A Projectathon is scheduled for mid-April 2023 (Week 16).
Our main goal is being able to integrate GITB based conformance testing tool within the Gazelle Test Bed to automate the validation of the messages captured by the Gazelle Proxy during the testing events.
Workflow will be made easier for participants and monitors.
All the pieces of proof will be stored in a single space.
Full advantage of using the Gazelle Proxy and the Gazelle test bed in general.
Demonstrate the ability of the Gazelle test bed to interact with GITB testing tools.
Integration of the GITB Validator is also something we have forseen to be able to reuse their Json validator (validation of WIA/AIR messages - DICOM Web) so there is an opportunity to mutualize the work here.
On the longer term, it will allow Gazelle Test Management to interact with other GITB based implementations.
The SOAP API of the XML validator is the same regardless of the specific instance (the OOTS instance we are discussing or a potential future additional instance) and is detailed here (a SOAP UI project is also available as part of the documentation). A REST variant of the SOAP API will also be made available. It's planned to be released mid to end November. In the case of the REST API, inputs will be provided via JSON and the report will be returned in XML format (the exact same XML you already get through the UI and SOAP API). The GITB development team also plans to prepare an XSL stylesheet that can be customized to use Gazelle's style.
Full documentation is available here: https://www.itb.ec.europa.eu/docs/guides/latest/validatingXML/index.html#validation-via-soap-web-service-api. In case you are considering using Java to call the SOAP API, we have a step-by-step guide that walks you through the development of a client. The simple project presented through this guide is also available on GitHub.