1 / 28

IHE Testing Tools

IHE Testing Tools. An overview. The past (and current) . Mesa Tools In house testing for Vendors C++, Perl Kudu Connectathon management tool : kind of speed dating software. Allows vendors to enter configuration and find test partners Allow sponsor to control connectathon’s progress

rashad
Télécharger la présentation

IHE Testing Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IHE Testing Tools An overview

  2. The past (and current) • Mesa Tools • In house testing for Vendors • C++, Perl • Kudu • Connectathon management tool : • kind of speed dating software. Allows vendors to enter configuration and find test partners • Allow sponsor to control connectathon’s progress • PHP, Postgresql DB

  3. The Future (Gazelle) • Improve quality of testing • Introducing conformance testing where we only had interoperability testing • Unify Kudu and Mesa into one tool • Target to Vendors, Users and Sponsors • Opensource • Open and evolving architecture

  4. Interoperability / Conformance Specifications/Standards ConformanceTesting ConformanceTesting ImplementationA ImplementationB Interoperability testing VendorA Vendor B Projet IHE-Dev Inria Rennes

  5. Gazelle

  6. Gazelle Architecture Gazelle Control System Database External Validation Services External Validation Services Gazelle Actor (Simulators) Configuration Info External Validation Services Gazelle Test Engine Gazelle Actor (Simulators) External Validation Services Control Gazelle Actor (Simulators) Gazelle Actor (Simulators) Feedback Gazelle Actor (Simulators) System Under Test System Under Test System Under Test System Under Test Tests Scenario Proxy Network Projet IHE-Dev Inria Rennes

  7. Proxy

  8. Requirements • Capture messages exchanged between test participants • Shall be neutral : Non destructive message capture • Transmit captured messages to the Test Engine for further processing (EVS) • Provide information about sender and recipient when available Projet IHE-Dev Inria Rennes

  9. Proxy Design Test Engine Proxy SUT1 Port 2200 9201 SUT2 Port 104, 2000 9202 SUTa 9203 9204 SIMU1 Port 104 9205 SIMU2 Port 2004

  10. Design • Need to open a port for each responder • Transaction initiator may not know the responder real port • Proxy knows the responder based on the port used • Useful to provide more information that port and ip • Responder port may be mapped with more that one port on the proxy • Solution to isolate messages in the context of a test

  11. SUT1 participating to 2 tests Proxy Test Engine 9201 9202 SUT1 Port 2200 SUTa 9203 9204 9205 SUTb

  12. SUT1 participating to 2 tests Proxy Test Engine SUT1 Actor A and Actor B share the same port 9201 9202 SUTa 9203 9204 9205 SUTb Proxy maps an individual port for each config

  13. Proxy Configuration Proxy Simulator 1 Test Engine Simulator 2 Control System SUT1 SUT2 SUT3

  14. 1 2 3 mirth_input 5 7 4 6 hl7_message_validation Proxy Environment Overview SUT1 Proxy SUT2 Daemon EVS

  15. Proxy : First Experience • Proxy developed for the Oxford C.A.T • Capture of HL7 V2 messages only • Used under real conditions in Oxford • Messages transmitted to Kudu for call to EVS • NIST EVS • INRIA EVS • Usage of the proxy not required but recommended • Message captured and validation results available to participants through Kudu. Projet IHE-Dev Inria Rennes

  16. Proxy • Concept validated • Enable gathering of sample messages for validation of the EVS services • Improvements following Oxford C.A.T. • Capture of ACK messages • Extension to other protocols • XDS Messages • HL7 V3 • Dicom (more complex) Projet IHE-Dev Inria Rennes

  17. External Validation Services EVS

  18. Gazelle Architecture Gazelle Control System Database External Validation Services External Validation Services Gazelle Actor (Simulators) Configuration Info External Validation Services Gazelle Test Engine Gazelle Actor (Simulators) External Validation Services Control Gazelle Actor (Simulators) Gazelle Actor (Simulators) Feedback Gazelle Actor (Simulators) System Under Test System Under Test System Under Test System Under Test Tests Scenario Proxy Network Projet IHE-Dev Inria Rennes

  19. Specification Requirement • Use of Webservices • Definition of the API • Arguments, methods • Definition of XSD and XSL for arguments • Choice of MTOM for the transport of large objects like Dicom Projet IHE-Dev Inria Rennes

  20. EVS • Dicom : • DVTK based • Dicom3tools based • HL7 : • NIST • INRIA • IHE-J ? • CDA • NIST publish Schematron Projet IHE-Dev Inria Rennes

  21. HL7 EVS • 2 EVS available for the moment • NIST • INRIA • Validation based on HL7 Message Profiles • More than 140 Message profiles defined for exisiting IHE transactions • Profiles available from Kudu TF section while waiting for Gazelle Message profile repository Projet IHE-Dev Inria Rennes

  22. Test Engine

  23. System Under Test EVS EVS EVS EVS Proxy Simulator Simulator System Under Test System Under Test Simulator TF Gazelle Database EVS Mgr Test Reports Logging Test Case Test Reports Test Case Test Reports Test Case Proxy Mgr Test Engine Projet IHE-Dev Inria Rennes

  24. Test Engine • Mock up • TF -> ebXML-BP -> BPEL -> gestion des différents composants Projet IHE-Dev Inria Rennes

  25. Product Registry • Application Web • Objectifs : recherche de produits qui implémentent des profils d’intégration IHE • Sous composant de gazelle utilisant un sous ensemble des modules de gazelle • Permet de tester les choix, le modèle • Développé à Rennes Projet IHE-Dev Inria Rennes

  26. Gazelle Registration • Se base sur l’expérience du Product Registry • Portage de la partie enregistrement pour le connect-a-thon dans Gazelle • Doit être fonctionnel pour l’été (C.A.T NA) • Réalisé à Saint Louis et Rennes Projet IHE-Dev Inria Rennes

  27. Project Management Mgt Tools

  28. Gazelle Project Management • Forge for source management • Use of

More Related