1、 ETSI ES 203 119-4 V1.1.1 (2015-06) 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.1.1 (2015-06)2Reference DES/MTS-203119-4 Keywords language, MBT, methodology, test
2、ing, 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 (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has be
3、en 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. Foreword This ETSI Standard (ES) has been produced by ETSI Technical C
4、ommittee Methods for Testing and Specification (MTS). The present document is part 4 of a multi-part deliverable covering the Test Description Language as identified below: Part 1: “Abstract Syntax and Associated Semantics“; Part 2: “Graphical Syntax“; Part 3: “Exchange Format“; Part 4: “Structured
5、Test Objective Specification (Extension)“. 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 express
6、ion 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 without
7、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 notations a
8、lready 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 the means
9、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 corresponding
10、concrete syntactical notation. ETSI ETSI ES 203 119-4 V1.1.1 (2015-06)61 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 abstract syntax,
11、 their semantics, as well as the concrete syntactical notation for the added constructs. 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
12、 standardized syntax for the specification of structured test objectives with TDL. 2 References 2.1 Normative 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
13、. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this c
14、lause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI ES 203 119-1 (V1.2.1): “Methods for Testing and Specification (MTS); The Test Description Language (TDL);
15、Part 1: Abstract Syntax and Associated Semantics“. 2 ETSI ES 203 119-2 (V1.1.1): “Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 2: Graphical Syntax“. 3 ETSI ES 203 119-3 (V1.1.1): “Methods for Testing and Specification (MTS); The Test Description Language (TD
16、L); Part 3: Exchange Format“. 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 non-specific references, the latest version of the referen
17、ced 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 for the application of the present document but they assist
18、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 expressing 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); Us
19、er Equipment (UE) conformance specification; Part 1: Protocol conformance specification (3GPP TS 36.523-1 version 10.2.0 Release 10)“. 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 fo
20、r IMS NNI Interoperability“. ETSI ETSI ES 203 119-4 V1.1.1 (2015-06)73 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, 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
21、 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 that 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 te
22、rm 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 additional meta-information that may be used to describe one or more events 3.2 Abbreviations For the purposes of the present document, the foll
23、owing abbreviations apply: BNF Backus-Naur Form EBNF Extended Backus-Naur Form IMS IP Multimedia Subsystem IUT Implementation Under Test PICS Protocol Implementation Conformance Statement SUT System Under Test TDL Test Description Language TPLan Test Purpose Notation 4 Basic principles 4.1 Structure
24、d Test Objective Specification The present document defines an extension for TDL enabling the specification of structured test 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 d
25、escribe test objectives in a more structured and formalized manner which can enable subsequent generation of test description skeletons and consistency checking against test descriptions realizing a given test objective. In addition, the structured approach to test objective specification also enabl
26、es syntactical and semantical consistency checking of the test objectives themselves. The abstract concepts and the concrete 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 specif
27、ication of a structured test objectives is the event occurrence which describes the occurrence of an abstract event in a specific context, comprising one or more involved entities, an event argument, as well as a time label and/or a time constraint. Events and entities referenced in an event occurre
28、nce need to be defined in advance as part of a domain description which can then be reused 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 i
29、nstance within a test description realizing the structured test objective. An event argument 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 an
30、d instances in advance. Pre-defined data and inline data can be integrated to a certain degree in that inline data may refer to pre-defined data, but not the other way around. ETSI ETSI ES 203 119-4 V1.1.1 (2015-06)8Event occurrence specifications are organized in the different compartments of a str
31、uctured test objective, including initial conditions, expected behaviour, and final conditions. Multiple event 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
32、test objectives may also include references to PICS which may be used as selection criteria for the concrete realization of the test objectives. The PICS need to be defined in advance as part of the domain description. Multiple PICS references within the same structured test objective are combined b
33、y means of an and or or operand indicating how subsequent referenced PICS are related to each other. 4.2 Document Structure The present document defines the structured test objective specification extension for TDL comprising: Meta-model extension describing additional concepts required for the spec
34、ification of structured test objectives (clause 5). Concrete syntax extension describing corresponding shapes for 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 ex
35、ample textual syntax (annex B). 4.3 Notational Conventions The present document inherits the notational conventions 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 Abs
36、tract Syntax and Associated Semantics 1. The concrete syntax notation specification follows the notational conventions described in clause 4.5 of the Graphical Syntax 2. 4.4 Conformance For an implementation claiming to conform to this extension of TDL meta-model, all concepts specified in the prese
37、nt 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 in the present document and the referenced documents. The electronic attachment from annex A in ETSI ES 203 119-1 1 ca
38、n 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 structured test objective specification is defined within a single package in the TDL meta-model. It relies on several
39、 concepts from the Foundation, Data, and Time packages of the TDL meta-model. 5.2 Foundation Abstra5.2.1 Entity Figure 5.1: Structured TeSemantics An Entity is a PackageableElement that desIUT, SUT, Tester, etc. may be referenced by and/or target of an Event referenced in a corrComponentInstance or
40、a GateInstance is nofor the type and role of the Entity. Generalizations PackageableElement Properties There are no properties specified. Constraints There are no constraints specified. 5.2.2 Event Semantics An Event is a PackageableElement that descEventOccurrence. The direction of an Eventdepends
41、on the interpretation of the Event, windication of the intended interpretation. Generalizations PackageableElement Properties There are no properties specified. Constraints There are no constraints specified. ETSI ETSI ES 203 1199tract Syntax and Classifier Descriest Objective Specification Foundati
42、on Concepescribes a participant in an EventOccurrence. User definey means of an EntityReference within an EventOccurrenorresponding EventReference. Whether an Entity corresn t specified in advance. Annotations may be used to proescribes a user defined event or activity that may be refereen with resp
43、ect to the Entity or Entitys referenced in thehere Annotations may be used to provide additional in19-4 V1.1.1 (2015-06)cription epts fin d entities, such as ce as the source responds a rovide an indication erenced in an th EventOccurrence formation as an 5.2.3 PICS Semantics A PICS is a Packageable
44、Element that may bthe StructuredTestObjective based on featureStructuredTestObjective. Generalizations PackageableElement Properties There are no properties specified. Constraints There are no constraints specified. 5.3 Test Objective Ab5.3.1 StructuredTestObjecFigure 5.2: Semantics A StructuredTest
45、Objective is a refinement offormalize the description of TestObjectives. TestObjective, a StructuredTestObjective inFinalConditions. ETSI ETSI ES 203 11910be referenced in StructuredTestObjectives to indicate seres required for and/or tested with the realization of the Abstract Syntax and Classifier
46、 Desjective Structured Test Objective Concepts t o TestObjective that enables the use of additional consts. In addition to the description and objectiveURI propecludes PICSReferences, InitialConditions, ExpectedB19-4 V1.1.1 (2015-06)e selection criteria for escription nstructs in order to perties in
47、herited from edBehaviour, and ETSI ETSI ES 203 119-4 V1.1.1 (2015-06)11Generalizations TestObjective Properties picsReference : PICSReference * ordered An ordered set of PICSReferences to PICS. initialConditions : InitialConditions 01 Initial conditions description for the StructuredTestObjective. e
48、xpectedBehaviour : ExpectedBehaviour 01 Expected behaviour description for the StructuredTestObjective. finalConditions : FinalConditions 01 Final conditions description for the StructuredTestObjective. Constraints There are no constraints specified. 5.3.2 PICSReference Semantics A PICSReference is
49、an Element that enables the referencing of PICS within a StructuredTestObjective. A Comment with body containing an and or or shall be used as a Boolean operand if there are two or more PICSReferences specified within a StructuredTestObjective, starting with the second PICSReference to indicate how the referenced PICS shall be interpreted with regard to the other referenced PICS within the same Structur
