ETSI TR 103 119-2018 Methods for Testing and Specification (MTS) The Test Description Language (TDL) Reference Implementation (V1 1 1).pdf

1、 ETSI TR 103 119 V1.1.1 (2018-02) Methods for Testing and Specification (MTS); The Test Description Language (TDL); Reference Implementation TECHNICAL REPORT ETSI ETSI TR 103 119 V1.1.1 (2018-02) 2 Reference DTR/MTS-103119REFV1.1.1 Keywords MBT ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Ce

2、dex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document

3、may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in

4、 print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status

5、of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be r

6、eproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restri

7、ction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Par

8、tners. oneM2M logo is protected for the benefit of its Members. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 103 119 V1.1.1 (2018-02) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 No

9、rmative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Basic Principles 7g34.1 Introduction 7g34.2 Implementation Scope 7g34.3 Document Structure 8g35 Graphical Representation Viewer 8g35.1 Scope and Requirements 8g35.2

10、Architecture and Technology Foundation 9g35.2.1 Diagram Viewer 9g35.2.2 Structured Test Objective Representation . 10g35.3 Implemented Facilities . 11g35.3.1 Creating Models 11g35.3.2 Viewing Models 15g35.3.3 Exporting Structured Test Objectives . 23g35.3.4 Validating Models 25g35.4 Usage Instructio

11、ns 26g35.4.1 Development Environment . 26g35.4.2 End-user Instructions 27g36 UML Profile Editor 28g36.1 Architecture and Technology Foundation 28g36.2 Implemented Facilities . 28g36.2.1 Applying the Profile 28g36.2.2 Hints for the Transforming UP4TDL Models into TDL Models 29g36.2.3 Editing models w

12、ith the Model Explorer 30g36.2.4 Editing models with TDL-specific properties from the TDL property view . 30g36.2.5 Editing models with TDL-specific diagrams 30g3Annex A (informative): Technical Realization of the Reference Implementation 35g3History 36g3ETSI ETSI TR 103 119 V1.1.1 (2018-02) 4 Intel

13、lectual Property Rights Essential patents IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellec

14、tual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, includin

15、g IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trad

16、emarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present docum

17、ent does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). NOTE: EclipseTM, XtextTM, SiriusTM, EMFTM, PapyrusTM,

18、 GMFTM, EpsilonTM, EVLTMare the trade names of a product supplied by the Eclipse Foundation. OMG, XMITM, UMLTM, OCLTM, MOFTMare the trade names of a product supplied by Object Management Group. This information is given for the convenience of users of the present document and does not constitute an

19、endorsement by ETSI of the product named. The present document is complementary to the multi-part deliverable covering the Test Description Language as identified below: ETSI ES 203 119-1: “Abstract Syntax and Associated Semantics“; ETSI ES 203 119-2: “Graphical Syntax“; ETSI ES 203 119-3: “Exchange

20、 Format“; ETSI ES 203 119-4: “Structured Test Objective Specification (Extension)“. Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal fo

21、rms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 103 119 V1.1.1 (2018-02) 5 1 Scope The present document summarizes technical aspects related to the reference implementation of TDL. It describes both t

22、he implementation details needed for further development and integration of the tools as well as gives usage instructions for end users. Following tools and components are covered in the present document: implementation of the TDL meta-model; viewer for the graphical representation format of TDL; va

23、rious TDL model editors; facilities for checking the semantic validity of models according to the constraints specified in the TDL meta-model; implementation of the UML profile for TDL; and editor supporting the creation and manipulation of UML models applying the UML profile for TDL. 2 References 2

24、.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For

25、 non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary f

26、or the application of the present document but they assist the user with regard to a particular subject area. i.1 Eclipse FoundationTM: Eclipse IDE Website (last visited 30.03.2016). NOTE: Available at https:/eclipse.org. i.2 Eclipse FoundationTM: Eclipse XtextTMWebsite (last visited 30.03.2016). NO

27、TE: Available at https:/eclipse.org/Xtext/index.html. i.3 Eclipse FoundationTM: Eclipse SiriusTMWebsite (last visited 30.03.2016). NOTE: Available at http:/www.eclipse.org/sirius/index.html. i.4 Eclipse FoundationTM: Eclipse Modeling Framework (EMFTM) Website (last visited 30.03.2016). NOTE: Availab

28、le at http:/www.eclipse.org/modeling/emf/. i.5 Eclipse FoundationTM: Eclipse PapyrusTMModeling Environment Website (last visited 30.03.2016). NOTE: Available at https:/www.eclipse.org/papyrus/. ETSI ETSI TR 103 119 V1.1.1 (2018-02) 6 i.6 Eclipse FoundationTM: UMLTMProfiles Repository Website (last v

29、isited 30.03.2016). NOTE: Available at https:/projects.eclipse.org/projects/modeling.upr. i.7 Eclipse FoundationTM: Graphical Modeling Framework (GMFTM) Website (last visited 30.03.2016). NOTE: Available at http:/www.eclipse.org/modeling/gmp/. i.8 “Object Constraint LanguageTM (OMG OCLTM), Version 2

30、.4“, formal/2014-02-03. NOTE: Available at http:/www.omg.org/spec/OCL/2.4/. i.9 Eclipse FoundationTM: Eclipse OCLTMWebsite (last visited 30.03.2016). NOTE: Available at https:/projects.eclipse.org/projects/modeling.mdt.ocl. i.10 Plutext Pty Ltd: Docx4j Website (last visited 30.03.2016). NOTE: Availa

31、ble at http:/www.docx4java.org/trac/docx4j. i.11 “OMG XMLTMMetadata Interchange (XMITM) Specification“, Version 2.4.2, formal/ 2014-04-04. NOTE: Available at http:/www.omg.org/spec/MOF/2.4.2/. i.12 Eclipse FoundationTM: EpsilonTMValidation Language (EVLTM) Website (last visited 30.03.2016). NOTE: Av

32、ailable at http:/www.eclipse.org/epsilon/doc/evl/. i.13 ETSI ES 203 119-1 (V1.3.1): “Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 1: Abstract Syntax and Associated Semantics“. i.14 ETSI ES 203 119-2 (V1.2.1): “Methods for Testing and Specification (MTS); The

33、 Test Description Language (TDL); Part 2: Graphical Syntax“. i.15 ETSI ES 203 119-3 (V1.2.1): “Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 3: Exchange Format“. i.16 ETSI ES 203 119-4 (V1.2.1): “Methods for Testing and Specification (MTS); The Test Descripti

34、on Language (TDL); Part 4: Structured Test Objective Specification (Extension)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: abstract syntax: graph structure representing a TDL specification in an independent fo

35、rm of any particular encoding concrete syntax: particular representation of a TDL specification, encoded in a textual, graphical, tabular or any other format suitable for the users of this language meta-model: modelling elements representing the abstract syntax of a language system under test (SUT):

36、 role of a component within a test configuration whose behaviour is validated when executing a test description TDL model: instance of the TDL meta-model TDL specification: representation of a TDL model given in a concrete syntax ETSI ETSI TR 103 119 V1.1.1 (2018-02) 7 3.2 Abbreviations For the purp

37、oses of the present document, the following abbreviations apply: API Application Programming Interface EBNF Extended Backus-Naur Form EMF Eclipse Modelling Framework EVL Epsilon Validation Language GMF Graphical Modelling Framework MBT Model-Based Testing MOF Meta-Object Facility OCL Object Constrai

38、nt Language OMG Object Management Group SUT System Under Test TDL Test Description Language UML Unified Modelling Language URI Unified Resource Identifier XMI XML Metadata Interchange XML eXtensible Markup Language4 Basic Principles 4.1 Introduction To accelerate the adoption of TDL, a reference imp

39、lementation of TDL is provided in order to lower the barrier to entry for both users and tool vendors in getting started with using TDL. The reference implementation comprises graphical and textual editors, as well as validation facilities. In addition, the UML profile for TDL and supporting editing

40、 facilities are implemented in order to enable application of TDL in UML-based working environments and model-based testing approaches. 4.2 Implementation Scope The implementation scope includes a graphical viewer according to ETSI ES 203 119-2 i.14 based on the Eclipse platform i.1 and related tech

41、nologies, covering essential constructs related to test configurations and test behaviour specification. For creating and manipulating models, a textual editor for ETSI ES 203 119-1 i.13, annex B is implemented based on the Eclipse platform and related technologies. The applicability of general purp

42、ose model editing facilities provided by the Eclipse platform and related technologies is discussed. For tools that need to import and export TDL models according to ETSI ES 203 119-3 i.15, corresponding facilities are implemented based on the Eclipse platform and related technologies. These facilit

43、ies can be used to transform textual representations based on ETSI ES 203 119-1 i.13 into XMI i.11 serializations according to ETSI ES 203 119-3 i.15 and can be integrated in custom tooling that builds on the Eclipse platform. An implementation of ETSI ES 203 119-4 i.16 includes a dedicated textual

44、editor for structured test objectives, which can be integrated in the textual editor for TDL. The implementation also includes facilities for exporting structured test objectives to Word documents using customisable tabular templates. An implementation of the UML profile for TDL includes a specifica

45、tion of the TDL UML profile abstract syntax according to the mapping from the TDL meta-model to TDL stereotypes and UML meta-classes in ETSI ES 203 119-1 i.13, annex C. It is integrated with the open source UML modelling environment Eclipse Papyrus i.5 as an open TDL UML profile reference implementa

46、tion platform. It will be published on the open source “Eclipse UML Profiles Repository“ project i.6. ETSI ETSI TR 103 119 V1.1.1 (2018-02) 8 Figure 4.2.1: TDL tool infrastructure An overview of the context of the reference implementation is shown in Figure 4.2.1. The TDL exchange format specified i

47、n ETSI ES 203 119-3 i.15 serves as a bridge between the different tool components. Textual editors enable the creation and manipulation of TDL models. The graphical viewer is used to visualize TDL models as diagrams. Documentation generation, in particular for structured test objectives, can be plug

48、ged in to produce Word documents for presenting parts of a TDL model in a format suitable for standardization documents. The complete implementation will be published on an open-source portal serving as a central hub for the TDL community. 4.3 Document Structure The present document contains two mai

49、n technical clauses focusing on relevant technical details. The Graphical Representation Viewer implementing ETSI ES 203 119-2 i.14, as well as related facilities implementing ETSI ES 203 119-1 i.13, ETSI ES 203 119-3 i.15 and ETSI ES 203 119-4 i.16 are described in clause 5. The UML Profile Editor implementing annex C of ETSI ES 203 119-1 i.13 is described in clause 6. 5 Graphical Representation Viewer 5.1 Scope and Requirements TDL graphical viewer implementation has two major re