Module Parameters
Data Types
Component Types
Port Types
Constants
Templates
Signatures
Functions
Altsteps
Test Cases
Group g_Mobile_Terminated_1_to_1_Chat
Declared in module RCS_Testcases
| Test Cases Summary |
| RCS_1_2_con_120 |
Verifies Mobile Terminated 1-to-1 Chat session establishment with Mobile Terminated session termination.
|
| RCS_1_2_con_121 |
Verifies Mobile Terminated 1-to-1 Chat session establishment with Mobile Originated session termination.
|
| RCS_1_2_con_122 |
Verifies Mobile Terminated 1-to-1 Chat session establishment when the sender is on the spam/blacklist.
|
| RCS_1_2_con_123 |
Verifies display notification in Mobile Terminated 1-to-1 Chat session.
|
| RCS_1_2_con_124 |
Verifies a duplicate session in a Mobile Terminated 1-to-1 Chat session
1.
|
| RCS_1_2_con_125 |
Verifies Mobile Terminated 1-to-1 Chat session race condition with new invite received after previous invite has been accepted
1.
|
| RCS_1_2_con_126 |
Verifies delivery of deferred messages in a Mobile Terminated 1-to-1 Chat session.
|
Details
RCS_1_2_con_120
testcase RCS_1_2_con_120() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies Mobile Terminated 1-to-1 Chat session establishment with Mobile Terminated session termination.
1. Execute “Mobile Terminated Session Establishment” (C.2.2) with the message “Hello A” from User B
2. User A receives “Hello A” from User B.
3. User A sends the message “Hello B” to User B before the session times out.
4. Execute “MSRP Session Message” (C.7.1) with the message “Hello B” from client A.
5. Execute “MSRP Session Message” (C.7.1) with the message “Bye A” from the Test Tool
6. User A receives an “Is Composing” indication from User B.
7. User A receives “Bye A” from User B.
8. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives “Hello A” from User B.
2. At step 6 User A receives an “Is Composing” indication from User B.
3. At step 7 User A receives “Bye A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4
RCS_1_2_con_121
testcase RCS_1_2_con_121() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies Mobile Terminated 1-to-1 Chat session establishment with Mobile Originated session termination.
1. Execute “Mobile Terminated Session Establishment” (C.2.2) with the message “Hello A” from User B
2. User A receives “Hello A” from User B.
3. User A sends the message “Hello B” to User B before the session times out.
4. Execute “MSRP Session Message” (C.7.1) with the message “Hello B” from client A.
5. Execute “MSRP Session Message” (C.7.1) with the message “Bye A” from the Test Tool
6. User A receives an “Is Composing” indication from User B.
7. User A receives “Bye A” from User B.
8. User A terminates the session.
9. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives “Hello A” from User B.
2. At step 6 User A receives an “Is Composing” indication from User B.
3. At step 7 User A receives “Bye A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4
RCS_1_2_con_122
testcase RCS_1_2_con_122() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies Mobile Terminated 1-to-1 Chat session establishment when the sender is on the spam/blacklist.
1. Execute “Mobile Terminated Session Establishment: Spam” (C.2.7) with the message “Spam for A” from User S
2. User A does not receive the message from User S.
3. The message “Spam for A” is available in the spam filter.
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
User A has User S listed in the spam/blacklist
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - During step 1 Client A sends a delivery notification with status “delivered” to Client S.
2. At step 2 User A does not receive the message from User S.
3. At step 3 the message “Spam for A” is available in the spam filter.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.15
RCS_1_2_con_123
testcase RCS_1_2_con_123() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies display notification in Mobile Terminated 1-to-1 Chat session.
1. Execute “Mobile Terminated Session Establishment: 1-to-1 Chat with display notification” (C.2.4) with the message “Hello A” from User B
2. User A receives “Hello A” from User B.
3. User A sends the message “Hello B” to User B before the session times out.
4. Execute “MSRP Session Message” (C.7.1) with the message “Hello B” from client A.
5. Execute “MSRP Session with Display Notification” (C.7.2) with the message “Bye A” from the Test Tool
6. User A receives “Bye A” from User B.
7. User A displays “Bye A” from User B.
8. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
User A’s device is configured to respond to display notification requests
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- The - pass-criteria are completely contained in the message flows in Appendix C.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.2.4
RCS_1_2_con_124
testcase RCS_1_2_con_124() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies a duplicate session in a Mobile Terminated 1-to-1 Chat session
1. Execute “Mobile Terminated Session Establishment: 1-to-1 Chat with two messages” (C.2.6) with the first message “Hello A” from User B and the second message “Wake up A” from User B.
2. User A receives “Hello A” from User B (but performs no action).
3. User A receives “Wake up A” from User B.
4. User A sends the message “Hello B” to User B before the session times out.
5. Execute “MSRP Session Message” (C.7.1) with the message “Hello B” from client A.
6. Execute “MSRP Session Message” (C.7.1) with the message “Bye A” from the Test Tool
7. User A receives “Bye A” from User B.
8. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives “Hello A” from User B.
2. At step 3 User A receives “Wake up A” from User B.
3. At step 7 User A receives “Bye A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.1
RCS_1_2_con_125
testcase RCS_1_2_con_125() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies Mobile Terminated 1-to-1 Chat session race condition with new invite received after previous invite has been accepted
1. Execute “Mobile Terminated Session Establishment: new INVITE race” (C.2.9) with the first message “Hello A” from User B and the
second message “Again A” from User B
2. User A receives “Hello A” from User B.
3. User A receives “Again A” from User B.
4. User A sends the message “Two B” to User B before the session times out.
5. Execute “MSRP Session Message” (C.7.1) with the message “Two B” from client A.
6. Execute “MSRP Session Message” (C.7.1) with the message “Bye A” from the Test Tool
7. User A receives “Bye A” from User B.
8. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives “Hello A” from User B.
2. At step 3 User A receives “Again A” from User B.
3. At step 7 User A receives “Bye A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.18.2
RCS_1_2_con_126
testcase RCS_1_2_con_126() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies delivery of deferred messages in a Mobile Terminated 1-to-1 Chat session.
1. User A comes online.
2. Execute “Mobile Terminated Session Store and Forward - deferred delivery” (C.2.12) with the first stored message “Hello A”
from User B and the second stored message “Again A” from User B.
3. User A receives an indication of the stored message “Hello A” from User B and may optionally receive an indication of the
stored message “Again A” from User B. User A opens the chat window.
4. Execute “MSRP Session Store and Forward Final Message Delivered” (C.7.5) with the stored message “Yet again A” from User B.
5. User A receives the stored message “Again A” from User B if not already received and then the message “Yet again A” from User B
and the session is closed.
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
User A is offline
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 User A receives an indication of the stored message “Hello A” from User B and optionally receives an indication
of the stored message “Again A” from User B.
2. At step 5 User A receives the stored message “Again A” from User B if not already received and then receives the stored message
“Yet again A” from User B and the session is closed.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.11, 3.2.4.19
© Copyright Testing Technologies IST GmbH 2013
provided by TTworkbench