1、 ETSI EG 202 568 V1.1.3 (2007-04)ETSI Guide Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT);Testing: Methodology and FrameworkETSI ETSI EG 202 568 V1.1.3 (2007-04) 2 Reference DEG/MTS-IPT-026-IP-GenTstFwk Keywords generic, interoperability, IP, methodology, testing, TTCN
2、ETSI 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 Individual copies of the present document can b
3、e downloaded from: http:/www.etsi.org The present document 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 re
4、ference shall be the printing on ETSI printers of the 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 of this and other ETSI documen
5、ts is available at http:/portal.etsi.org/tb/status/status.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 permis
6、sion. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Ma
7、rks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI EG 202 568 V1.1.3 (2007-04) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6
8、3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 The IP Testing (IPT) framework8 5 The IPT test development process9 5.1 Conformance testing methodology.10 5.2 Interoperability testing methodology .10 6 The Requirements Catalogue .11 6.1 Entries in the Requirements Catalogue
9、 11 6.2 Naming requirements .12 7 Developing test specifications12 7.1 Conformance test specifications.12 7.1.1 Test configurations .12 7.1.1.1 Naming conformance test configurations13 7.1.1.2 Naming test components .13 7.1.2 Test Suite Structure and Test Purposes.14 7.1.2.1 Test Suite Structure.14
10、7.1.2.1.1 Naming test groups14 7.1.2.2 Test Purposes 14 7.1.2.2.1 Naming TPs.14 7.1.2.2.2 Using the TP Language .15 7.1.3 Test Description development 16 7.1.4 Test Suite development in TTCN-316 7.1.4.1 Modular development of TTCN-3 16 7.1.4.2 Test Cases .16 7.1.4.3 Synchronizing test components.18
11、7.1.4.4 Naming TTCN-3 elements18 7.1.4.5 Test suite parameterization19 7.2 Interoperability test specifications20 7.2.1 Test configurations .20 7.2.1.1 Naming interoperability test configurations20 7.2.1.2 Naming test components .20 7.2.2 Test Suite Structure and Test Purposes.21 7.2.2.1 Test Suite
12、Structure.21 7.2.2.1.1 Naming test groups21 7.2.2.2 Test Purposes 21 7.2.2.2.1 Naming TPs.21 7.2.2.2.2 Using the TP notation TPLan 21 7.2.3 Test Description development 22 7.2.3.1 Naming Test Descriptions.22 7.2.3.2 Presentation of TDs.22 8 TTCN-3 naming conventions.23 9 TTCN-3 comment tags.24 Annex
13、 A (informative): A guide to using the Test Purpose notation, TPLan.25 A.1 General considerations .25 ETSI ETSI EG 202 568 V1.1.3 (2007-04) 4 A.1.1 Introduction 25 A.1.2 Structure of a TPLan specification .25 A.1.3 Choosing a suitable text editor .26 A.2 The TPLan header 27 A.2.1 TSS Header 27 A.2.2
14、 Cross-references .27 A.2.2.1 Requirement sources.27 A.2.2.2 Configurations 27 A.2.3 User-defined extensions to TPLan .28 A.2.3.1 General layout of user definitions.28 A.2.3.2 Header fields.29 A.2.3.3 Entities 29 A.2.3.4 Events .30 A.2.3.5 Conditions.30 A.2.3.6 Values .31 A.2.3.7 Units31 A.2.3.8 Key
15、words31 A.2.3.9 Syntactical context32 A.3 Test Purposes32 A.3.1 Grouping TPs .32 A.3.1.1 TP header33 A.3.1.2 TP body.34 A.3.1.2.1 Preconditions.34 A.3.1.2.2 Stimulus and response.34 A.3.1.2.2.1 The when and then construct .34 A.3.1.2.2.2 Identifying the contents of message events .35 A.3.1.2.2.3 Int
16、eractions with the user.36 A.3.1.2.2.4 Establishing the order of a sequence of events 36 A.3.1.2.2.5 The “do nothing“ response 37 Annex B (informative): Bibliography:38 History 39 ETSI ETSI EG 202 568 V1.1.3 (2007-04) 5 Intellectual Property Rights IPRs essential or potentially essential to the pres
17、ent 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: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in re
18、spect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/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 t
19、he 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 Guide (EG) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). ETSI E
20、TSI EG 202 568 V1.1.3 (2007-04) 6 1 Scope The present document gives guidelines on the use of a common method for developing test specifications for standardized IP-related communications systems and protocols. This method is applicable to all such systems and protocols. The underlying method is bas
21、ed on the methodologies specified in ISO/IEC 9646-1 5 for conformance tests and EG 202 237-1 1 for interoperability tests. It provides guidance on the development and use of the following key elements of the method: a Requirements Catalogue (RC); a Test Suite Structure (TSS) and Test Purposes (TP);
22、Test Descriptions (TD) - interoperability; a TTCN-3 library of data types and values, templates and functions; an Abstract Test Suite (ATS) - conformance. The methodology also offers general guidance on naming conventions and other style-related issues. Although the present document has been develop
23、ed primarily for use in the testing of internet-related protocols, it could equally be used in other areas of protocol test specification. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are eith
24、er specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the exp
25、ected location might be found at http:/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. 1 ETSI EG 202 237: “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT);
26、 Generic approach to interoperability testing“. 2 ETSI EG 201 770 (V4.2.2): “Methods for Testing and Specification (MTS); Test Synchronization Protocol 1 plus (TSP1+) specification“. 3 ETSI EG 202 106 (V2.1.1): “Methods for Testing and Specification (MTS); Guidelines for the use of formal SDL as a d
27、escriptive tool“. 4 ETSI TS 102 351 (2005): “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework“. 5 ISO/IEC 9646-1 (1992): “Information Technology - Open Systems Interconnection - Conformance Testing Methodology and Framework - Part
28、1: General concepts“. ETSI ETSI EG 202 568 V1.1.3 (2007-04) 7 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: behavioural function: TTCN-3 function which specifies actions which result in the sending of messages to
29、one or more observed interface computational function: TTCN-3 function which specifies actions which modifies data values but does not result in the sending of messages to one or more observed interface Equipment Under Test (EUT): grouping of one or more devices which has not been previously shown t
30、o interoperate with previously Qualified Equipment (QE) 1 internet protocols: any protocol, including IPv4 and IPv6, designed specifically for use in an internet environment. Such protocols include DHCP, ICMP, SIP and IKEv2 Qualified Equipment (QE): grouping of one or more devices that has been show
31、n, by rigorous and well-defined testing, to interoperate with other equipment 1 NOTE: Once an EUT has been successfully tested against a QE, it may be considered to be a QE, itself. TPLan: notation for expressing test purposes 3.2 Abbreviations For the purposes of the present document, the following
32、 abbreviations apply: 3GPP 3rdGeneration mobile Partnership Project ATS Abstract Test Suite EUT Equipment Under Test IETF Internet Engineering Task Force IFS Interoperable Functions Statement IP Internet Protocol IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 IPT IP Testing IUT Im
33、plementation Under Test MTC Main Test Component NGN Next Generation Network PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing PTC Parallel Test Component QE Qualified Equipment RC Requirements Catalogue RFC Request For Comments (IETF termi
34、nology for a draft standard) RQ Requirement SUT System Under Test TC Test Case TD Test Description TP Test Purpose TSP1+ Test Synchronization Protocol 1+ TSS Test Suite Structure TTCN-3 Testing and Test Control Notation edition 3 UDP User Datagram Protocol UT Upper Tester ETSI ETSI EG 202 568 V1.1.3
35、 (2007-04) 8 4 The IP Testing (IPT) framework ETSI test specifications are usually developed for a single base protocol standard or for a coherent set of standards. As such, it is possible to follow the methodology specified for conformance test development in ISO/IEC 9646-1 5 without much difficult
36、y. However, Internet Protocol (IP) testing requirements are, in many cases, distributed across a wide range of documents and, thus, an adaptation of the ISO/IEC 9646 approach to test development is necessary. Also, for readability, consistency and to ease reusability of TTCN-3 code it is necessary t
37、o apply some guidelines on the use of TTCN-3. It is this approach that is referred to as the “IP Testing (IPT) Framework“. As its name implies, the framework is oriented towards the production of Test specifications for internet protocols. The IPT Framework comprises: a documentation structure: - ca
38、talogue of requirements; - Test Suite Structure (TSS); - Test Purposes (TP): square4 conformance; square4 interoperability. a methodology linking the individual elements of a test specification together: - style guidelines and examples; - naming conventions; - a structured notation for TPs; - guidel
39、ines on the development of TTCN-3 Test Cases (TCs); - guidelines on the use of tabulated English Test Descriptions (TDs). ETSI ETSI EG 202 568 V1.1.3 (2007-04) 9 5 The IPT test development process The process to be followed when developing IP test specifications is shown in figure 1. Figure 1: IPT t
40、est development process ETSI ETSI EG 202 568 V1.1.3 (2007-04) 10The process begins with the analysis of the primary public standards related to the IP communications system to be tested (most often IETF RFCs) and a range of secondary inputs which include: current industry practice; existing test doc
41、umentation from any relevant fora and other established sources; specifications related to the use of communications system in other standardization bodies. The result of this analysis is the identification and classification of a full range of requirements which is recorded in the Requirements Cata
42、logue and used as the basis for both conformance and interoperability test specifications. 5.1 Conformance testing methodology Conformance test specifications should be produced following the methodology described in ISO/IEC 9646-1 5. In summary, this methodology begins with the collation and catego
43、rization of the requirements to be tested into a tabular form which is normally referred to as the “Protocol Implementation Conformance Statement“ (PICS). Each PICS relates to a specific protocol standard. In those cases where the requirements are distributed across a large number of documents there
44、 may be very little benefit in producing an individual PICS for each document. Consequently, the requirements should be collected together and categorized in a single document, referred to in figure 1 as the Requirements Catalogue. This document could be structured as an overall PICS covering the re
45、quirements of all the relevant specifications. For each requirement in the catalogue, one or more tests should be identified and classified into a number of groups which will provide a structure to the overall test suite (TSS). A brief Test Purpose (TP) should then be written for each identified tes
46、t and this should make it clear what is to be tested but not how this should be done. Although not described or mandated in ISO 9646-1, in many situations (particularly where the TPs are complex) it may be desirable to develop a Test Description (TD) for each TP. The TD describes in plain language (
47、often tabulated) the actions required to reach a verdict on whether an implementation passes or fails the test. Finally, a detailed Test Case (TC) is written for each TP. In the interests of test automation, TCs are usually combined into an Abstract Test Suite (ATS) using a specific testing language
48、 such as TTCN-3. 5.2 Interoperability testing methodology For a certification (or branding or logo) scheme to be meaningful, it is necessary that interoperability testing is carried out in addition to conformance testing and that this is done in accordance with a comprehensive and structured suite o
49、f tests. In the context of the present document, it is this type of testing which is referred to as “Interoperability Testing“. The purpose of interoperability testing is to prove that the end-to-end functionality between (at least) two communicating systems is as required by the standard(s) on which those systems are based. A methodology for developing such interoperability test specification is described in EG 202 237 6 and this should be used as a guide when developing test suites. This methodology is based extensively on ISO
