Please enable JavaScript.
Coggle requires JavaScript to display documents.
smsmessaging (Invoke application provision call (Should be able to receive…
smsmessaging
Invoke application provision call
Should be able to receive a success response
Check 'sms_outbound_response' table
Should be able to add a new row
Invoke UPDATE call while selecting a row
Should be able to receive a success response
Check 'sms_outbound_response' table
Should be able to add a new row
Invoke a GET call to receive a selected row
Should be able to receive a success response with db results
Invoke a GET call to receive all saved data in 'sms_outbound_response' table
Should be able to see all data from 'payment_application' table
Invoke DELETE call while selecting a row id
Should be able to see 204 No content response
Check 'sms_outbound_response' table
Should be able to remove selected id from the table
Invoke MO/DN subscription call
Invoke UPDATE call while selecting that row
Should be able to receive proper error message. because while there is a subscription can't be update the row
Successfully start all services
Invoke DNSubscription using 'CAS' keyword and '8280' shortCode
Invoke Sendsms without 'notifyURL' and use 'CAS' keyword and '8280' shortCode
Should be able to notify to the notifyURL service
Check MS log(there should be Delivery Notification logs)
Down the delivery notification service(sp side)
Invoke Sendsms without 'notifyURL' and use 'CAS' keyword and '8280' shortCode
There should be a notification failure log on MS
Invoke Sendsms with 'notifyURL' and use 'CAS' keyword and '8280' shortCode
There should be a notification failure log on MS
Down smpp service(MS Client)
Invoke Sendsms without 'notifyURL' and use 'CAS' keyword and '8280' shortCode
There should be failure logs on MS
Check 'sms_outbound_response' table and should be able to see the NULL value for 'callback_data' and 'notify_url' fields
Invoke Sendsms without 'notifyURL' and use 'CAS' keyword and '8280' shortCode
Check 'sms_outbound_response' table and should be able to see the NULL value for 'callback_data' and 'notify_url' fields
Invoke Sendsms with 'notifyURL' and use 'CAS' keyword and '8280' shortCode
Should be able to receive a success response
Check notifuURL service. there should be a notification
Invoke Sendsms with 'notifyURL' and use 'CAS' keyword and '8280' shortCode
Should be able to notify to the notifyURL service
Check MS log(there should be Delivery Notification logs)
Down the delivery notification service(sp side)
Invoke Sendsms with 'notifyURL' and use 'CAS' keyword and '8280' shortCode
There should be a notification failure log on MS
Down smpp service(MS Client)
Invoke Sendsms with 'notifyURL' and use 'CAS' keyword and '8280' shortCode
There should be failure logs on MS
Check 'sms_outbound_response' table and should be able to see the NULL value for 'callback_data' and 'notify_url' fields
Invoke Sendsms without 'notifyURL' and use 'CAS' keyword and '8280' shortCode
Should be able to receive a success response
Check 'sms_outbound_response' table and should be able to see the NULL value for 'callback_data' and 'notify_url' fields
Invoke MOSubscription using 'CAS' keyword and '8280' shortCode
Invoke sendsms for staub
Should be able to receive a success response
Check MS log(there should be Delivery Notification logs)
Down the delivery notification service(sp side)
Check 'sms_inbound_request_backlog' table
Down smpp service(MS Client)
Should be able to receive failure response
Check all services are started successfully
Invoke DN subscription call
Do a small load test
Down the notification url while running the load
Tail the notification server(sp) and stop the load
Should be able to notify all queued response to the notify url
Down the back-end while running the load
Tail the notification server(sp) and start the back-end service
Should be able to receive response logs
Tail the notification server(sp)
Can't be able to receive a response
Down the ms2(smpp) service while running the load
Tail the notification server(sp)
Can't be able to receive a response
Tail the notification server(sp) and start the ms2(smpp) service
Should be able to receive response logs
Invoke MO subscription call
Invoke sendsms call from smsc
Down the notification url while running the invocations
Tail the notification server(sp) and stop the load
Should be able to notify all queued response to the notify url
Down the back-end while running the load
Tail the notification server(sp)
Can't be able to receive a response
Tail the notification server(sp) and start the back-end service
Should be able to receive response logs
Down the ms2(smpp) service while running the load
Tail the notification server(sp)
Can't be able to receive a response
Tail the notification server(sp) and start the ms2(smpp) service
Should be able to receive response logs
Invoke sendsms call from smsc
Should be able to insert data to the 'sms_inbound_request' table
Successfully start the sms back-end service
Successfully start and connect smpp ms2 back-end
Successfully start and connect ms1 with ms2(smpp)
Successfully start the AM server and connection establish with ms1
Insert a row to the 'application' table in iris_db with priority=1
Invoke sendsms call
Should be able to receive a success response
Successfully start the sms back-end service
Successfully start and connect smpp ms2 back-end2
Successfully start and connect ms1 with ms2(smpp)
Successfully start the AM server and connection establish with ms1
Insert a row to the 'application' table in iris_db with priority=2
Invoke sendsms call
Should be able to receive a success response
Successfully start the sms back-end service
Successfully start and connect smpp ms2 back-end
Successfully start and connect ms1 with ms2(smpp)
Successfully start the AM server and connection establish with ms1
Insert a row to the 'application' table in iris_db with priority=1
Down back-end service successfully
Invoke sendsms call
Should be able to receive a proper error message
Should queue the call on ms2(smpp)
Check all services are started successfully
Do a small load test
Down MS2 while running the load
Check 'sms_outbound_response' row count
Stop the load test
Start MS2
Check 'sms_outbound_response' row count
Evaluate row count from after and before got
Check all services are started successfully
Dow smpp service
Invoke sendsms call
view sms_outbound_response table
Should be able to see NULL value for 'message_id', 'notify_url' and 'callback_data' fields