OVERVIEW   INDEX   DEPRECATED   HELP   CORRESPONDENCES  


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

Group g_Mobile_Originated_Group_Chat

Declared in module RCS_Testcases


Test Cases Summary
RCS_1_2_con_130 Verifies Mobile Originated Group Chat session establishment and Originating User leaves the session 1.
RCS_1_2_con_131 Verifies Mobile Originated Group Chat session when non-originating Users leave the session and the session is closed 1.
RCS_1_2_con_132 Verifies Group Chat when a new User is added to the session 1.

Details

RCS_1_2_con_130
testcase RCS_1_2_con_130() runs on MTC_IMS system SYSTEM_IMS 

Declared in group g_Mobile_Originated_Group_Chat

Verifies Mobile Originated Group Chat session establishment and Originating User leaves the session 1. User A initiates a Group Chat session with User B, User C and User D on his device with the subject “Test”. 2. Execute “Mobile Originated Session Establishment: Group Chat” (C.2.13) with the subject “Test” and participants list with User B and User C as accepted (User D does not accept). 3. User A receives the participant list and the status for each one 4. User A sends the message “Hello group” to the group. 5. Execute “MSRP Group Session Message” (C.7.6) with the message “Hello group” from Client A. 6. Execute “MSRP Group Session Message” (C.7.6) with the message “Hello A” from the Test Tool from User B 7. User A receives “Hello A” from User B. 8. User A leaves the Group Chat session. 9. Execute “Mobile Originated Session Termination” (C.3.1)

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

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.5

RCS_1_2_con_131
testcase RCS_1_2_con_131() runs on MTC_IMS system SYSTEM_IMS 

Declared in group g_Mobile_Originated_Group_Chat

Verifies Mobile Originated Group Chat session when non-originating Users leave the session and the session is closed 1. User A initiates a Group Chat session with User B, User C and User D on his device with the subject “Test”. 2. Execute “Mobile Originated Session Establishment: Group Chat” (C.2.13) with the subject “Test” and participants list with User B and User C as accepted (User D does not accept). 3. Execute “MSRP Group Session Message” (C.7.6) with the message “B going” from the Test Tool from User B 4. User A receives the message “B going” from User B. 5. Execute “Participant List Update” (C.5.1) with User B as offline (and User C as accepted). 6. User A receives the participant list and the status for each one (User B as offline and User C as accepted). 7. Execute “MSRP Group Session Message” (C.7.6) with the message “C going” from the Test Tool from User C 8. User A receives the message “C going” from User C. 9. Execute “Participant List Update” (C.5.1) with User C as offline. 10. User A receives the participant list and the status for each one (User C as offline). 11. Execute “Mobile Terminated Session Termination” (C.3.2).

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

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.5

RCS_1_2_con_132
testcase RCS_1_2_con_132() runs on MTC_IMS system SYSTEM_IMS 

Declared in group g_Mobile_Originated_Group_Chat

Verifies Group Chat when a new User is added to the session 1. User A initiates a Group Chat session with User B and User C on his device with the subject “Test”. 2. Execute “Mobile Originated Session Establishment: Group Chat” (C.2.13) with the subject “Test” and participants list with User B and User C as accepted. 3. User A selects User D to add to the session 4. Execute “Inviting new User to Group Chat” (C.5.2) with new User D added to the Group Chat 5. User A receives the participant list and the status for each one (User D as added/accepted and User B and User C as accepted). 6. User A leaves the Group Chat session. 7. Execute “Mobile Originated Session Termination” (C.3.1)

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

Runs On: MTC_IMS

System: SYSTEM_IMS

Verdicts:
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.5.5.4