CONFIGURING A TTCN-3 TEST SYSTEM IN A COMPLEX MULTI-SYSTEM ENVIRONMENT

Transcription

1 CONFIGURING A TTCN-3 TEST SYSTEM IN A COMPLEX MULTI-SYSTEM ENVIRONMENT Anke Abromeit, Dr. Rafael Schirru

2 Outline gematik The Telematics Infrastructure Testing Environment Challenges for Test Case Configuration ConfigStore Providing Configuration Data to the Test Scripts Outcome Using ConfigStore Questions 2

3 gematik (Gesellschaft für Telematikanwendungen der Gesundheitskarte mbh) Founded in January 2005 as competence center for egk and TI egk comprises applications such as Management of insured persons master data (VSDM) Emergency data management (NFDM) Electronic health record (epa) TI: Healthcare network ensuring secure exchange of information for registered users 3

4 The Telematics Infrastructure (1/2) Medical Office Clientsystem TI egk Reception Switch Connector Health Insurances 4

5 The Telematics Infrastructure (2/2) 5

6 Testing Environment workplace ASA ConfigStore 6

7 Challenges for Test Case Configuration (1/2) High degree of test automation required Many product types of the TI are mocked in TTCN-3 Components need to be configured with respect to Connection establishment comprising PKI Intended sequence of the test case behavior Expected values and outcomes 7

8 Challenges for Test Case Configuration (2/2) Global test case configuration needs to be adapted Configuration Database workplaces Workplace replacements Product replacements TC repository Base repository products of different vendors test scripts 8

9 ConfigStore: Adaptable Configuration <PsConfig id="pssimwuid1" type="record"> <soapconnectionconfig type="record"> <serverip type="charstring">${konlanip}</serverip> <serverport type="int">${soapservertlsport}</serverport> <clienttlsconfig type="record"> <identityref type="charstring">${konclientidentity}</identityref> <tlsconfigref type="charstring">serververify</tlsconfigref> </clienttlsconfig> </soapconnectionconfig> <cetpconnectionconfig type="record"> <serverip type="charstring">${workplacelanip}</serverip> <serverport type="int">${cetpserverport}</serverport> </cetpconnectionconfig> </PsConfig> 9

10 ConfigStore: Placeholders <PsConfig id="pssimwuid1" type="record"> <soapconnectionconfig type="record"> <serverip type="charstring">${konlanip}</serverip> <serverport type="int">${soapservertlsport}</serverport> <clienttlsconfig type="record"> <identityref type="charstring">${konclientidentity}</identityref> <tlsconfigref type="charstring">serververify</tlsconfigref> </clienttlsconfig> </soapconnectionconfig> <cetpconnectionconfig type="record"> <serverip type="charstring">${workplacelanip}</serverip> <serverport type="int">${cetpserverport}</serverport> </cetpconnectionconfig> </PsConfig> 10

11 ConfigStore: Testcase-specific Adaptation <PsConfig id="pssimwuid1" type="record"> <soapconnectionconfig type="record"> <serverip type="charstring">${konlanip}</serverip> <serverport type="int">${soapservertlsport}</serverport> <clienttlsconfig type="record"> <identityref type="charstring">${expiredkonclientidentity}</identityref> <tlsconfigref type="charstring">serververify</tlsconfigref> </clienttlsconfig> </soapconnectionconfig> <cetpconnectionconfig type="record"> <serverip type="charstring">${workplacelanip}</serverip> <serverport type="int">${cetpserverport}</serverport> </cetpconnectionconfig> </PsConfig> 11

12 ConfigStore: Default Replacement of Placeholders <PsConfig id="pssimwuid1" type="record"> <soapconnectionconfig type="record"> <serverip type="charstring"> </serverip> <serverport type="int">443</serverport> <clienttlsconfig type="record"> <identityref type="charstring">expiredclientidentity</identityref> <tlsconfigref type="charstring">serververify</tlsconfigref> </clienttlsconfig> </soapconnectionconfig> <cetpconnectionconfig type="record"> <serverip type="charstring"> </serverip> <serverport type="int">4443</serverport> </cetpconnectionconfig> </PsConfig> 12

13 ConfigStore: Product-specific Adaptations <PsConfig id="pssimwuid1" type="record"> <soapconnectionconfig type="record"> <serverip type="charstring"> </serverip> <serverport type="int">6200</serverport> <clienttlsconfig type="record"> <identityref type="charstring">expiredclientidentity</identityref> <tlsconfigref type="charstring">serververify</tlsconfigref> </clienttlsconfig> </soapconnectionconfig> <cetpconnectionconfig type="record"> <serverip type="charstring"> </serverip> <serverport type="int">4443</serverport> </cetpconnectionconfig> </PsConfig> 13

14 ConfigStore: Workplace-specific Adaptations <PsConfig id="pssimwuid1" type="record"> <soapconnectionconfig type="record"> <serverip type="charstring"> </serverip> <serverport type="int">6200</serverport> <clienttlsconfig type="record"> <identityref type="charstring">expiredclientidentity</identityref> <tlsconfigref type="charstring">serververify</tlsconfigref> </clienttlsconfig> </soapconnectionconfig> <cetpconnectionconfig type="record"> <serverip type="charstring"> </serverip> <serverport type="int">4443</serverport> </cetpconnectionconfig> </PsConfig> 14

15 Providing Configuration Data to the Test Scripts ConfigStore is implemented as TTCN-3 plugin The XML data is converted to TTCN-3 records Data access is provided via external functions Convenience functions implemented in TTCN-3 provide access to The first configuration element of a particular type Configuration elements by ID Configuration elements by index position in the repository 15

16 Outcome Using ConfigStore Configurations are adapted in XML files thus not requiring changes in test scripts or recompilation Support for test automation: Specific product states can be ensured Before executing a test case (test setup) After executing a test case (clean up) Support of traceability for approval tests: During test case execution only the required configuration is loaded and logged 16

17 Time for Questions 17