DO WE NEED TEST SPECIFICATION LANGUAGES?!

Transcription

1 DO WE NEED TEST SPECIFICATION LANGUAGES?! Ina Schieferdecker ICST 2017, Tokyo, March 17, 2017 Please look up my yesterday s proposal for the new version of the UML Testing Profile

2 OUTLINE 1. About me 2. Do we need test specification languages? 3. What is needed in addition to a test specification language? 4. Where should we aim at next? 4 Fraunhofer FOKUS

3 ABOUT ME Scientiest... in applied research Professor in education Member of academy for scientific recommendations President for high-quality software-based systems 5

4 BACKGROUND TELECOMMUNICATION: CONFORMANCE AND INTEROPERABILITY 1. Interoperability Interoperability is the ability of making systems and organizations to work together (interoperate). While the term was initially defined for information technology or systems engineering services to allow for information exchange, [Wikipedia] 2. Conformance Confirmation that a good, service, or conduct meets the requirements of legislation, accepted practices, prescribed rules and regulations, specified standards, or terms of a contract. [Business Dictionary] Interoperability is a precondition for the increasing integration and networking of systems and components. Conformance supports interoperability. 6

5 FUNDAMENTAL INTEROPERABILITY TEST METHOD A dynamic testing method Complements conformance testing Test Case Interpretation Test Logging Test Reporting Test system Test Coordinator QE System Under Test (SUT) EUT Test Driver (QE Side) Test Interface Means of communication Test Interface Test Driver (EUT Side) 1. QE = Qualified Equipment (previously tested) 2. EUT = Equipment under Test (such as gateway, protocol layer, software component) 7

6 ABOUT ME Working on Test Specification Languages for quite some time Message Sequence Charts Testing and Test Control Notation UML Testing Profile 8 Fraunhofer FOKUS

7 LOOKING BACK AND FORWARD Do we need test standardized specification languages test specification? languages? 9 Fraunhofer FOKUS

8 THE WORD WAS IN THE BEGINNING And the word comes with A common understanding A language A concept space, semantics and syntax(es) A mind set A culture A set of methods and processes 10 Fraunhofer FOKUS

9 EVOLUTION OF SOFTWARE ENGINEERING C O M P L E XI T Y C++ Java Smalltalk CCM.Net Java EE object composition paradigm Model-Driven Engineering MOF, ecore Linked Data, RDF SOA REST JSON distributed components paradigm service orchestration paradigm model transformation paradigm C Pascal Modula procedural refinement paradigm FLEXIBILITY 11

10 MODELING LANGUAGES Taken from Alberto Rodrigues da Silva: Model-driven engineering: A survey supported by the unified conceptual model, Computer Languages, Systems & Structures. 43(2015)

11 MBT 1.0 Require ments System model System test Test system 13

12 MBT 2.0 Require ments System model test Test model System test Test system 14

13 MBT 3.0? Require ments System req. test Test req. System model test Test model System test Test system 15

14 TEST SPECIFICATION LANGUAGES Require ments System req. test UML, ReqIF, Test TPLan, TDL req. UML Testing Profile System model test UML, SDL, ML/SL,, XLSX Test UML Testing Profile model TTCN-3 System test Java, C++, Junit, Test CppUnit, Python, system Ruby, TTCN-3 16

15 STANDARDIZED TEST SPECIFICATION LANGUAGES System req. Require ments test UML, ReqIF, Test TPLan, TDL req. UML Testing Profile Tester's mind set System model System test test UML, SDL, ML/SL,, XLSX Test UML Testing Profile model TTCN-3 Java, C++, Junit, Test CppUnit, Python, system Ruby, TTCN-3 Common language 17

16 LOOKING BACK AND FORWARD What is needed in addition to a test specification language? 18 Fraunhofer FOKUS

17 METHODOLOGIES AND AUTOMATION AND TRAINING And the methodologies come with Tools Examples Guidelines Case studies Qualitative / quantitative evaluations Experience reports Best practices Pattern / anti-patterns Process (models) 19 Fraunhofer FOKUS

18 TEST AUTOMATION ENGINEERING Generic Test Automation Architecture Test Automation Engineer Syllabus 20 Fraunhofer FOKUS

19 SOFTWARE TESTING TRAINING 21 Fraunhofer FOKUS

20 CERTIFIED TEST AUTOMATION ENGINEER 22 Fraunhofer FOKUS

21 CERTIFIED MODEL-BASED TESTER 23

22 TOOLING MAKES LANGUAGES AND METHODOLOGIES LIVE They need to be practicable, usable and efficient Within established tool and process landscape Should respect huge amounts of legacy data being (also) models! Reuse the expertise of the people and teams 24 Fraunhofer FOKUS

23 TOOL FRAMEWORK MODELBUS 1. is a model-driven tool integration framework which allows you to build seamlessly integrated tool environments for your development process. 2. connects tools commercial off the shelf or in-house tools 3. helps automating development and quality assurance processes 4. uses SOA principles and well-established standards See 25

24 MODELBUS - GENERAL CONCEPT Requirements Tool Analysis Tool Design Tool Verification Tool Deployment Tool Simulation Tool Management Tool Coding Tool Test Tool Control Tool Orchestration Tool Lifecycle Tools Process Enactment ModelBus Core Services Modeling Services Service Registry Notification Verification Transformation Testing Model Storage Simulation Analysis Traceability Code Generation 26

25 MODELBUS ARCHITECTURE Existing Tool Adapter Tools / Frontend Web Interface Indexing Search Reasoning Model Checking Information gap analysis Testing Common Interface Smart suggestions Simulation Transformation Services Service and Functionality Discovery Workflo w Simulati on Model Checkin g Development Process Code Generati on Transformatio n Intranet Model Repository RDBMS File System Repositories 27

26 SELECTION OF CONNECTED TOOLS Eclipse-based Tools Topcased, Papyrus, ProR, Rational Software Architect Doors Rhapsody Simulink Microsoft Office (Word, Excel) Sparx Enterprise Architect AVL InMotion 28

27 METRINO Model-driven metric definition and computation Challenge Identifying properties and quality of models Definition of metrics for complex models Approach Model-driven handling of quality attributes and properties Definition of Metric Generation rules Usage of OMGs SMM for management of metrics Solution Tool front-end allows the definition and management of metrics definition of thresholds, grouping of metrics Visualization of Metric computation results in tabular way and kiviat graphs 29

28 TRACEINO Tool-independent traceability framework Challenge Linking of development artefacts Definition of individual complex traceability models Approach Model-driven handling of traceability information Based on ModelBus tool integration approach to easily extend existing tools with traceability functionality Solution Definition and utilization of type safe case specific traceability Navigation and quering through trace info Common Look and Feel UI (Web and Desktop) Graphical visualization of traces 30

29 REQUINO Model-driven requirements engineering Challenge Structured Requirements during the whole system development Design Space Exploration Approach Model-driven handling of requirements Graphical refinement of requirements Based on SysML/UML Based on ModelBus (Versioning, Notification, Locking, Fragmentation, etc.) Solution Structured Definition of Requirements Refinement through structural/behavioral diagrams Evaluation of different concepts Common Look and Feel UI (Web and Desktop) 31

30 AND YES We also have our MBT tool 32 Fraunhofer FOKUS

31 LOOKING FORWARD Where should we aim at next? 33 Fraunhofer FOKUS

32 LOOKING FORWARD What are your thoughts? 34 Fraunhofer FOKUS

33 LOOKING FORWARD Where should we aim at next? Automated test framework generation Machine / deep learning in test processes / test automation Data quality assurance Self-awareness and self-adaptation via models Some of which may require language extensions or even new languages 35 Fraunhofer FOKUS

34 ?! 36 Fraunhofer FOKUS

35 CONTACT Fraunhofer-Institut für Offene Kommunikationssysteme FOKUS Kaiserin-Augusta-Allee Berlin, Germany Director Prof. Dr.-Ing. Ina Schieferdecker Tel. +49 (30) Fraunhofer FOKUS