1、 ETSI ES 202 553 V1.2.1 (2009-06)ETSI Standard Methods for Testing and Specification (MTS);TPLan: A notation for expressing Test PurposesETSI ETSI ES 202 553 V1.2.1 (2009-06) 2Reference RES/MTS-001002-TPLan Keywords methodology, testing, TTCN ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cede
2、x - 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 Individual copies of the present document can be downloaded from: http:/www.etsi.org The present documen
3、t may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF
4、 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 of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status
5、.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend
6、to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benef
7、it of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI ES 202 553 V1.2.1 (200
8、9-06) 3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Introduction 8g34.1 TPLan: A formal notation for expressing test purpo
9、ses . 8g34.2 Extensibility of TPLan . 8g34.3 The Test Suite Structure . 8g34.4 Areas of application 8g34.5 Limitations of TPLan . 9g35 TPLan keywords, comments and identifiers 9g35.1 TPLan keywords 9g35.2 Comments. 10g35.3 TPLan identifiers 10g35.4 Uniqueness of identifiers 11g35.5 Including files .
10、 11g36 TSS Header 11g36.1 Standard TSS header entries . 11g36.2 User-defined TSS Header entries . 12g37 External references . 12g38 User definitions 13g38.1 User-defined words 13g38.2 User-defined headers 13g38.3 User-defined test entities 13g38.4 User-defined events and parameters . 13g38.5 User-de
11、fined values 14g38.6 User-defined units 14g38.7 User-defined conditions . 15g38.8 Constraining keywords to specific contexts . 15g39 Groups 16g310 TP Header . 17g310.1 Standard TP Header entries 17g310.2 User-defined TP Header entries . 18g311 TP body 18g311.1 TP body structure . 18g311.2 TP pre-con
12、ditions . 19g311.3 TP stimuli . 19g311.4 TP responses . 20g311.5 Precedence of TPLan statements 20g311.6 Temporal ordering of TPLan statements 20g311.7 Using user-defined test entities, conditions and words. 21g311.8 Glue words and readability . 21g3Annex A (normative): The TPLan Grammar . 22g3ETSI
13、ETSI ES 202 553 V1.2.1 (2009-06) 4A.1 Syntactic Rules . 22g3A.2 TPLan EBNF Productions 22g3Annex B (informative): Use of the IPT Testing Framework 27g3B.1 IPT naming conventions . 27g3B.1.1 IPT identifiers . 27g3B.1.2 The Requirements Identifier . 27g3B.1.3 The Configuration Identifier. 27g3B.1.4 Th
14、e Test Purpose Identifier 27g3B.1.5 The Test Case Identifier . 27g3B.1.6 The Test Description Identifier 28g3B.2 IPT cross references . 28g3B.2.1 References to the Requirements Catalogue 28g3B.2.2 References to test configurations 28g3Annex C (informative): A guide to using TPLan in a communications
15、 testing environment 29g3C.1 General considerations . 29g3C.1.1 Introduction 29g3C.1.2 Structure of a TPLan specification . 29g3C.1.3 Choosing a suitable text editor . 30g3C.2 The TPLan header 31g3C.2.1 TSS Header 31g3C.2.2 Cross-references . 31g3C.2.2.1 Requirement sources . 31g3C.2.2.2 Configurati
16、ons 31g3C.2.3 User-defined extensions to TPLan . 32g3C.2.3.1 General layout of user definitions . 32g3C.2.3.2 Header fields . 33g3C.2.3.3 Entities 33g3C.2.3.4 Events . 34g3C.2.3.5 Conditions . 34g3C.2.3.6 Values . 35g3C.2.3.7 Units 35g3C.2.3.8 Keywords 35g3C.2.3.9 Syntactical context 36g3C.3 Test Pu
17、rposes 36g3C.3.1 Grouping TPs . 36g3C.3.1.1 TP header 37g3C.3.1.2 TP Body 38g3C.3.1.2.1 Preconditions . 38g3C.3.1.2.2 Stimulus and response . 38g3C.3.1.2.2.1 The when and then construct . 38g3C.3.1.2.2.2 Identifying the contents of message events . 39g3C.3.1.2.2.3 Interactions with the user . 40g3C.
18、3.1.2.2.4 Establishing the order of a sequence of events 40g3C.3.1.2.2.5 The “do nothing“ response 41g3Annex D (informative): Some communications testing examples 42g3D.1 IPv6 Interoperability Test Purposes . 42g3D.2 QSIG Interoperability Test Purposes . 46g3D.3 ISDN Conformance Test Purposes . 49g3
19、Annex E (informative): Bibliography . 51g3History 52g3ETSI ETSI ES 202 553 V1.2.1 (2009-06) 5Intellectual Property Rights 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
20、for ETSI members and non-members, 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 (ht
21、tp:/webapp.etsi.org/IPR/home.asp). Pursuant 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 m
22、ay become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). ETSI ETSI ES 202 553 V1.2.1 (2009-06) 61 Scope The present document specifies the syntax and use of a notation for the definition
23、of Test Purposes, TPLan. This notation provides a structure and a common set of English keywords for the specification of Test Purposes. The basic notation is oriented towards testing of reactive, black-box communication systems and uses terminology derived from ISO/IEC 9646-1 3. However, facilities
24、 are also included to allow users to extend the notation with application-specific keywords of their own. The use of TPLan as the means of specifying Test Purposes is optional but, if it is used, the requirements specified in the present document shall be met. 2 References References are either spec
25、ific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it
26、 will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. 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 a
27、ny hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies.
28、 For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ETSI ES 201 873-1: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language“. 2 ETSI EG 202 568 (V1.1.3): “Methods for
29、Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework“. 3 ISO/IEC 9646-1: “Information Technology - Open Systems Interconnection - Conformance Testing Methodology and Framework - Part 1: General concepts“. 4 ISO/IEC 9646-2: “Information Technology - Ope
30、n Systems Interconnection - Conformance Testing Methodology and Framework - Part 2: Abstract Test Suite specification“. 2.2 Informative references The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area
31、. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI ES 202 553 V1.2.1 (2009-06) 73 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply:
32、 event: something observable (measurable) at a given place and time NOTE: The cause of a stimulus or the result of a response. notation: textual means of representing ideas programming language: artificial language that can be used to control the behaviour of a machine test case: specification of th
33、e actions required to achieve a specific test purpose, starting in a stable testing state, ending in a stable testing state and defined in either natural language for manual operation or in a machine-readable language (such as TTCN-3) for automatic execution test description: systematic specificatio
34、n of the test steps (generally in tabulated text) that must be taken to reach a specific test verdict test purpose: description of a well-defined objective of testing, focussing on a single interoperability requirement or a set of related interoperability requirements test suite structure: logical g
35、rouping of test purposes or test cases which should be both relevant and convenient 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: EBNF Extended Backus-Nauer Form EUT Equipment Under Test ICS Implementation Conformance Statement IETF International Engi
36、neering Task Force IP Internet Protocol IPT Internet Protocol Testing IUT Implementation Under Test PICS Protocol Implementation Conformance Statement QE Qualified Equipment QSIG Q interface Signalling protocol RFC Request For Comments NOTE: IETF terminology for a draft standard. RQ ReQuirement TC T
37、est CaseTD Test Description TP Test Purpose TPLan Test Purpose Notation TSS Test Suite Structure TTCN-3 Testing and Test Control Notation edition 3 ETSI ETSI ES 202 553 V1.2.1 (2009-06) 84 Introduction 4.1 TPLan: A formal notation for expressing test purposes ISO/IEC 9646-1 3 and ISO/IEC 9646-2 4 re
38、commend that test specifications include a concise and unambiguous description of each test which focuses on its purpose. These Test Purposes, or TPs, define what is to be tested rather than how the testing is performed. The TPs are based on the requirements identified in the relevant standard (or s
39、tandards) from which the test specification is derived. The detailed coding of each Test Purpose is specified in a Test Case. Often Test Cases, or TCs, are written in a test specification language such as TTCN-3 1. The specification of Test Cases is outside the scope of the present document. General
40、ly, Test Purposes are written in prose (possibly displayed in a tabular format). There is considerable benefit to be gained by having all TPs written in a similar and consistent way. With this in mind, a simple, structured notation called TPLan has been developed for the expression of TPs. TPLan is
41、defined with a minimal set of test-oriented keywords but with the capability that permits users to define extensions to the notation. is an example of how TPLan can be extended into a specific application area; in this case, telecommunications. The benefits of using TPLan are: consistency in test pu
42、rpose descriptions - less room for misinterpretation; clear identification of the TP pre-conditions, test body, and verdict criteria; automatic syntax checking and syntax highlighting in text editors; a basis for a TP transfer format and representation in tools. 4.2 Extensibility of TPLan TPLan prov
43、ides a framework for a consistent representation (format, layout, structure and logical ordering) and a consistent use of words and patterns of words for expressing TPs. This is achieved without unnecessarily restricting the expressive power of pure prose. TPLan allows the use of keywords in combina
44、tion with free-text strings (enclosed by single quotes). Thus, the TP writer has considerable freedom of expression in the use of unstructured text between the keywords. The basic set of pre-defined TPLan keywords has been kept to a minimum. These keywords are mainly concerned with providing structu
45、re to the TPs. The intention is that this set of keywords is extended by the user for specific testing applications through the use of user-defined keywords (see clause 8) which can be checked by automatic tools for consistency and, to some extent, correctness. 4.3 The Test Suite Structure Test Purp
46、oses should be grouped in a tree-like structure. This structure is known as the Test Suite Structure, or TSS. The combination of structure and Test Purposes is known as the TSS - A to Z. Numeric: - 0 to 9. special characters: - |._- SEPARATOR := “,“; U_SCORE := “_“; qstring := “ *(“) “; ETSI ETSI ES
47、 202 553 V1.2.1 (2009-06) 27Annex B (informative): Use of the IPT Testing Framework B.1 IPT naming conventions B.1.1 IPT identifiers The IP Testing Framework 2 naming conventions provide traceability to other components of a complete test specification. For example, to the base standards, requiremen
48、ts catalogue or PICS, configuration descriptions or Test Cases. These conventions are defined in EG 202 568 2 but are repeated here for convenience. If the TPLan user wishes to follow these conventions then the syntax defined in 2 should be used. B.1.2 The Requirements Identifier The Requirements Id
49、entifier is of the form RQ_nnn_mmmm where “nnn“ is a 3-digit number and “mmmm“ is a 4-digit number. The Requirements Identifier uniquely identifies a requirement in the corresponding Requirements Catalogue, derived from the relevant base standards. For example: RQ_201_1001 In cases where a PICS (or profile PICS) is used rather than a Requirements Catalogue then the reference to the relevant PICS entry will depend on the naming conventions followed by the relevant PICS. A typical example might be: PICS_101_Table1.item3 B.1.3
