Technical testing and validation is a key requirement for joining the EWP Network via in-house or 3rd-party mobility software. This is indicated in the joining procedure and the Collaboration Agreement each provider has to sign. No APIs can be made available in the production network prior to the completion of successful technical testing and validation. This process is necessary to ensure the correct functioning of the digital tools; particularly for Inter-Institutional Agreements (IIAs) and Learning Agreements (LAs).
Technical testing and validation entail the usage of both automatic validators and test cases for IIAs and LAs. Such testing takes place with the reference implementation (which is the EWP Dashboard), and is carried out in concert with the EWP Dashboard technical team. Technical testing and validation, as the name suggests, needs to be carried out by the technical team which maintains and operates the respective nodes.
Please note that technical testing and validation needs to be repeated when new versions of these tools are deployed. The process itself does not guarantee a bug-free data exchange, which is why other tools are in place to monitor actual exchanges.
The list below provides an overview of all providers that successfully completed the technical testing. Conversely, if a provider features in the list but you encounter issues exchanging data, we encourage you to contact the ESCI support desk.
In order to make this process as transparent as possible, the list indicating which technical tests have been successfully completed, is regularly updated.
In August 2022, a six-month Interoperability Reinforcement Plan was launched to pave the way for a much more seamless exchange of IIA data under the aegis of EWP. A key action of the Plan was to carry out proactive debugging of the setup of 3rd-party provider nodes and re-engage in technical testing of all nodes. This was essential to ensure corrective measures had been deployed. As a result of this testing, almost all 3rd-party providers were able to improve the services they provide to their clients.
The only 3rd-party provider involved in the Interoperability Action Plan which has not yet completed technical testing and validation is SOP (Mobility-Online). The matter is being considered by DG EAC and this page will be updated when more information becomes available.