1、 ETSI ES 202 785 V1.6.1 (2018-05) Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Behaviour Types ETSI STANDARD ETSI ETSI ES 202 785 V1.6.1 (2018-05) 2 Reference RES/MTS-202785-ed161 Keywords conformance, testing, TTCN-3 ETSI
2、650 Route des Lucioles F-06921 Sophia Antipolis Cedex - 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:/w
3、ww.etsi.org/standards-search The present document 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 diff
4、erence in contents between such versions and/or in 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 ch
5、ange of status. Information on the current status 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/CommiteeSupport
6、Staff.aspx Copyright Notification No part may be reproduced 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 authorizati
7、on of ETSI. The copyright and the foregoing restriction 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 LTETMare trademarks of ETSI registered for the benefi
8、t of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI ES 202 785 V1.6.1 (2018-05) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verb
9、s terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Package conformance and compatibility 7g35 Package concepts for the core language . 8g35.1 Extension to ETSI ES 201
10、 873-1, clause 5 (Basic language elements) 8g35.2 Extension to ETSI ES 201 873-1, clause 6 (Types and values) 9g35.3 Extension to ETSI ES 201 873-1, clause 7 (Expressions) 14g35.4 Extension to ETSI ES 201 873-1, clause 8 (Modules) . 15g35.5 Extension to ETSI ES 201 873-1, clause 10 (Declaring consta
11、nts) 15g35.6 Extension to ETSI ES 201 873-1, clause 11 (Declaring variables) 15g35.7 Extension to ETSI ES 201 873-1, clause 15 (Declaring templates) . 16g35.8 Extension to ETSI ES 201 873-1, clause 16 (Functions, altsteps and test cases) . 16g35.9 Extension to ETSI ES 201 873-1, clause 19 (Basic pro
12、gram statements) 17g35.10 Extension to ETSI ES 201 873-1, clause 20 (Statements and operations for alternative behaviours) 18g35.11 Extension to ETSI ES 201 873-1, clause 21 (Configuration Operations) 18g35.12 Extension to ETSI ES 201 873-1, clause 26 (Module control) 19g35.13 Extension to ETSI ES 2
13、01 873-1, annex A (BNF and static semantics) 20g35.13.0 New keywords and TTCN-3 syntax BNF productions . 20g35.13.1 Changes to ETSI ES 201 873-1, clause A.1.6 (TTCN-3 syntax BNF productions) . 20g36 Package semantics 21g36.1 Replacements . 21g36.2 Activate statement 21g36.3 Replacements in Execute s
14、tatements operational semantics 22g36.3.0 Execute statement . 22g36.3.1 Flow graph segment . 23g36.4 Replacements in Function calls operational semantics 24g36.4.0 Function call . 24g36.4.1 Flow graph segment 26g36.4.2 Flow graph segment . 26g36.5 Start component operation 26g37 TRI extensions for t
15、he package 29g38 TCI extensions for the package 29g38.1 Extensions to ETSI ES 201 873-6, clause 7 (TTCN-3 control interface and operations). 29g38.2 Extensions to ETSI ES 201 873-6, clause 8 (Java language mapping) 30g38.3 Extensions to ETSI ES 201 873-6, clause 9 (ANSI C language mapping) 31g38.4 E
16、xtensions to ETSI ES 201 873-6, clause 10 (C+ language mapping) 31g38.5 Extensions to ETSI ES 201 873-6, clause 11 (W3C XML mapping) 33g39 Extensions to TTCN-3 documentation comment specification for the package 43g39.1 Extensions to ETSI ES 201 873-10, annex A (Where Tags can be used) 43g3History 4
17、5g3ETSI ETSI ES 202 785 V1.6.1 (2018-05) 4 Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-membe
18、rs, and can be found in ETSI SR 000 314: “Intellectual 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
19、to the ETSI IPR Policy, no investigation, including 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
20、. Trademarks The present document may include trademarks 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
21、. Mention of those trademarks in the present document does not 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 us
22、e of underline (additional text) highlights the differences between base document and extended documents. The present document relates to the multi-part standard ETSI ES 201 873 covering the Testing and Test Control Notation version 3, as identified below: Part 1: “TTCN-3 Core Language“; Part 2: “TT
23、CN-3 Tabular presentation Format (TFT)“; Part 3: “TTCN-3 Graphical presentation Format (GFT)“; Part 4: “TTCN-3 Operational Semantics“; Part 5: “TTCN-3 Runtime Interface (TRI)“; Part 6: “TTCN-3 Control Interface (TCI)“; Part 7: “Using ASN.1 with TTCN-3“; Part 8: “The IDL to TTCN-3 Mapping“; Part 9: “
24、Using XML schema with TTCN-3“; Part 10: “TTCN-3 Documentation Comment Specification“; Part 11: “Using JSON with TTCN-3“; Part 12: “Using WSDL with TTCN-3“. NOTE: Part 2 of the multi-part deliverable ETSI ES 201 873 is in status “historical“ and is not maintained. ETSI ETSI ES 202 785 V1.6.1 (2018-05
25、) 5 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 expression of provisions). “must“ and “must no
26、t“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI ES 202 785 V1.6.1 (2018-05) 6 1 Scope The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communicat
27、ion ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including
28、interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 c
29、ore language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines types for behaviour definitions in TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core lang
30、uage with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or ver
31、sion 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 be publicly available in the expected location might be fo
32、und 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 application of the present document. 1 ETSI ES 201 873-1: “Meth
33、ods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language“. 2 ETSI ES 201 873-4: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 4: TTCN-3 Operational Semantics“. 3 ETSI ES 201 873-5: “Me
34、thods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)“. 4 ETSI ES 201 873-6: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)“. 5 ISO/IEC
35、9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework; Part 1: General concepts“. 6 ETSI ES 202 784: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Advanced Parameteri
36、zation“. 7 ETSI ES 201 873-10: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification“. ETSI ETSI ES 202 785 V1.6.1 (2018-05) 7 2.2 Informative references References are either specific (identified by date of
37、 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. NOTE: While any hyperlinks included in this clause were valid
38、 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 the user with regard to a particular subject area. i.1 ETSI ES 201 873-7: “Methods for Testing and Specificati
39、on (MTS); The Testing and Test Control Notation version 3; Part 7: Using ASN.1 with TTCN-3“. i.2 ETSI ES 201 873-8: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 8: The IDL to TTCN-3 Mapping“. i.3 ETSI ES 201 873-9: “Methods for Testing and Speci
40、fication (MTS); The Testing and Test Control Notation version 3; Part 9: Using XML schema with TTCN-3“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI ES 201 873-1 1, ETSI ES 201 873-4 2, ETSI ES 201 873-5 3, ETSI ES
41、201 873-6 4, ISO/IEC 9646-1 5 and the following apply: behaviour definition: definition of an altstep, function, or testcase that can be called explicitly NOTE: A control part is not considered a behaviour definition, because it cannot be called explicitly. behaviour type: type of behaviour definiti
42、ons NOTE: Behaviour types are of kind altstep, function, or testcase. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI ES 201 873-1 1, ETSI ES 201 873-4 2, ETSI ES 201 873-5 3, ETSI ES 201 873-6 4 and ISO/IEC 9646-1 5 apply. 4 Package conformance and compat
43、ibility The package presented in the present document is identified by the package tag: “TTCN-3:2009 Behaviour Types“ - to be used with modules complying with the present document For an implementation claiming to conform to this package version, all features specified in the present document shall
44、be implemented consistently with the requirements given in the present document; in ETSI ES 201 873-1 1 and ETSI ES 201 873-4 2. All features marked AdvancedParameterization have to be implemented only in case that this package is used together with the Advanced Parameterization package 6. The packa
45、ge presented in the present document is compatible with: ETSI ES 201 873-1 1 (V4.5.1). ETSI ES 201 873-4 2 (V4.4.1). ETSI ES 201 873-5 3 (V4.5.1). ETSI ETSI ES 202 785 V1.6.1 (2018-05) 8 ETSI ES 201 873-6 4 (V4.5.1). ETSI ES 201 873-7 i.1 (V4.5.1). ETSI ES 201 873-8 i.2 (V4.5.1). ETSI ES 201 873-9 i
46、.3 (V4.5.1). ETSI ES 201 873-10 7 (V4.5.1). If later versions of those parts are available and should be used instead, the compatibility to the package presented in the present document has to be checked individually. The package presented in the present document is also compatible with: ETSI ES 202
47、 784 6 Package Advanced Parameterization (V1.3.1); and can be used together with this package. If later versions of those packages are available and should be used instead, the compatibility to the package presented in the present document has to be checked individually. 5 Package concepts for the c
48、ore language 5.1 Extension to ETSI ES 201 873-1, clause 5 (Basic language elements) Clause 5.4 Parameterization Values of behaviour types can be passed as parameters as indicated in table 2. Table 2: Overview of parameterizable TTCN-3 objects Keyword Allowed kind of Parameterization Allowed form of
49、Parameterization Allowed types in formal parameter lists module Value parameterization Static at start of run-time all basic types, all user-defined types and address type. type (see note) Value parameterization Static at compile-time all basic types, all user-defined types and address type. template Value and template parameterization Dynamic at run-time all basic types, all user-defined types, address type, template, and behaviour types. function Value, template, port and timer paramete
