ETSI ES 202 388-5-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 5 User interaction SCF《开放业务接入(OSA) 应用编.pdf

《ETSI ES 202 388-5-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 5 User interaction SCF《开放业务接入(OSA) 应用编.pdf》由会员分享，可在线阅读，更多相关《ETSI ES 202 388-5-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 5 User interaction SCF《开放业务接入(OSA) 应用编.pdf（73页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI ES 202 388-5 V1.1.1 (2005-03)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 5: User interaction SCF(Parlay 4)ETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 2 Reference DES/TISPAN-06004-05-OSA Keywords API, OSA, TSS Essen

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

3、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. Foreword This ETSI Standard (ES) has been produced by ETSI Technical

4、 Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 5 of a multi-part deliverable. Full details of the entire series can be found in part 1 6. To evaluate conformance of a particular implementation, it is necessar

5、y 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 (TSS Application Programming Interface (API); Part 5: User Interaction SCF (Parlay 4)“. 2 ETS

6、I ES 202 363: “Open Service Access (OSA); Application Programming Interface (API); Implementation Conformance Statement (ICS) proforma specification; (Parlay 4)“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: Genera

7、l concepts“. 4 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. 5 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specification

8、s; Standardization methodology“. 6 ETSI ES 202 388-1: “Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part 1: Overview (Parlay 4)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and

9、 definitions given in ES 202 915-5 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 Method (ATM): Refer to ISO/IEC 9646-1 3. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 3. Implementation Under Test (IUT): Refer to ISO/

10、IEC 9646-1 3. Lower Tester (LT): Refer to ISO/IEC 9646-1 3. Implementation Conformance Statement (ICS): Refer to ISO/IEC 9646-1 3. ETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 6 ICS proforma: Refer to ISO/IEC 9646-1 3. Implementation eXtra Information for Testing (IXIT): Refer to ISO/IEC 9646-1 3. IXIT p

11、roforma: Refer to ISO/IEC 9646-1 3. Test Purpose (TP): Refer to ISO/IEC 9646-1 3. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: API Application Programming Interface ATM Abstract Test Method ATS Abstract Test Suite ICS Implementation Conformance State

12、ment IUT Implementation Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester OSA Open Service Access SCF Service Capability Feature TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) User Interaction - IPUIManager interface - IPUI interface - IPUICall inter

13、face 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convention TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite (see table 1). Table 1: T

14、P identifier naming convention scheme Identifier: _ = SCG name: “UI“ for User Interaction part of User Interaction SCF UI_APP for User Interaction part of User interaction Application = sequential number: (01-99) 5.1.2 Source of TP definition The TPs are based on ES 202 915-5 1. ETSI ETSI ES 202 388

15、-5 V1.1.1 (2005-03) 7 5.1.3 Test strategy As the base standard ES 202 915-5 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification ES 202 363 2. The TPs are only based on conformance requirements related to t

16、he externally observable behaviour of the IUT and are limited to conceivable situations to which a real implementation is likely to be faced (see ETS 300 406 5). 5.2 TPs for the User Interaction SCF All PICS items referred to in this clause are as specified in ES 202 363 2 unless indicated otherwise

17、 by another numbered reference. All parameters specified in method calls are valid unless specified. The procedures to trigger the SCF to call methods in the application are dependant on the underlying network architecture and are out of the scope of the present document. Those method calls are prec

18、eded by the words “Triggered action“. 5.2.1 User Interaction, SCF side Pre-requisite: Registration of the IUT (User Interaction SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpUIManager interface through selecting that service and

19、 signing the required service agreement. 5.2.1.1 IpUIManager interface Test UI_01 Summary: IpUIManager, createUI method, successful Reference: ES 202 915-5 1, clause 8.1 Selection: createUI method supported - PICS item: 2 UIM1 Test Sequence: 1. Method call createUI() Parameters: appUI, userAddress C

20、heck: valid value of TpUIIdentifier is returned : IpAppUIManager : IpUIManagercreateUI(appUI, userAddress)userInteractionETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 8 Test UI_02 Summary: IpUIManager, createUI method, P_INVALID_NETWORK_STATE Reference: ES 202 915-5 1, clause 8.1 Selection: createUI metho

21、d supported - PICS item: 2 UIM1 Condition: the underlying protocol cannot support the method call. Test Sequence: 1. Method call createUI() Parameters: appUI, userAddress Check: P_INVALID_NETWORK_STATE is returned : IpAppUIManager : IpUIManagercreateUI(appUI, userAddress)P_INVALID_NETWORK_STATETest

22、UI_03 Summary: IpUIManager, createUI method, P_INVALID_INTERFACE_TYPE Reference: ES 202 915-5 1, clause 8.1 Selection: createUI method supported - PICS item: 2 UIM1 Test Sequence: 1. Method call createUI() Parameters: appUI including an invalid reference type, userAddress Check: P_INVALID_ INTERFACE

23、_TYPE is returned : IpAppUIManager : IpUIManagercreateUI(appUI, userAddress)P_INVALID_INTERFACE_TYPEETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 9 Test UI_04 Summary: IpUIManager, createUICall method, successful Reference: ES 202 915-5 1, clause 8.1 Selection: createUICall method supported - PICS item: 2

24、 UIM2 Test Sequence: 1. Method call createUICall() Parameters: appUI, uiTargetObject Check: valid value of TpUIIdentifier is returned : IpAppUIManager : IpUIManagercreateUICall(appUI, uiTargetObject)userInteractionTest UI_05 Summary: IpUIManager, createUICall method, P_INVALID_NETWORK_STATE Referenc

25、e: ES 202 915-5 1, clause 8.1 Selection: createUICall method supported - PICS item: 2 UIM2 Condition: the underlying protocol cannot support the method call. Test Sequence: 1. Method call createUICall() Parameters: appUI, userAddress Check: P_INVALID_NETWORK_STATE is returned : IpAppUIManager : IpUI

26、ManagercreateUICall(appUI, uiTargetObject)P_INVALID_NETWORK_STATEETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 10Test UI_06 Summary: IpUIManager, createUICall method, P_INVALID_INTERFACE_TYPE Reference: ES 202 915-5 1, clause 8.1 Selection: createUICall method supported - PICS item: 2 UIM2 Test Sequence:

27、1. Method call createUICall() Parameters: appUI including an invalid reference type, userAddress Check: P_INVALID_INTERFACE_TYPE is returned : IpAppUIManager : IpUIManagercreateUICall(appUI, uiTargetObject)P_INVALID_INTERFACE_TYPETest UI_07 Summary: IpUIManager, all createNotification and destroyNot

28、ification methods, successful Reference: ES 202 915-5 1, clause 8.1 Selection: createNotification methods supported - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2. Method call destroyN

29、otification() Parameters: assignmentID as returned in 1 Check: no exception is returned. ETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 11: IpAppUIManager : IpUIManagercreateNotification(appUIManager, eventCriteria1)assignmentIDdestroyNoti ficati on(assignmentID)Test UI_08 Summary: IpUIManager, receipt of

30、reportEventNotification method, successful Reference: ES 202 915-5 1, clauses 8.1 and 8.2 Selection: createNotification methods supported - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2

31、. Triggered action: cause IUT to call reportEventNotification() method on the testers (Application) IpAppUIManager interface. Check: valid value of userInteraction, eventNotificationInfo and assignmentID given in 1. is transmitted,Return: valid value of IpAppUIRef ETSI ETSI ES 202 388-5 V1.1.1 (2005

32、-03) 12: IpAppUIManager : IpUIManagercreateNotification(appUIManager, eventCriter.assignmentIDreportEventNotification(userInteraction, eventNotificationInfo, assignmentID)appUITest UI_09 Summary: IpUIManager, createNotification method, P_INVALID_INTERFACE_TYPE Reference: ES 202 915-5 1, clause 8.1 S

33、election: createNotification methods supported - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager including an invalid reference type, eventCriteria, Check: P_INVALID_INTERFACE_TYPE is returned : IpAppUIManager : IpUIManagercreateNotification(appUIManager

34、_inv, eventCriteria)P_INVALID_INTERFACE_TYPEETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 13Test UI_10 Summary: IpUIManager, createNotification method, P_INVALID_CRITERIA Reference: ES 202 915-5 1, clause 8.1 Selection: createNotification methods supported - PICS item: 2 UIM3 Test Sequence: 1. Method call

35、 createNotification() Parameters: appUIManager, eventCriteria containing an invalid criteria. Check: P_INVALID_CRITERIA is returned. : IpAppUIManager : IpUIManagercreateNotification(appUIManager, eventCriteria_inv)P_INVALID_CRITERIATest UI_11 Summary: IpUIManager, createNotification and changeNotifi

36、cation methods, P_INVALID_ASSIGNMENT_ID Reference: ES 202 915-5 1, clause 8.1 Selection: createNotification and changeNotification methods supported - PICS item: 2 UIM3 AND UIM5 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssign

37、mentID is returned 2. Method call changeNotification() Parameters: assignmentID different from returned in 1., eventCriteria. Check: P_INVALID_ASSIGNMENT_ID is returned. ETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 14: IpAppUIManager : IpUIManagerchangeNotification(assignmentID_inv, eventCriteria)P_INVAL

38、ID_ASSIGNMENT_IDcreateNotification(appUIManager, eventCriteria)a ssi g n m e n tIDTest UI_12 Summary: IpUIManager, createNotification and changeNotification method, P_INVALID_CRITERIA Reference: ES 202 915-5 1, clause 8.1 Selection: createNotification and changeNotification methods supported - PICS

39、item: 2 UIM3 AND UIM5 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2. Method call changeNotification() Parameters: assignmentID as returned in 1., eventCriteria containing an invalid criteria Check: P_INV

40、ALID_CRITERIA is returned. : IpAppUIManager : IpUIManagerchangeNotification(assignmentID, eventCriteria_inv)P_INVALID_CRITERIAcreateNotification(appUIManager, eventCriteria)assignmentIDETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 15Test UI_13 Summary: IpUIManager, destroyNotification method, P_INVALID_AS

41、SIGNMENT_ID Reference: ES 202 915-5 1, clause 8.1 Selection: createNotification method supported - PICS item: 2 UIM3 Test Sequence: 1. Method call createNotification() Parameters: appUIManager, eventCriteria, Check: valid value of TpAssignmentID is returned 2. Method call destroyNotification() Param

42、eters: assignmentID different from 1 Check: P_INVALID_ASSIGNMENT_ID is returned. : IpAppUIManager : IpUIManagerdestroyNotification(assignmentID_inv)P_INVALID_ASSIGNMENT_IDcreateNotification(appUIManager, eventCriteria)assignmentIDETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 16Test UI_52 Summary: IpUIMana

43、ger, all methods, successful Reference: ES 202 915-5 1, clause 8.1 Precondition: enableNotifications supported Preamble: Registration of the IUT (User Interaction SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpUIManager interface

44、 through selecting that service and signing the required service agreement. Test Sequence: 1. Method call enableNotifications() Parameters: appUIManager Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call reportEventNotification() method on the testers (Applicatio

45、n) IpAppAccountManager interface. Parameters: userInteraction, eventNotificationInfo, assignmentID 3. Method call disableNotifications() Parameters: none Check: no exception is returned : IpAppUIManager : IpUIManagerdisableNotifications()e nabl eNo ti fi ca ti ons(a ppUI Manag er)assignmentIDreportE

46、ventNotification(userInteraction, eventNotificationInfo, assignmentID)ETSI ETSI ES 202 388-5 V1.1.1 (2005-03) 175.2.1.2 IpUI interface Test UI_14 Summary: IpUI, sendInfoReq & sendInfoRes methods, successful Reference: ES 202 915-5 1, clauses 8.3 and 8.4 Preamble: A User Interaction object, created e

47、ither with the createUI or the createUICall method on the IpUIManager interface or reported in a reportEventNotification method, exists. The given sessionID is used in the following methods to identify this User Interaction object. Selection: sendInfoReq method supported - PICS item: 2 UI1 Test Sequ

48、ence: 1. Method call sendInfoReq() Parameters: userInteractionSessionID given in preamble, info, language, variableInfo, repeatIndicator, responseRequested. Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call sendInfoRes() method on the testers (Application) IpApp

49、UI interface. Check: valid value of userInteractionSessionID (given in preamble), assignmentID (given in 1.) and response is transmitted, Return: no parameter : IpAppUIManager : IpAppUI : IpUIManager : IpUIpreamble:createUI(appUI, userAddress)userInteractionSessionID1sendInfoReq(userInteractionSessionID1, info, language, variableInfo, repeatIndicator, responseRequested)assignmentID1send In foRes(userInteracti onSe ssion ID1 , assi gnmen tI D1, response)ETSI ETSI ES 202 388-5 V1.1