ETSI TS 103 254-2017 Methods for Testing and Specification (MTS) TTCN-3 Conformance Test Suite for use of XML schema Test Suite Structure and Test Purposes (TSS & TP) (V1 3 1 Inclu.pdf

1、 ETSI TS 103 254 V1.3.1 (2017-09) Methods for Testing and Specification (MTS); TTCN-3 Conformance Test Suite for use of XML schema; Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI S

2、ecretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). 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 updat

3、es 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 tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as be

4、ing 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 constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specifica

5、tion (TS) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). 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.

6、2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 254 V1.3.1 (2017-09)5 1 Scope The purpose of the present document is to provide Test Suite Structure and Test

7、 Purposes (TSS The Testing and Test Control Notation version 3; Part 9: Using XML schema with TTCN-3“. 2 ISO/IEC 9646-1 (1992): “Information Technology - Open Systems Interconnection - Conformance Testing Methodology and Framework - Part 1: General concepts“. 3 ISO/IEC 9646-7 (1994): “Conformance te

8、sting methodology and framework - Part 7: Implementation Conformance Statement“. 4 ETSI TS 102 995: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Proforma for TTCN-3 reference test suite“. 5 ETSI ES 201 873-1: “Methods for Testing and Specification (M

9、TS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language“. 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

10、-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 guarantee their long term validity. The following referenced documents are not necessary for t

11、he application of the present document but they assist the user with regard to a particular subject area. i.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“. i.2 ETSI ES 201 873-5: “Methods for Testing a

12、nd Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)“. i.3 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)“. i.4 ETSI ES 201 873-7: “Met

13、hods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 7: Using ASN.1 with TTCN-3“. ETSI ETSI TS 103 254 V1.3.1 (2017-09)6 i.5 ETSI ES 201 873-8: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 8: The IDL to

14、 TTCN-3 Mapping“. i.6 ETSI ES 202 781: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support“. i.7 ETSI ES 202 784: “Methods for Testing and Specification (MTS); The Testing and Test Control Not

15、ation version 3; TTCN-3 Language Extensions: Advanced Parameterization“. i.8 ETSI ES 202 785: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Behaviour Types“. 3 Definitions and abbreviations 3.1 Definitions For the purposes

16、of the present document, the terms and definitions given in ISO/IEC 9646-1 2, ISO/IEC 9646-7 3, ETSI ES 201 873-1 5 (TTCN-3) and the following apply: Abstract Test Suite (ATS): test suite composed of abstract test cases ICS pro forma: document, in the form of a questionnaire, which when completed fo

17、r an implementation or system becomes an ICS Implementation Conformance Statement (ICS): statement made by the supplier of an implementation claimed to conform to a given specification, stating which capabilities have been implemented Implementation eXtra Information for Testing (IXIT): statement ma

18、de by a supplier or implementor of an IUT which contains or references all of the information related to the IUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT Implementation Under Test (IUT): implementation of one or more OSI prot

19、ocols in an adjacent user/provider relationship, being part of a real open system which is to be studied by testing IXIT pro forma: document, in the form of a questionnaire, which when completed for the IUT becomes the IXIT 3.2 Abbreviations For the purposes of the present document, the following ab

20、breviations apply: ATS Abstract Test Suite ICS Implementation Conformance Statement IUT Implementation under Test IXIT Implementation eXtra Information for Testing TC Test Case TCI TTCN-3 Control Interface TP Test Purpose TRI TTCN-3 Runtime Interface TS Test System TSS Test Suite Structure TSS b) ne

21、gative tests (“Neg_“ test case name prefix). The execution order of the TTCN-3 tool conformance test cases is specified in the dependencies section of test purpose descriptions. ETSI ETSI TS 103 254 V1.3.1 (2017-09)8 Annex A (normative): Test Purposes (TP) A.0 General For each test requirement a Tes

22、t Purpose (TP) is defined. Test purposes shall be defined in a dedicated test purpose document as well as with TTCN-3 documentation tags in each test case of the ATS. Both documentations shall convey the same information for each test purpose. A.1 Introduction A.1.1 Test purpose naming convention Th

23、e test purpose naming scheme corresponds to the test case identifier naming scheme and vice-versa. A.1.2 Test purpose structure The test purpose structure is according to the test suite structure (TSS). A.1.3 Test purpose format In the following, examples for tabular test purpose descriptions are sh

24、own that shall be defined in the test purpose document. This representation is a direct mapping of the contents of the document tags in the ATS (such as purpose, remark, or verdict). The tabular descriptions are presented along with their corresponding TTCN-3 documentation tag equivalent. The test p

25、urpose reference shall be provided in a machine-readable format. Test Purpose Id TP_Neg_05_top_level_001 Reference ETSI ES 201 873-9 1, clause 5 ICS None Dependencies None Summary Verify that error is generated for missing XSD language tag in import clause Expected Output The TTCN-3 module shall be

26、rejected by the validator or after/during execution Notes A corresponding TTCN-3 module addressing TP_Neg_05_top_level_001 is the following: /* * author STF 521 * version 0.0.1 * purpose 9:5, Verify that error is generated for missing XSD language tag in import clause * verdict pass reject */ / The

27、following requirements are tested: / When importing from an XSD Schema, the following language identifier string shall be used: “XSD“ module Neg_05_top_level_001 import from schema_Neg_05_top_level_001 all; template MyType m_msg := 1; /* * desc The timeout given in seconds after which the test case

28、will be stopped. */ modulepar float PX_TC_EXECUTION_TIMEOUT := 5.0; type universal charstring Raw; type port P message inout all; ETSI ETSI TS 103 254 V1.3.1 (2017-09)9 type component C port P p; testcase TC_Neg_05_top_level_001() runs on C system C map(self:p, system:p); / encode the message p.send

29、(m_msg); log(“template should either be rejected by compiler or by runtime latest while encoding“); setverdict(fail, “Invalid template should not be encoded“); unmap(self:p, system:p); control execute(TC_Neg_05_top_level_001(),PX_TC_EXECUTION_TIMEOUT); Test Purpose Id TP_Pos_050101_namespaces_001 Re

30、ference ETSI ES 201 873-9 1, clause 5.1.1 ICS None Dependencies None Summary Verify that schema with target namespace is correctly translated into single module Expected Output The TTCN-3 module shall be accepted by the tool and all test cases have to produce the verdict pass after execution Notes A

31、 corresponding TTCN-3 module for TP_Pos_050101_namespaces_001 is the following: /* * author STF 521 * version 0.0.1 * purpose 9:5.1.1, Verify that schema with target namespace is correctly translated into single module * verdict pass accept, ttcn3verdict:pass */ / The following requirements are test

32、ed: / A single XML Schema may be composed of a single or several schema element information / items, and shall be translated to one or more TTCN-3 modules, corresponding to schema / components that have the same target namespace. For XSD schemas with the same target / namespace (including absence of

33、 the target namespace) exactly one TTCN-3 module shall / be generated. module Pos_050101_namespaces_001 import from schema_Pos_050101_namespaces_001 language “XSD“ all; template MyType m_msg := 1; /* * desc The timeout given in seconds after which the test case will be stopped. */ modulepar float PX

34、_TC_EXECUTION_TIMEOUT := 5.0; type universal charstring Raw; type universal charstring File; type record of File FileList; type port P message inout all; type component C port P p; /* * desc lexical compare the charstring p_textToMatch with the contents of the reference XML file and returns true if

35、they represent the same XML structure * param p_textToMatch text to be compared with the UTF-8 contents of the XML file * param p_referenceXmlFile the XML file * param p_xsdFileList the list of XSD files * param p_matchError the error result in case it did not match * param p_referenceTTCN3File the

36、file of the TTCN-3 test module. This path is used to find the reference XML file relative to this path, by keeping the TTCN-3 code file system independent. * return true if p_textToMatch and the contents of p_referenceXmlFile represent the same XML structure */ external function matchFile(Raw p_text

37、ToMatch, File p_referenceXmlFile, FileList p_xsdFileList, out universal charstring p_matchError, File p_referenceTTCN3File := _FILE_) return boolean; ETSI ETSI TS 103 254 V1.3.1 (2017-09)10 testcase TC_Pos_050101_namespaces_001() runs on C system C var Raw v_rcv; var universal charstring v_matchErro

38、r; map(self:p, system:p); / encode the message p.send(m_msg); alt / compare the encoded message with the reference XML file p.check(receive(Raw:?) - value v_rcv) log(“XML message “, v_rcv); if (matchFile(v_rcv, “Pos_050101_namespaces_001.xml“, “Pos_050101_namespaces_001.xsd“ , v_matchError) alt / ma

39、tch decoded value to pass test p.receive(m_msg) setverdict(pass, “Decoded value matches encoded template and reference XML“); p.receive setverdict(fail, “XML decoding failure“); else setverdict(fail, v_matchError); p.receive setverdict(fail, “Raw decoding failure“); control execute(TC_Pos_050101_nam

40、espaces_001(), 5.0); ETSI ETSI TS 103 254 V1.3.1 (2017-09)11 A.2 Test purposes for the TTCN-3 Part 9 conformance test suite The TTCN-3 library modules are contained in archive ts_103254v010301p0.zip which accompanies the present document. This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873 i.1 to i.5. ETSI ETSI TS 103 254 V1.3.1 (2017-09)12 History Document history V1.1.1 March 2015 Publication V1.2.1 March 2016 Publication V1.3.1 September 2017 Publication