We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byRiley Jerrett
Modified about 1 year ago
Automated Test Design ™ © 2011 Conformiq, Inc. CONFORMIQ DESIGNER On ES v1.2.1 Stephan Schulz MBT Working Meeting/MTS#56, Göttingen
Automated Test Design ™ © 2011 Conformiq, Inc. Status ES DSLs in ETSI test language specification? Test selection standardization Outline
Automated Test Design ™ © 2011 Conformiq, Inc. Work finished early 2011 – published by summer Comments received after finalization –Formalization of concepts (in UML diagram) –Annex for flowchart/activity based modeling –“weak point is missing relation of modeling to testing” –Section on modeling from system vs test perspective –“Missing terms” –Missing modeling/coverage of specific test data Status ES
Automated Test Design ™ © 2011 Conformiq, Inc. After years of ”unification” a clear & strong trend in industry to specialization in (modeling) languages, i.e., DSLs –So far deployments mainly in MDD UML, TTCN-3, etc – one size fits all? –One size is how many pages of standard? –One language ?= one compiler –XMI ? A(nother) domain specific modeling hype ? –”Everything is a domain specific language” -> what is a ”domain” –Presentation format vs actual language –Strong (Eclipse) open source initiative ”xtext” Test language specification and DSLs
Automated Test Design ™ © 2011 Conformiq, Inc. What is a Domain Specific Modeling? Modeling with a Domain Specific Modeling Language What is a Domain Specific Modeling Language (DSML)? –A formal language defined on a custom, limited set of domain specific concepts, symbols, and rules in a so called meta model –Attempts to achieve a higher level of abstraction than a general purpose language like, e.g., UML Conceptual foundation dating back to the 80s (ISO ) –Later on popularized in 90s by OMG as “Meta Object Facility” (MOF)
Automated Test Design ™ © 2011 Conformiq, Inc. [Example] Anatomy of a DSML or Meta-Model Concepts [Symbol] s Generators Rules
Automated Test Design ™ © 2011 Conformiq, Inc. A Layered Definition of ETSI Testing DSLs? [based on Oligschläger, LACTOSE 2012] A DSML definition in multiple levels A new level can add new concepts, properties, relationships etc A new level can refine or restrict already existing concepts, properties, relationships, etc Application Domain Generic Testing SpecificTest Description Specific System Generic System System Operation Specific System Operation input, entity test step initial state SIP UA
Automated Test Design ™ © 2011 Conformiq, Inc. Why DSML(s) in Standardization? Not a new idea in context of TTCN-3 A fast way to nice & free text editors available for anybody (via xtext) –One of the challenges of the ExTRA aka TPLan A nice way to formalize dependencies and ensure consistency between different abstraction levels –ExTRA -> System operation or TDL -> TTCN-3 ? Allow space for tool proprietary presentation formats and even refinements, and extensions –At same time enables enforcing ”tool independent single language” for use in standardization
Automated Test Design ™ © 2011 Conformiq, Inc. Open Issues xtext as common denominator? In ES or rather separate standard?
Automated Test Design ™ © 2011 Conformiq, Inc. About Test Selection in ES test generation: automatic derivation of abstract test cases in one or more different formats from a model based on user defined test selection criteria test selection: process or the result of choosing a subset of tests during test generation from a larger or infinite set of tests which can be derived from a model test selection criterion: property that is satisfied by a set of test cases generated from a model
Automated Test Design ™ © 2011 Conformiq, Inc. About Test Selection in ES Section 4: ”The model is then instrumented for the purpose of test generation by adding or selecting test selection criteria, i.e., coverage goals or test purposes specifying what is to be covered, and heuristics specifying how these goals are to be covered. Test selection is necessary since from every non-trivial model, an infinite or huge amount of tests can be derived. A model-based testing tool then automatically generates an abstract test suite that complies with these criteria.” ”NOTE: The specification of test selection criteria is beyond the scope of the present document.”
Automated Test Design ™ © 2011 Conformiq, Inc. (Part of ) An Earlier Attempt Instrumenting the model for test selection A model of system interface and system behaviour provides the basis for model-based testing. In order to control the generation of a test suite from a model, an engineer will need to provide additional information steering the test selection process. In this section, general concepts for test selection are defined. While these concepts are not necessarily part of a modelling notation itself, they are tightly connected to it, and in some instances are models themselves which relate to the behavioural model via model composition. –Coverage In model-based testing, coverage is defined in terms of the elements of the model. Coverage goals can be used to either prune the generation of the model graph from the model, or to steer the test generation process from the model graph. There is a variety of coverage criteria available. In this standard, only very basic coverage criteria are mentioned; many tools will provide more than those. 1.Test selection instrumentation shall provide a way to define coverage goals in terms of model requirements capture. 2.Test selection instrumentation shall provide one or more ways to define coverage goals in terms of the structure of the model, i.e. rule coverage, branch coverage, arc coverage, parameter range coverage, etc. We need more here!
Automated Test Design ™ © 2011 Conformiq, Inc. Next steps Section Test Selection and Test Suite Coverage? –Concepts & terminology/dictionary for use in context of MBT Revise notion of a state? –What is a test in the context of a model Effectively are the same quality – means to compare –Test selection Paramerization Test case properties like redundancy, priority/cost, differences in general –Test Suite Coverage Something may be measurable Type of coverage: Loop, definition coverage once vs n-times, ”full coverage” Criteria/types incl data and combinations thereof Reachability vs trace/pattern/test purpose (data at certain point) Use model vs specification vs implementation vs usage coverage
Agent Based Software Development Michael Luck, Ronald Ashri and Mark dInverno Chapter 4: Methodologies and Modeling Languages.
Software Engineering Model Driven Architecture Software Engineering 2011 Department of Computer Science Ben-Gurion university Based on the book: MDA Explained:
Chapter - 5 Understanding Requirements Unit II. Introduction Definition : “The broad spectrum of tasks and techniques that lead to an understanding of.
Software Reuse and Component-Based Software Engineering CIS 376 Bruce R. Maxim UM-Dearborn.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Chapter 5 Software Requirements.
Fraunhofer FOKUS Competence Center MOTION FOKUS VIEW ON MODEL-BASED TEST DESCRIPTION LANGUAGES (TDLS) Alain-G. Vouffo Feudjio.
The Validation Planning Process The EUROCONTROL Validation Planning Process A brief presentation on the outcome of TRS139/04 Presentation Prepared by:
Chapter 17 Component-based software engineering Lecture 1 1Chapter 17 Software reuse.
Requirements (selected from Ian Sommerville slides for “Software Engineering”)
The Model-Driven Semantic Web Emerging Technologies & Implementation Strategies Elisa Kendall Sandpiper Software September 8, 2005.
HL7 Templates A means to Manage Complexity. Objectives What is an HL7 Template? What types of constraints can HL7 Templates define? What types of HL7.
Overview of the ANSI/ISA S88.01 Batch Control Standard © 1996.
Day 2: Hands-on UML Using UML to put MITA to work to solve the immediate process improvement needs of states.
Kathy Reed June 4, 2013 IIBA Austin CBAP Study Guide for the Business Analyst Body of Knowledge (BABOK) Version 2.0.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps Unit - II.
Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of an.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Topics covered l Functional and non-functional requirements l User requirements.
Documenting Software Architectures These notes are my personal view of the concepts presented on Duran-Limons paper: Documenting Software Architectures:
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
An Introduction to Object Modeling An Introduction to Object Modeling The approach of using object modeling during systems analysis and design is called.
16 August Trends in Practical Deployment of HL7 Standards: supporting regional electronic healthcare records Mark Shafarman Past Chair HL7 with additional.
1 Lecture #6 MBASE Integration Framework Copyright 2000 by USC and the Center for Software Engineering, all rights reserved.
Copyright 1999, 2003 G.v. Bochmann CN-FM ch.2 1 Course Notes on Formal Methods for the Development of Distributed Real-Time Applications Gregor v. Bochmann.
Ch-10 Configuration Management. Introduction A software project produces a number of items during its execution including various documents, manuals,
Author: Graeme C. Simsion and Graham C. Witt Chapter 5 Attributes and Columns.
Introduction to Java 2 Programming Lecture 1 Java, Principles of OO, UML.
Software Process Modeling with UML and SPEM Chris Armstrong Armstrong Process Group
Components Alexey Golubev, What is a component? What is a component? The father of components? The father of components? Components and their.
Three-Step Database Design. Database applications are modeled using a three-step design process Conceptual-datatypes, relationships and constraints(ER.
© 2006 Open Grid Forum GridRPC Interoperability Test Response to comments Yusuke Tanimura.
© 2016 SlidePlayer.com Inc. All rights reserved.