Introducing MBT to Standardization. ETSI All rights reserved

Similar documents
THE ETSI TEST DESCRIPTION LANGUAGE (TDL)

A scenario-based test approach for testing reactive concurrent systems

TDL. bridging the gap between specifications and testing. Dr. Gusztáv Adamis Dr. GyÖrgy réthy Ericsson Hungary Test Solutions and Competence Center

STF 476: TDL Phase 2. Status Report. ETSI All rights reserved

STF 492: TDL Phase 3. Status Report. ETSI All rights reserved

Automated Test Design with TTCN-3

DO WE NEED TEST SPECIFICATION LANGUAGES?!

TESTING OF IOT APPLICATIONS AND INFRASTRUCTURES

IOT-TESTWARE AN ECLIPSE PROJECT

PragmaDev. change request. Emmanuel Gaudin. PragmaDev ITU-T SG17 change request Grimstad June 24,

TTCN (Testing and Test Control Notation) A standard test specification and implementation language. Contents

Multi-site testing strategy using TTCN-3

Introduction to Dependable Systems: Meta-modeling and modeldriven

On the Standardization of Conformance Tests for Communicating Systems. State of the Art and Future Trends. Prof. Dr.

FOUR INDEPENDENT TOOLS TO MANAGE COMPLEXITY INHERENT TO DEVELOPING STATE OF THE ART SYSTEMS. DEVELOPER SPECIFIER TESTER

APPLYING TDL IN PRACTICE

V&V: Model-based testing

ETSI ES V1.1.1 ( )

Automated generation of TTCN-3 test scripts for SIP-based calls

ETSI All rights reserved

AN INTRODUCTION TO TTCN-3. Axel Rennoch TestingStage, Kiev, April 14, 2018

STF 492: TDL Phase 3. Status Report. ETSI All rights reserved

TEST AUTOMATION FOR THE IOT: IOT-TESTWARE. Axel Rennoch, IoTbarcamp, Munich, October 5th, 2017

Technical Report Intelligent Transport Systems (ITS); Testing; Part 5: IPv6 over GeoNetworking validation report

The TINA Conformance Testing Framework. TINA Conformance Testing Framework. Ina Schieferdecker, Mang Li GMD FOKUS

Ensuring Interoperability with Automated Interoperability Testing

Joint Agile Delivery Phase 3

ETSI Experiences in Testing and Interoperability

Future Directions for SysML v2 INCOSE IW MBSE Workshop January 28, 2017

ETSI ETR 346 TECHNICAL December 1996 REPORT

Start Up Benoît Langlois / Thales Global Services Eclipse (EMFT) EGF 2011 by Thales; made available under the EPL v1.

Different levels of Interoperability

Part I: Preliminaries 24

ETSI CTI INTRODUCTION

Software. Test. Architecture. Dr Sigrid Eldh. Ericsson AB Stockholm, Sweden. Public Ericsson AB Page 1

Introduction to EGF. Benoît Langlois / Thales Global Services.

Harmonizing System Development and Test Development with MDA

Java-based test system development with open source components

Metamodeling. Janos Sztipanovits ISIS, Vanderbilt University

Automatic test generation based on functional coverage

ETSI SPECIFICATION Methods for Testing and Specification (MTS); The Test Description Language (TDL)

Proactive Shift Left (left, left, left), a practical approach. Szilard Szell, Test Coach, NOKIA 15th November, 2017, Budapest

Model-Based Testing. The Next Step in Test Automation!? Jan Tretmans SUT. model. TorXakis. SUMBAT: SUpersizing. Model.

From Models to Components. Rapid Service Creation with

An overview on the. version 3 (TTCN-3)

Test Automation. 20 December 2017

From Scenarios to Test Implementations via Promela

Designing a System Engineering Environment in a structured way

IMS networks PSTN/ISDN simulation services conformance testing using ETSI standardized test suites and commercial TTCN-3 test tools

Introduction to OpenArchitectureWare

Alcatel-Lucent Enterprise Model Based Testing applied to Video Testing. Michel SUHR ETSI MBT User Conference Berlin October

From Manual Testing to Intelligent Test Automation Presented by Stephan Schulz

Developing Web-Based Applications Using Model Driven Architecture and Domain Specific Languages

ETSI CTI INTRODUCTION

Papyrus: Advent of an Open Source IME at Eclipse (Redux)

SECURITY TESTING USING MODELS AND TEST PATTERNS. Presented by [Bruno Legeard, Elizabeta Fourneret]

A UML 2 Profile for Variability Models and their Dependency to Business Processes

Introduction to Telelogic Tau SDL Suite

SECURITY TESTING USING MODELS AND TEST PATTERNS. Presented by [Bruno Legeard, Elizabeta Fourneret]

Improving the Quality of Test Suites for Conformance. Tests by Using Message Sequence Charts. Abstract

Software Engineering with Objects and Components Open Issues and Course Summary

From U2TP Models to Executable Tests with TTCN-3 - An Approach to Model Driven Testing -

Chapter 9. Introduction to High-Level Language Programming. INVITATION TO Computer Science

Christian Doppler Laboratory

Homework Identify a suitable project topic that conforms to project requirements

Introduction to MDE and Model Transformation

Towards flexible and efficient model-based testing, utilizing domain-specific modelling

TTCN3 in Wireless Testing Eco Space

SysML Past, Present, and Future. J.D. Baker Sparx Systems Ambassador Sparx Systems Pty Ltd

UPDATE ON NFV PLUGTEST

A Comparison of Ecore and GOPPRR through an Information System Meta Modeling Approach

Model Transformers for Test Generation from System Models

2 nd UML 2 Semantics Symposium: Formal Semantics for UML

Using Model Based Testing for Robustness Tests. Håkan Fredriksson Ericsson AB

Model-Based Testing. Theory Tools Applications SUT. model. Jan Tretmans

Dictionary Driven Exchange Content Assembly Blueprints

ON THE DESIGN OF THE NEW TESTING LANGUAGE TTCN-3

Testing. in A Large scale agile Development Environment

Architectural Design

UML for RTES: develop a UML-based proposal for modelling and analysing of RTES

ETSI ES V3.1.1 ( )

ETSI CTI Plugtests Guide First Draft V ( ) IoT CoAP Plugtests; Paris, France; March 2012

Investigation of System Timing Concerns in Embedded Systems: Tool-based Analysis of AADL Models

ETSI Electronic Signatures and Infrastructures (ESI) TC

Implementation of an Open Source Toolset for CCM Components and Systems Testing *

A Survey on Domain-Specific Languages in Robotics

ETSI CTI Plugtests Guide First Draft V ( ) IoT CoAP Plugtests; Paris, France; March 2012

No Source Code. EEC 521: Software Engineering. Specification-Based Testing. Advantages

ETSI documents published or circulated for vote/comment in May 2018

ETSI TS V1.1.1 ( )

ETSI TC GRID in 5mn!

PAPYRUS TOOL SUPPORT FOR FMI

Architectural Design

ACHIEVING INTEROPERABLE STANDARDS -THE ETSI APPROACH. Anthony Wiles Director Centre for Testing and Interoperability (CTI)

Architecture of models in testing how models of various abstraction levels relate to each other

Technischer Bericht. TRex The Refactoring and Metrics Tool for TTCN-3 Test Specifications

International Telecommunication Testing Centre (ITTC)

Black Box Testing. EEC 521: Software Engineering. Specification-Based Testing. No Source Code. Software Testing

Certified Model-Based Tester

Budapest, October 2016 FUZZ TESTING ITS. Presented by Jürgen Großmann and Dorian Knoblauch. All rights reserved

Transcription:

THE ETSI TEST DESCRIPTION LANGUAGE Introducing MBT to Standardization Presented by Andreas Ulrich, Siemens AG for ICTSS 2017, St. Petersburg, Russia

ABOUT ETSI

About ETSI, MTS, CTI European Telecommunication Standards Institute Develops standards and test specifications for ICT Incl. fixed, mobile, radio, aeronautical, broadcast and internet technologies Ensures and assesses interoperability ETSI s activities in testing Technical Committee on Methods for Testing and Specification (MTS) Responsible for standardizing test and specification methods and languages, guidelines, frameworks Testing and Test Control Notation version 3 (TTCN 3), Test Description Language (TDL) Centre for Testing and Interoperability (CTI) Evaluates test specification technologies Provides hands on support and assistance to TC and projects Interoperability events (Plugtests Service)

TDL SETTING THE CONTEXT

Challenges in Validating Complex Systems Characterization Complex design system of systems Complex behavior real-time, concurrency Complex data big data Intelligent Transport Systems ETSI Adequate validation & testing methods needed Proper modeling techniques Proper test automation Proper fault analysis Support of agile approaches and scenario-based testing

Trend in Software Development Practices Always shorter product release cycles lead to a merge of system development and system operation DevOps Continuous Feedback on Quality Shift Left Shift Right Design Develop Integrate Test Release Deploy Operate Adaptive Test Architecture 1 yr 1 mo 1 wk 1 hr 1 min 1 s 1 dy Release in production frequency

Black Box Testing Using Scenarios Cam Kaner on Scenario Testing, STQE Magazine, Sep./Oct. 2003 The scenario is a story about someone trying to accomplish something with the product under test. Scenarios are useful to connect to documented software requirements, especially requirements modeled with use cases. A scenario test provides an end to end check on a benefit that the program is supposed to deliver. Scenarios are used to systematically test for the correct implementation of requirements in the system.

Model Based Testing Can MBT be used for the generation of conformance test suites? Evaluated tools Microsoft Spec Explorer Conformiq Designer Sepp.med MBTsuite Fraunhofer FOKUS MDTester YES, but Model and test generation tool become parameters of the generated test suite Models and generated tests differ between tools and are not comparable Which model and tool are best?

UML and Testing OMG UML Testing Profile Extension ofuml to support (model based) testing Wide scope modelling notations inherited from UML Might still not capture all needs, further profiles needed, e.g. MARTE Semantic fuzz of UML leads to different interpretations i

The Beginning of TDL Siemens AG, Munich, 14 Dec 2011

TDL LANGUAGE DESIGN

Business Value Support to test design before rushing to test code Better quality of tests Higher productivity in testing Common test concepts Enable development of specialized tools for Test documentation and visualization Generation of executable test code using different strategies Consistency verification and further analysis of test descriptions Harmonize test descriptions coming from different tool sources Support for customized syntax Graphical, Textual, Tabular representation of tests

TDL Usage MBT Workflow Manual Workflow Specification Requirements Level MBT Model TDL-TO Modeling / TP Level Test Generator TDL High-Level Test Cases TTCN-3 or other Execution Language Adapters Low-Level Test Cases Executable Tests Execution Level

Ingredients of a Software Language Abstract Syntax meta-model Concrete Syntax BNF grammar Semantics static and dynamic semantics 15

Standardization in TDL Abstract Syntax Standardized, incl. extension capabilities Concrete Syntax Standardized graphical and exchange syntax Semantics Standardized (formal static, informal dyn. s.)

The TDL Standard Series ETSI ES 203 119 TDL MM, part 1: Abstract Syntax and Associated Semantics TDL GR, part 2: Graphical Syntax TDL XF, part 3: Exchange Format TDL-TO Concrete Syntax TDL- -GR TDL- -XF TDL-MM Abstract t Syntax Othe r synta ax TDL TO, part 4: Structured Test Objective Language TDL UML, part 5: UML Profile for TDL (upcoming) Published documents https://tdl.etsi.org/ and https://www.etsi.org/

TDL is Adjustable by User Concrete syntax may cover only parts of the meta model Mt Meta model dlcan be extended dby a user if need arises User extensions of the meta model can be subjected to further TDL standardization and maintenance Extends Partially implements User-defined TDL concrete syntax TDL meta-model with user extensions 18 ETSI 2013. 1 st User Conference on Advanced Automated Testing, Paris, France, 22 24 Oct 2013

Key Concepts of a TDL Specification Test configuration St Set of interacting ti components in the roles Tester or SUT Test description Represents the expected foreseeable (passing) behavior, i.e. any deviation is a fail Expresses a test in terms of interactions of data exchanged between tester and SUT components Interactions are totally ordered, i.e. they are implicitly synchronized amongcomponents synchronized among components Test data Represented as abstract name tuples 19 ETSI 2013. 1 st User Conference on Advanced Automated Testing, Paris, France, 22 24 Oct 2013

TDL Meta Model Elements Base elements, Concept of time, Test configuration Simple data, Structured data, Data use Test description, Atomic behavior, Combined behavior Test objective language extension Part 4

Example Test Configuration Gate type restricts communication to data of listed types; Component types; Test configuration wiring of components of role Tester / SUT

Example Test Data Data type definitions; Data instance definitions (values); Function declarations

Example Test Description, GR time test configuration being used combined behavior interaction interaction interaction condition time constraint

Example Test Description, TDLan Same test description expressed in textual format

Interactions for Data Exchange An interaction is atomic and instantaneous A common concept for three types of communication Message based communication The data represents a message being bi sent and received via gates Procedure based communication The data represents a (remote) function call being invoked or its return values Shared variable access The data represents a shared variable being read or written

Example TDL Test Objective Language Test objective specification (requirement to be tested) Supportfor Behavior Driven Development Prose syntax Defined in TDL TO, part 4 GIVEN WHEN THEN

TDL IMPLEMENTATION

Typical Efforts in Test Automation Specification (20%) (textual, MSC-like) Scripting (40%) (TTCN-3, Java) Execution (40%) Figures are from an ICT project at Siemens with test team comprising about 24 members. Execution consists of host tests, tests on target HW and regression tests. Additional efforts for test env. / test case build and tool support exist.

Abstract vs Concrete Tests Test Model Test Derivation / Test Specification TDL Test Descriptions Abstract Test Cases The hard part! Test Code Gen. / Test Scripting SUT Concrete Test Cases

TDL Tool Example Generated Textual Editor (EMFText) Interrupting interactions Sequence of blocks Sequence of interactions (Partial) TDL Concrete Syntax 31 ETSI 2013. 1 st User Conference on Advanced Automated Testing, Paris, France, 22 24 Oct 2013

TDL Tool Example Concrete Syntax Variants Domain specific test description languages can be designed by editing the syntax rules to specific needs Interaction ti {ATPStatus(516) t source ts_gatet targett op_gate} Message: ts_gate -> op_gate ATPStatus(516) ;

TDL Tool Example Model to Model Transformation Mapping rules TDL spec State chart

A Scalable TDL Based Tool Architecture Textual Editor (incl. ES 203119-4) UML-based Graph. Editor Report TDL Model Analyzer TDL Test Generator TDL Exchange Format (ES 203119-3) Graphical Editor (ES 203119-2) Graph. Viewer & Doc. Gen. Test Plan Test Code Generator C-code, TTCN-3 Front-end tool Back-end tool Artefact (output)

TDL Open Source Project (TOP) Lower the barrier of entry for both users and tool vendors in getting started with using TDL Graphical and textual editors, validation facilities Visit https://top.etsi.org/ or https://tdl.etsi.org/top

CONCLUSIONS

What Was Achieved? A new, standardized approach for the design of test descriptions and test purposes in TDL Graphical, textual and user defined syntaxes supported Common exchange format TDL harmonizes and eases development of toolsfor scenariobased testing Editors generated fromtdlmeta meta modelmodel Re useable back end tools, e.g. model analyzers code & documentation generators g Eclipse ecosystem enables quick and low cost tool development

Timeline 2011 2013 Very first discussions on TDL Work on TDL design and standardization started 2015 2017 Launch of TDL standards Launch of TDL Open Source Project First applications

TDL @ UCAAT ETSI User Conference on Advanced Automated Testing (UCAAT) https://ucaat.etsi.org/ TDL tutorials and applications

What Comes Next? More applications! Making TDL executable Work on (partial) language mapping from TDL to TTCN 3 has started at ETSI MTS No general solution, but fault model dependent Can the different test generation strategies be classified? Better understanding of abstraction, underspecification, fault detection, i.e. what features can be omitted from a TDL spec such that the outcome is still predictable? Test models in TDL

Acknowledgements The author grateful for contributions from Philip Makedonski (U Göttingen) Martti Käärik (Elvior) Thanks to the TDL Team @ ETSI MTS Michele Carignani, Anthony Wiles (ETSI) Gusztav Adamis, György Rethy (Ericsson) FinnKristoffersen (Cinderella ApS) Marc Florian Wendland (FhG FOKUS) Xavier Zeitoun (CEAList)

Contact Details: Andreas Ulrich Siemens AG, Corporate Technology Munich, Germany andreas.ulrich@siemens.com Благодарю вас за внимание!

Resources TDL website, https://tdl.etsi.org/ Latest standards, documents Bug reporting Mailing list, tdl@list.etsi.org TDL Open Source Project (TOP) TOP is officially launched at UCAAT 2017 The 5 th ETSI User Conference on Advanced Automated Testing, Berlin, 11 13 Oct. 2017 https://top.etsi.org/ p