OVERVIEW   INDEX   DEPRECATED   HELP   CORRESPONDENCES  

Module Parameters   Data Types   Component Types   Port Types   Constants   Templates   Signatures   Functions   Altsteps   Test Cases  

Group g_Mobile_Originated_Capability_Discovery

Declared in module RCS_Testcases


Test Cases Summary
RCS_1_2_con_030 Mobile Originated Capability Discovery - Successful.
RCS_1_2_con_031 Mobile Originated Capability Discovery – Unsuccessful – 480 Temporarily Unavailable.
RCS_1_2_con_032 Mobile Originated Capability Discovery – Unsuccessful –408 Request Timeout.
RCS_1_2_con_033 Mobile Originated Capability discovery – Unsuccessful – 404 Not Found.
RCS_1_2_con_034 Mobile Originated Capability Discovery – Successful – Multiple Identities.
RCS_1_2_con_035 Mobile Originated Capability Discovery - Successful.

Details

RCS_1_2_con_030 
testcase RCS_1_2_con_030() runs on MTC_IMS system SYSTEM_IMS

Declared in group g_Mobile_Originated_Capability_Discovery

Mobile Originated Capability Discovery - Successful. 1. User A triggers a capability discovery procedure towards User B at User A’s device. This can be done by one of the following: a. Adding new User B entry (RCS user) to User A’s address book; or b. Refreshing User B’s status (RCS user) manually 2. Execute "Mobile Originated Capability Exchange" (C.1.1) 3. Check that User B is shown as available for RCS on User A’s RCS client

Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_031 
testcase RCS_1_2_con_031() runs on MTC_IMS system SYSTEM_IMS

Declared in group g_Mobile_Originated_Capability_Discovery

Mobile Originated Capability Discovery – Unsuccessful – 480 Temporarily Unavailable. 1. User A triggers a capability discovery procedure towards User B on User A’s device. This can be done by one of the following: a. Adding new User B entry (RCS user) to User A’s address book; or b. Refreshing User B’s (RCS user) status manually 2. Execute step 1 of "Mobile Originated Capability Exchange" (C.1.1). 3. The test tool responds with a 480 TEMPORARILY UNAVAILABLE towards User A’s RCS client. 4. Check that User B is shown as not available for RCS on User A’s RCS client

Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_032 
testcase RCS_1_2_con_032() runs on MTC_IMS system SYSTEM_IMS

Declared in group g_Mobile_Originated_Capability_Discovery

Mobile Originated Capability Discovery – Unsuccessful –408 Request Timeout. 1. User A triggers a capability discovery procedure towards User B on User A’s device. This can be done by one of the following: a. Adding new User B entry (RCS user) to User A’s address book; or b. Refreshing User B’s (RCS user) status manually 2. Execute step 1 of "Mobile Originated Capability Exchange" (C.1.1). 3. The test tool responds with a 408 REQUEST TIMEOUT towards the RCS client. 4. Check that User B is shown as not available for RCS on User A’s RCS client

Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_033 
testcase RCS_1_2_con_033() runs on MTC_IMS system SYSTEM_IMS

Declared in group g_Mobile_Originated_Capability_Discovery

Mobile Originated Capability discovery – Unsuccessful – 404 Not Found. 1. User A triggers a capability discovery procedure towards User B on User A’s device. This can be done by one of the following: a. Adding new User B entry (RCS user) to User A’s address book; or b. Refreshing User B’s (RCS user) status manually 2. Execute step 1 of "Mobile Originated Capability Exchange" (C.1.1). 3. The test tool responds with a 404 NOT FOUND towards User A’s RCS client. 4. Check that User B is shown as not available for RCS on User A’s RCS client

Requirements: User A is IMS registered for RCS, User A’s RCS device is provisioned for RCS

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_034 
testcase RCS_1_2_con_034() runs on MTC_IMS system SYSTEM_IMS

Declared in group g_Mobile_Originated_Capability_Discovery

Mobile Originated Capability Discovery – Successful – Multiple Identities. 1. User A creates a new contact (User C) in address book with the following four unique entries 1. MSISDN number 1 (RCS capable) 2. MSISDN number 2 (without RCS capabilities) 3. MSISDN number 3 (RCS capable, different from 1) 4. SIP-URI (RCS capable, if supported by the UI, independent from 1, 2 or 3). 2. Execute step 1 of "Mobile Originated Capability Exchange" (C.1.1) for all four entries (three if SIP-URI was not supported). 3. The test tool responds with 200 OK towards User A’s RCS client for each OPTIONS message. 4. Check that User C’s identities 1, 3 and 4 (if supported) are shown as available for RCS on User A’s RCS client

Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_035 
testcase RCS_1_2_con_035() runs on MTC_IMS system SYSTEM_IMS

Declared in group g_Mobile_Originated_Capability_Discovery

Mobile Originated Capability Discovery - Successful. 1. User A triggers a capability discovery procedure towards User B at User A’s device. This can be done by one of the following: a. Adding new User B entry (RCS user) to User A’s address book; or b. Refreshing User B’s (RCS user) status manually 2. Execute "Mobile Originated Capability Exchange" (C.1.1) with exception to not sending feature param tag in the contact header of 200 OK. 3. Check that User B is shown as unavailable for RCS on User A’s RCS client

Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS , User B is IMS registered, but does not support RCS

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
© Copyright Testing Technologies IST GmbH 2013