CEF e Delivery Industry Day CEF e Delivery

CEF e. Delivery Industry Day CEF e. Delivery Conformance Testing 30 November 2016 Maarten Daniels CEF e. Delivery technical team

What I will talk about Goal of Conformance Testing Benefits of CEF e. Delivery Conformance Testing From specifications to test cases Sample AS 4 test case Sample SMP test case Conformance Testing process What does Conformance Testing not cover? Future enhancements Take action and become conformant Q&A

Goal of Conformance Testing Verify that an implementation of the CEF e. Delivery components, conforms to the relevant specifications: • e-SENS AS 4 profile • OASIS SMP profile

Benefits of CEF e. Delivery Conformance Testing • Get assurance that a software package is conform the CEF e. Delivery specifications • Supporting tools developed and proofed in the context of the e-SENS project • Testing supported by e. Delivery team • Quick testing cycle with reduced cost and time • Testing anywhere at anytime • Tests are fully domain-neutral • Ready to use test cases and test platform

From specifications to test cases

Sample AS 4 test case The e-SENS AS 4 specifications define the requirements

Sample AS 4 test case The requirements are used as input to create Test Assertions

Sample AS 4 test case The Test Assertions are implemented as Test Cases on the Test Platform

Sample AS 4 test case The Test Cases are written in MTDL (Minder Test Definition Language), based on Scala.

Sample SMP test case The OASIS SMP specifications define the requirements

Sample SMP test case The requirements are used as input to create Test Assertions

Sample SMP test case The Test Assertions are implemented as Test Cases on the Test Platform Minder HTTP client SMP HTTP GET

Sample SMP test case The Test Cases are written in MTDL (Minder Test Definition Language), based on Scala.

Conformance Testing process

Conformance Testing process

Conformance Testing process

Conformance Testing process

Conformance Testing process

Conformance Testing process Test reports are automatically produced from the test platform and signed by the CEF e. Delivery team

e-SENS AS 4 conformant solutions More information on CEF Digital Conformant Solutions > DOMIBUS FLAME HOLODECK IBM LAURENTIUS MENDELSON RSSBus ADES EESSI AS 4. NET Conformant Ongoing Registered

OASIS SMP conformant solutions More information on CEF Digital Conformant Solutions > phoss SMP Conformant

What does Conformance Testing not cover? • • Conformance testing is complementary to: • Functional testing • Connectivity testing • Interoperability testing • Load testing • Vulnerability testing Current Test Cases are testing a component against its own specifications and do not verify integration with other components

Take action and become conformant • Additional Quality Assurance for your product • Increase chances for successfully communicating with other implementations Benefits of being conformant to the CEF e. Delivery specifications • Get brand product visibility by being present on the list of conformant implementations • Be ready for call for grants that require an implementation to be conformant

Take action and become conformant Join us on the e. Delivery User Community: • Discuss in the forum • Ask questions • See that latest news

Questions & Answers

Find out more on CEF Digital DIGIT Directorate-General for Informatics DG CONNECT Directorate-General for Communications Networks, Content and Technology Contact us CEF-BUILDING-BLOCKS@ec. europa. eu/cefdigital © European Union, 2016. All rights reserved. Certain parts are licensed under conditions to the EU. Reproduction is authorized provided the source is acknowledged.