ETSI ES 202 196-1-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 1 Overview (V1 2 1 Parlay 3)《开放业务接入(OS_1.pdf

1、 ETSI ES 202 196-1 V1.2.1 (2005-02)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 1: Overview(Parlay 3)ETSI ETSI ES 202 196-1 V1.2.1 (2005-02) 2 Reference RES/TISPAN-06005-01-OSA Keywords API, OSA, TSS Essential, or pot

2、entially 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:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried

3、 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 Committee T

4、elecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 1 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part 2: “Common data d

5、efinitions“; Part 3: “Framework“; Part 4: “Call control SCF“; Part 5: “User interactions SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal capabilities SCF“; Part 8: “Data session control SCF“; Part 9: “Generic messaging SCF“; Part 10: “Connectivity manager SCF“; Part 11: “Account management SCF“; Par

6、t 12: “Charging SCF“. To evaluate conformance of a particular implementation, it is necessary to have a set of test purposes to evaluate the dynamic behaviour of the Implementation Under Test (IUT). The specification containing those test purposes is called a Test Suite Structure and Test Purposes (

7、TSS Application Programming Interface (API)“. 2 ETSI ES 202 170: “Open Service Access (OSA); Application Programming Interface (API); Implementation Conformance Statement (ICS) proforma specification (Parlay 3)“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance

8、testing methodology and framework - Part 1: General concepts“. 4 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of th

9、e present document, the terms and definitions given in ES 201 915-1 1, ISO/IEC 9646-1 3, ISO/IEC 9646-2 4 and the following apply: abstract test case: Refer to ISO/IEC 9646-1 3. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 3. ICS proforma: Refer to ISO/IEC 9646-1 3. Implementation Conformance

10、Statement (ICS): Refer to ISO/IEC 9646-1 3. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 3. Test Purpose (TP): Refer to ISO/IEC 9646-1 3. ETSI ETSI ES 202 196-1 V1.2.1 (2005-02) 6 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: API Applicati

11、on Programming Interface ATS Abstract Test Suite IUT Implementation Under Test ICS Implementation Conformance Statement OSA Open Service Access SCF Switching Control Function SOAP Simple Object Access Protocol TP Test Purpose TSS Test Suite Structure WSDL Web Services Definition Language 4 Overview

12、of OSA testing documentation The OSA test specification for Parlay 3 is a multi-part deliverable, following exactly the same part structure as the multi-part OSA base specification (Parlay 3), in ES 201 915 1. The following structure has been used for the test specification: Part 1: “Overview“; Part

13、 2: “Common Data Definitions“; (empty document, to keep part numbering same as ES 201 915 1) Part 3: “Framework“; Part 4: “Call Control SCF“; Part 5: “User Interaction SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SC

14、F“; Part 10: “Connectivity Manager SCF“; Part 11: “Account Management SCF“; Part 12: “Charging SCF“. A related specification, the OSA Implementation Conformance Statement (ICS) proforma specification for Parlay 3, has also been produced. This can be found in ES 202 170 2. These two specifications ar

15、e closely related, and the test specifications have been designed to be used with the ICS proforma specification. ETSI ETSI ES 202 196-1 V1.2.1 (2005-02) 7 5 Test Purposes (TP) 5.1 Test Purpose description method All test purposes are described in a similar manner. Each has a 1-line summary descript

16、ion, followed by a reference to the source of the base specification requirement being tested. Each test purpose may include a preamble description, and a pre-requisite or pre-condition, as required. Then follows a numbered list of methods the tester is required to call on identified interfaces on t

17、he IUT, or methods the IUT is required to call on the testers interfaces. In addition to the text description of each test purpose, a short sequence diagram has been included to illustrate the sequence of expected events. Most tests cover testing of the IUTs expected response to valid behaviour from

18、 the tester. A number of tests examine response to invalid behaviour from the tester, usually leading to exceptions being raised. Tests without any preconditions are mandatory tests. 5.2 Realization technology issues The OSA specifications can be realized using many different technologies, and can u

19、sed in different types of networks, and different contexts. The OSA specification for Parlay 3 (ES 201 915 1) includes only CORBA IDL code as a realization technology. But this is not intended to limit the types of realization technologies which can be used (Java, .NET, WSDL/SOAP, etc.). Similarly,

20、the OSA APIs have been designed to enable their use with numerous different types of networks: fixed or mobile, circuit or packet switched, voice and non-voice networks. This broad range of realization possibilities poses a problem for the creators of test specifications and test tools. The test spe

21、cification should not assume a certain realization technology has been used - in doing so, it restricts the use of other valid technologies. But a test tool, which implements the test specification, will have to be implementation technology specific. The OSA test specifications have been designed to

22、 permit their use with any technology used to implement OSA. Many details and specific values, which are necessary to run the test cases, but are specific to how the OSA APIs being tested are implemented, have been left out or generalized in the test specifications. When these test specifications ar

23、e implemented, they will need a significant amount of parameterization with items such as interface references, addresses etc. These may be specific to the realization technology or underlying network type. Implementers should not underestimate this task. 5.3 Test specification coverage The tests ha

24、ve been developed with a view towards promoting interoperability. Rather than attempting to provide complete coverage, in the style of full conformance tests, the tests have been limited to conceivable situations to which a real implementation is likely to be faced, identifying the most likely behav

25、ioural sequences, or sequences considered most likely to lead to interoperability difficulties. The tests are only based on conformance requirements related to the externally observable behaviour of the IUT. ETSI ETSI ES 202 196-1 V1.2.1 (2005-02) 8 History Document history V1.1.1 August 2003 Publication V1.2.1 December 2004 Membership Approval Procedure MV 20050211: 2004-12-14 to 2005-02-11 V1.2.1 February 2005 Publication