ETSI ES 203 119-4-2018 Methods for Testing and Specification (MTS) The Test Description Language (TDL) Part 4 Structured Test Objective Specification (Extension) (V1 3 1).pdf

1、 ETSI ES 203 119-4 V1.3.1 (2018-05) Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 4: Structured Test Objective Specification (Extension) ETSI STANDARD ETSI ETSI ES 203 119-4 V1.3.1 (2018-05)2 Reference RES/MTS-203119-4v1.3.1 Keywords language, MBT, methodolog

2、y, testing, TSS 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, including IPR searche

3、s, 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 trademarks and/or

4、 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 document does not

5、constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). The present document is part 4 of a multi-part deliverable. Full deta

6、ils of the entire series can be found in part 1 1. Modal verbs terminology In the present document “shall“, “shall not“, “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 forms for the

7、 expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. Introduction Test purposes play an essential role in test specification processes at ETSI. Currently, TDL treats test purposes, and test objectives in general as informal text

8、without any additional structural constraints. This extension package for TDL refines and formalizes test objective specification within TDL by introducing relevant meta-model concepts and a corresponding syntactical notation, both of which are related to TPLan ETSI ES 202 553 i.1 and TPLan-like not

9、ations already established at ETSI. This enables test purpose specification to enter the modelling world and paves the way for improved tool support and better structured test objectives, as well as additional formal verification and validation facilities down the road by integrating and unifying th

10、e means for the specification of test purposes and test descriptions, while relying on the same underlying meta-model and benefiting from other related technologies built around this meta-model. The present document describes the relevant abstract syntax (meta-model) extensions as well as the corres

11、ponding concrete syntactical notation. ETSI ETSI ES 203 119-4 V1.3.1 (2018-05)6 1 Scope The present document specifies an extension of the Test Description Language (TDL) enabling the specification of structured test objectives. The extension covers the necessary additional constructs in the abstrac

12、t syntax, their semantics, as well as the concrete graphical syntactic notation for the added constructs. In addition textual syntax examples of the TDL Structured Test Objectives extensions as well as BNF rules for a textual syntax for TDL with the Structured Test Objectives extensions are provided

13、. The intended use of the present document is to serve both as a foundation for TDL tools implementing support for the specification of structured test objectives, as well as a reference for end users applying the standardized syntax for the specification of structured test objectives with TDL. NOTE

14、: OMG, UML, OCL and UTP are the trademarks of OMG (Object Management Group). This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of the products named. 2 References 2.1 Normative references References are either specific (iden

15、tified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to

16、be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference. 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 necessary for the applic

17、ation of the present document. 1 ETSI ES 203 119-1 (V1.4.1): “Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 1: Abstract Syntax and Associated Semantics“. 2 ETSI ES 203 119-2 (V1.3.1): “Methods for Testing and Specification (MTS); The Test Description Language

18、 (TDL); Part 2: Graphical Syntax“. 3 ETSI ES 203 119-3 (V1.3.1): “Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 3: Exchange Format“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version

19、number) or non-specific. For specific references, only the cited version applies. For 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 guara

20、ntee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI ES 202 553 (V1.2.1): “Methods for Testing and Specification (MTS); TPLan: A notation for express

21、ing Test Purposes“. i.2 ETSI TS 136 523-1 (V10.2.0): “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol conformance specification (3GPP TS 36.523-1 version 10.2.0 Release 10)“. ETSI ETSI ES 203 119-

22、4 V1.3.1 (2018-05)7 i.3 ETSI TS 186 011-2: “Core Network and Interoperability Testing (INT); IMS NNI Interoperability Test Specifications (3GPP Release 10); Part 2: Test descriptions for IMS NNI Interoperability“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present docume

23、nt, the terms and definitions given in ETSI ES 203 119-1 1 and the following apply: context: set of circumstances related to the occurrence of an event entity: object that may be involved in the occurrence of an event as part of a specific context entity type: alias for additional meta-information t

24、hat may be used to describe one or more entities event: observable phenomenon or state that may occur in a specific context NOTE: Related to a term of the same name defined in ETSI ES 202 553 i.1. event occurrence: description of the occurrence of an event in a specific context event type: alias for

25、 additional meta-information that may be used to describe one or more events 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: BNF Backus-Naur Form EBNF Extended Backus-Naur Form IMS IP Multimedia Subsystem IUT Implementation Under Test OCL Object Constra

26、int Language PICS Protocol Implementation Conformance Statement SUT System Under Test TDL Test Description Language TPLan Test Purpose Notation 4 Basic principles 4.1 Structured Test Objective Specification The present document defines an extension for TDL enabling the specification of structured te

27、st objectives. Rather than rely on external documents or informal text provided by the default test objective specification facilities of TDL, this extension enables users to describe test objectives in a more structured and formalized manner which may enable subsequent generation of test descriptio

28、n skeletons and consistency checking against test descriptions realizing a given test objective. In addition, the structured approach to test objective specification also enables syntactical and semantical consistency checking of the test objectives themselves. The abstract concepts and the concrete

29、 syntax are based on TPLan ETSI ES 202 553 i.1 to a large extent, as they also reflect concepts and practices already established at ETSI. The fundamental concept in the specification of a structured test objectives is the event occurrence which describes the occurrence of an abstract event in a spe

30、cific context, comprising one or more involved entities, an event argument, as well as a time label and/or a time constraint. ETSI ETSI ES 203 119-4 V1.3.1 (2018-05)8 Events and entities referenced in an event occurrence shall be defined in advance as part of a domain description which may then be r

31、eused across all structured test objective specifications in that domain. An entity is an abstract representation of an object involved in an event occurrence that may be realized as a component instance or a gate instance within a test description realizing the structured test objective. An event a

32、rgument may either refer to a data instance for data already defined with the facilities provided by TDL, or, following a more light weight approach, describe data inline without the need to define all data types and instances in advance. Pre-defined data and inline data may be integrated to a certa

33、in degree. Inline data may refer to pre-defined data, but pre-defined data shall not refer to inline data. Event occurrence specifications are organized in the different compartments of a structured test objective, including initial conditions, expected behaviour, and final conditions. Multiple even

34、t occurrences are combined by means of an and or or operand indicating how subsequent event occurrences are related to each other (as a sequence or as alternatives, respectively). Structured test objectives may also include references to PICS which may be used as selection criteria for the concrete

35、realization of the test objectives. The PICS shall be defined in advance as part of the domain description. Multiple PICS references within the same structured test objective are combined by means of an and or or operand indicating how subsequent referenced PICS are related to each other. 4.2 Docume

36、nt Structure The present document defines the structured test objective specification extension for TDL comprising: Meta-model extension describing additional concepts required for the specification of structured test objectives (clause 5). Concrete syntax extension describing corresponding shapes f

37、or the representation of the additional concepts (clause 6). An informative annex with examples in a textual concrete syntax (annex A). An informative annex with production rules for the example textual syntax (annex B). 4.3 Notational Conventions The present document inherits the notational convent

38、ions defined in ETSI ES 203 119-1 1 and ETSI ES 203 119-2 2. The abstract syntax specification and the classifier descriptions follow the notational conventions defined in clause 4.5 of Abstract Syntax and Associated Semantics 1. The concrete syntax notation specification follows the notational conv

39、entions described in clause 4.5 of the Graphical Syntax 2. 4.4 OCL Constraints Requirements In addition to the operations provided by the standard library of OCL and in ETSI ES 203 119-1 1, the formalized constraints for the present document rely on the following additional operations that serve as

40、reusable shortcuts and shall be provided by TDL semantical analyser implementations for the interpretation of the OCL constraints: OclAny getTestObjective (): StructuredTestObjective - applicable on any TDL Element, returns the StructuredTestObjective that contains the construct directly or indirect

41、ly. OclAny contains (object : OclAny): Boolean - applicable on any TDL Element, accepts a TDL Element as parameter object, returns true if the Element contains the object and false otherwise. StructuredTestObjective indexOf (object : OclAny): Integer - applicable on a StructuredTestObjective, accept

42、s a TDL Element as parameter object, returns the position of the object within the flattened list of all Elements directly and indirectly contained within the StructuredTestObjective. The list is flattened according to a depth-first approach. ETSI ETSI ES 203 119-4 V1.3.1 (2018-05)9 4.5 Conformance

43、For an implementation claiming to conform to this extension of the TDL meta-model, all concepts specified in the present document and in ETSI ES 203 119-1 1, as well as the concrete syntax representation specified in the present document shall be implemented consistently with the requirements given

44、in the present document and in ETSI ES 203 119-1 1. The electronic attachment from annex A in ETSI ES 203 119-1 1 may serve as a starting point for a TDL meta-model implementation conforming to the present document and the overall abstract syntax of TDL 1. 5 Meta-Model Extensions 5.1 Overview The st

45、ructured test objective specification is defined within a single package in the TDL meta-model. It relies on several concepts from the Foundation, Data, and Time packages of the TDL meta-model. 5.2 Foundation Abstract Syntax and Classifier Description 5.2.1 Entity Figure 5.1: Structured Test Objecti

46、ve Specification Foundation Concepts Semantics An Entity is a PackageableElement that describes a participant in an EventOccurrence. User defined entities, such as IUT, SUT, Tester, etc. may be referenced by means of an EntityReference within an EventOccurrence as the source and/or target of an Even

47、t referenced in a corresponding EventReference. Whether an Entity corresponds to a ComponentInstance or a GateInstance is not specified in advance. Annotations may be used to provide an indication for the type and role of the Entity. Generalizations PackageableElement Properties There are no propert

48、ies specified. ETSI ETSI ES 203 119-4 V1.3.1 (2018-05)10 Constraints There are no constraints specified. 5.2.2 Event Semantics An Event is a PackageableElement that describes a user defined event or activity that may be referenced in an EventOccurrence. The direction of an Event with respect to the

49、Entity or Entitys referenced in the EventOccurrence depends on the interpretation of the Event, where Annotations may be used to provide additional information as an indication of the intended interpretation. Generalizations PackageableElement Properties There are no properties specified. Constraints There are no constraints specified. 5.2.3 PICS Semantics A PICS is a PackageableElement that may be referenced in StructuredTestObjectives to