Unit Test Plan Of SDDP_TextReqHandler

Module Name: SddpTextRequestHdlr

Function ID: 1 Function Name: Init

Function Overview: The function is called to intialize HashTable & Throttling Manager.
Function Inputs: None

Function Outputs: Returns status of initialization.

Configuration/Environment:

Positive Test Cases:

Sr. No. Description Expected Result

1.1.1 HashTable object initalization Success It should produce
appropriate logs &
continues further.
1.1.2 Throttling Manager object initialization Success It should produce
appropriate logs &
continues further.

1.1.3 Init call returns success when both HashTable & Initialisation Success
Throttling Manger initilization succeeds Returns true with
appropriate Logs.

Negative Test Cases:

Sr. No. Description Expected Result
1.2.1 Init call returns false when either of Hashtable or Process intialization
Throttling Manager initialization fails. It drops the request. Failed.Returns false with
appropriate error logs &
traces.

1.2.2
1.2.3

Function ID: 2 Function Name: DecodeTextMessage

Function Overview: The function decodes all URL parameters. The various request parameters are UserName, Passwd, Orig
Dcs, Message, & Guaranteed. It checks for OrigAddr whether it is numeric or alphanumeric.

Function Inputs: Requested URL

Function Outputs: Decoding Success or Failure
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result
2.1.1 It decodes each URL parameters in which UserName, Each parameters should
Passwd, OrigAddr, DestAddr, Dcs & Message are be correct.It should
mandatory parameters.Dsr, Guaranteed parameters are populate decoded
optional. parameters. Continues with
appropriate logs & traces

2.1.2 It checks for OrigAddr whether it is Numeric or Accordingly Sets the flag.
Alphanumeric.

2.1.3
2.1.4

Negative Test Cases:

Sr. No. Description Expected Result
2.2.1 If any of Mandatory parameters are missed or expected Returns false with
URL Keywords for each parameters mismatch then appropriate error
generates error messages to user & drops the request. messages & error codes to
the user.Generates error
logs & traces.

2.2.3

Function ID: 3 Function Name: ProcessTextMessage

Function Overview: This function fetches the application information from ApplicationInfo shared memory(Hash Table). Perfo
applies the throttling. If both results in success then forms the request & sends it to the validation queue for further processing

Function Inputs: SMSRequest, AppShmDetails structures.

Function Outputs: Status of processing Request.
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result
3.1.1 With the decoded UserName it fetches the application I should populate
details from Hash Table(ApplicationInfo SHM).Gets the AppShmDetails structure.
stucture AppShmDetails

3.1.2 It applies the throttling using app_Id contained in If throttling not exceeded,
AppShmDetails to check whether throttling limit exceeded continues for further
or not. processing

3.1.3 It validates the password present in AppShmDetails with if success continues for
that of the decoded URL password. further processing
3.1.4 Formats the SMSRequest Structure using all decoded continues further by
parameters populating SMSRequest
structure with appropriate
logs

3.1.5 It writes the SMSRequest structure to Validation queue Returns True with
"MSG_VAL_REQ_QUEUE_RCV " with SessionId as appropriate logs
Message Type.

3.1.6
3.1.7

Negative Test Cases:

Sr. No. Description Expected Result
3.2.1 If it fails to fetch the application details from HashTable, it Returns false with
produces a error message "User Invalid/Inactive " & appropriate logs. Produces
drops the request. Error message along with
error code.

3.2.2 If user is inactive or throttling limit for the application Returns false with
exceeded, then it produces a error message "Incorrect appropriate logs. Produces
User/ Inactive User" & drops the request.. Error message along with
error code.

3.2.3 If password is not valid then it produces a error message Returns false with
"Invalid Password" & drops the request. appropriate logs. Produces
Error message along with
error code.

Returns false with

appropriate logs. Produces
If fails to send the SMSRequest to validation queue it Error message along with
3.2.4 produces appropriate logs error code.

Function ID: 4 Function Name: ReadResponse

Function Overview: Reads the response sent from Validation response queue. It checks for the messageId in SMSRespose
displays the "Message Id " as response indicating Message is accepted. Otherwise displays Message Not Accepted.

Function Inputs: SMSResponse structure

Function Outputs: Message Id

Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result
4.1.1 It Reads the SMSResponse structure from Validation Success to read response
response queue "MSG_VAL_RSP_QUEUE_RCV" with continues with logs further.
message type as SessionId.
4.1.2 It checks for the Message Id in SMSResponse structure.If Displays Message Id
found sends positive response

Negative Test Cases:

Sr. No. Description Expected Result
4.2.1 If fails to read the response Returns false with
appropriate logs
4.2.2 If Message Id not found (zero) sends nagative response Termiates by producing
displaying Message Not Accepted. error message & error
code.

4.2.3
xtReqHandler

e: Init
r.

Observation Remarks
Success

OK
Success

OK
Produces Logs & traces
for successful
initialization.
OK

Observation Remarks
Generating error Logs &
traces.

e: DecodeTextMessage
parameters are UserName, Passwd, OrigAddr, DestAddr, Dsr,
meric.

Observation Remarks
 Generating Logs &
populating decoded
parameters success.

OK
success to produce the
expected result.

OK

Observation Remarks
success to produce the
expected result.

OK

e: ProcessTextMessage
nInfo shared memory(Hash Table). Performs user validation &
e validation queue for further processing.

Observation Remarks
Populating
AppShmDetails structure.

OK
success to produce the
expected result.

OK
success to produce the
expected result.

OK
 Populating SMSRequest
structure.

OK
success to write.

OK
OK

Observation Remarks
Appropriate Error
message & erroe code
displayed. Also logs are
generated.

Appropriate Error
message & erroe code
displayed. Also logs are
generated.

Appropriate Error
message & erroe code
displayed. Also logs are
generated.

Appropriate Error
message & erroe code
displayed. Also logs are
generated.

e: ReadResponse
cks for the messageId in SMSRespose structure. If found
splays Message Not Accepted.

Observation Remarks
Read Response success

OK
Message displayed.

OK

Observation Remarks
Expected result observed.
OK
Success to display the
message.

OK
 Unit Test Plan Of SDDP_BinaryReqHandler

Module Name: SddpBinaryRequestHdlr

Function ID: 1 Function Name: Init

Function Overview: The function is called to intialize HashTable & Throttling Manager.
Function Inputs: None
Function Outputs: Returns status of initialization.
Configuration/Environment:
Positive Test Cases:

Sr. No. Description Expected Result

1.1.1 HashTable object initalization Success It should produce
appropriate logs &
continues further.
1.1.2 Throttling Manager object initialization Success It should produce
appropriate logs &
continues further.
1.1.3 Init call returns success when both HashTable & Initialisation Success
Throttling Manger initilization succeedes Returns true with
appropriate Logs.

1.1.4
1.1.5
1.1.6 .

Negative Test Cases:

Sr. No. Description Expected Result
1.2.1 Init call returns false when either of Hashtable or Process intialization
Throttling Manager initialization fails. It drops the Failed.Returns false with
request. appropriate error logs &
traces.

1.2.2
1.2.3

Function ID: 2 Function Name: DecodeBinaryMessage

Function Overview: The function decodes all URL parameters. The various request parameters are UserName, Passwd, Orig
DestAddr, Inputs:
Function Udh.DsrRequested
& Message(UserData).It
URL checks for OrigAddr whether it is numeric or alphanumeric.It aslo checks for Udh,
is ' 0 ' thenOutputs:
Function it treats the message
Decoding as Textormessage
Success Failure & processes further. Else it treats the message as Binary message.
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result
2.1.1 It decodes each URL parameters in which UserName, Each parameters should
Passwd, OrigAddr, DestAddr, Udh & Message are be correct.It should
mandatory parameters.Dsr parameter is optional. populate decoded
parameters. Continues
with appropriate logs &
traces

2.1.2 It checks for OrigAddr whether it is Numeric or Accordingly Sets the

Alphanumeric. flag.

2.1.3 If Udh is not zero (0) then it processes the message as Continues with further
binary message else as normal Text message. processing
2.1.4

Negative Test Cases:

Sr. No. Description Expected Result
2.2.1 If any of Mandatory parameters are missed or expected Returns false with
URL Keywords for each parameters mismatch then appropriate error
generates error messages to user & drops the request. messages & error codes
to the user.Generates
error logs & traces.

2.2.2
2.2.3
9
Function ID: 3 Function Name: ProcessBinaryMessage
Function Overview: This function fetches the application information from Application Info shared memory(Hash Table). Perfo
user validation & applies the throttling. If both results in success then forms the request & sends it to the validation queue for f
processing.

Function Inputs: SMSRequest, AppShmDetails structures.

Function Outputs: Status of processing Request.
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result
3.1.1 With the decoded UserName it fetches the application I should populate
details from Hash Table(ApplicationInfo SHM).Gets the AppShmDetails
stucture AppShmDetails structure.

3.1.2 It applies the throttling using app_Id contained in If throttling not

AppShmDetails to check whether throttling limit exceeded, continues for
exceeded or not. further processing

3.1.3 It validates the password present in AppShmDetails with if success continues for
that of the decoded URL password. further processing
3.1.4 Formats the SMSRequest Structure using all decoded continues further by
parameters populating SMSRequest
structure with
appropriate logs

3.1.5 It writes the SMSRequest structure to Validation queue Returns True with
"MSG_VAL_REQ_QUEUE_RCV " with SessionId as appropriate logs
Message Type.
3.1.6
3.1.7

Negative Test Cases:

Sr. No. Description Expected Result
3.2.1 If it fails to fetch the application details from HashTable, Returns false with
it produces a error message "User Invalid/Inactive " & appropriate logs.
drops the request. Produces Error
message along with
error code.

3.2.2 If user is inactive or throttling limit for the application Returns false with
exceeded, then it produces a error message "Incorrect appropriate logs.
User/ Inactive User" & drops the request.. Produces Error
message along with
error code.

3.2.3 If password is not valid then it produces a error Returns false with
message "Invalid Password" & drops the request. appropriate logs.
Produces Error
message along with
error code.

Returns false with

appropriate logs.
Produces Error
If fails to send the SMSRequest to validation queue it message along with
3.2.4 produces appropriate logs error code.

Function ID: 4 Function Name: ReadResponse

Function Overview: Reads the response sent from Validation response queue. It checks for the messageId in SMSRespose
structure. If found displays the "Message Id " as response indicating Message is accepted. Otherwise displays Message Not
Accepted.

Function Inputs: SMSResponse structure

Function Outputs: Message Id
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result
4.1.1 It Reads the SMSResponse structure from Validation Success to read
response queue "MSG_VAL_RSP_QUEUE_RCV" with response continues with
message type as SessionId. logs further.

4.1.2 It checks for the Message Id in SMSResponse Displays Message Id

structure. If found sends positive response

Negative Test Cases:

Sr. No. Description Expected Result
4.2.1 If fails to read the response Returns false with
appropriate logs
4.2.2 If Message Id not found (zero) sends nagative response Termiates by producing
displaying Message Not Accepted. error message & error
code.

4.2.3
 yReqHandler

me: Init
nager.

Observation Remarks
Success

OK
Success

OK
Produces Logs &
traces for successful
initialization.

OK
OK
OK
OK

Observation Remarks
Generating error
Logs & traces.

me: DecodeBinaryMessage
est parameters are UserName, Passwd, OrigAddr,
meric or alphanumeric.It aslo checks for Udh, if udh
ats the message as Binary message.

Observation Remarks
 Generating Logs &
populating decoded
parameters
success.

OK
success to produce
the expected result.

Need to be clarified.

OK

Observation Remarks
success to produce
the expected result.

OK

me: ProcessBinaryMessage
ation Info shared memory(Hash Table). Performs
equest & sends it to the validation queue for further

Observation Remarks
Populating
AppShmDetails
structure.

OK
success to produce
the expected result.

OK
success to produce
the expected result.
OK
 Populating
SMSRequest
structure.

OK
success to write.

OK
OK

Observation Remarks
Appropriate Error
message & erroe
code displayed.
Also logs are
generated.

Appropriate Error
message & erroe
code displayed.
Also logs are
generated.

Appropriate Error
message & erroe
code displayed.
Also logs are
generated.

Appropriate Error
message & erroe
code displayed.
Also logs are
generated.

me: ReadResponse
checks for the messageId in SMSRespose
ccepted. Otherwise displays Message Not

Observation Remarks
Read Response
success

OK
Message displayed.

OK

Observation Remarks
Expected result
observed.
Success to display
the message.
 Unit Test Plan cum Report

Module Name: SDDP_AppInfoCreator

PARAMETERS TO BE CONFIGURED BEFORE STARTING PROCESS

Connection Details must be configured in

1
CONNECTION_MASTER table

All Application Parameters must be configured

2 in APPLICATION_CONFIG table &
MODIFIED_FLAG must be set to 1.

For SMPP/CIMD2 accounts the

3 SMPP_CIMD2_APPLICATION_DETAILS table
must be populated.

Function ID: 1 Function Name: Init

Function Overview: The function is called during the start up of the process .the process initializes the Dbmanager
object ,Application Shared memory ,Throttling Shared memory and Resets the Throttle Shared memory.

Function Inputs:
Function Outputs: Initializes the Application Shared memory and Throttling Shared memory .
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
1.1.1 Initializes the Application Shared Memory Reads Shared Memory Success
keys and creates the
shared Memory

1.1.2 Initializes the Throttling Shared Memory Reads Shared Memory Success
keys and creates the
shared Memory

1.1.3 Resets the complete Throttling shared memory Resets the values to Throttling Library
zero function should
generate logs and
traces.

Negative Test Cases:

Sr. No. Description Expected Result Observation
1.2.1 If the Application Shared Memory already exists Fails to create Shared Success
memory and attaches
to the existing shared
memory.
1.2.2 If the Throttling Shared Memory already exists Fails to create Shared Success
memory and attaches
to the existing shared
memory.

Function ID: 2 Function Name: CreateAppinterfaceConfg

Function Overview: The function gets the current time of the system ,takes the backup of the existing files with
timestamp and fetches the required details from connection master table from database and creates the
appinterface.cfg file

Function Inputs: ConnectionDetails

Function Outputs: File Creation success/fail
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
2.1.1 Moves all existing files to backup directory Success Success
2.1.2 Fetches the connection Details and Populates the Success Success
ConnectionDetails Structure
2.1.3 Creates the appinterface.cfg file with the structure Success Success
parameters

Negative Test Cases:

Sr. No. Description Expected Result Observation
2.2.1 If Failed to move the existing files to backup Fail/False Generatiing traces
directory saying failed to move.
2.2.2 If failed to fetch the connection Details from No_Record Found Creates the
CONNECTION_MASTER table and populate the Error appinterface file with all
ConnectionDetails Structure values '0'.
2.2.3 If appinterface.cfg file already exists Fails to create new file Success

Function ID: 2.a Function Name: MoveExisting File

Function Overview: Moves the existing files i.e. apponterface.cfg,Application wise files and dest rule files to a backu
directory with file name concatenated with current time.

Function Inputs: None

Function Outputs: Moves all the files to a bachkup directory and removes the old files from current directory
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
3.1.1 Renames Application directory as Application Success Success
_time concatenated with current time
3.1.2 Moves the renamed directory to backup folder Success Success
3.1.3 Removes all files from Applicatons directory Success Success
3.1.4 Renames appdestrule directory as appdestrule Success Success
_time concatenated with current time
3.1.5 Moves the renamed directory to backup folder Success Success
3.1.6 Removes all files from appdestrule directory Success Success

Negative Test Cases:

Sr. No. Description Expected Result Observation
3.2.1 Failed to rename and move the files/folders Print traces. Print traces.

Function ID: 2.b Function Name: Fetch Connection Details

Function Overview: Fetches the Connection parametes from connectionmaster table from database and populates to
ConnectionDetails structure

Function Inputs: None

Function Outputs: Status of Database fetch
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
4.1.1 Selects ip,port,protocol,session_init_timer_timeout Success Success
parameters from connection master table and
populates into ConnectionDetails Structure

Negative Test Cases:

Sr. No. Description Expected Result Observation
4.2.1 If failed to select the No_Record Success
ip,port,protocol,session_init_timer_timeout Found ,returns true
parameters from connection master table and
populates into ConnectionDetails Structure

Function ID: 3 Function Name: UpdateAppinterfaceConfg

Function Overview: Fetches appinterface.cfg related parameters from application_config table from database aand
populates the same into appinterface.cfg file
Function Inputs: None
Function Outputs: Populates AppShmDetails Structure and populates the same in appinterface.cfg file
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
5.1.1 Selects name ,password,generic_app- Success Success
flag,Interface from application_config table and
populates AppShmDetails structure
5.1.2 Populated appinterface.cfg file with data fetched Success Success
from APPLICATION_CONFIG table.

Negative Test Cases:

Sr. No. Description Expected Result Observation
5.2.1 If failed to select name ,password,generic_app- No Data Found ,returns
flag,Interface from application_config table and false
populates AppShmDetails structure
5.2.2 If failed to copy the populated structure to returns false
appinterface.cfg file

Function ID: 4 Function Name: FetchMaxThrottle

Function Overview: Fetches the Max Throttle Values for each interface type and populates the Throttle shared
Memory
Function Inputs: None
Function Outputs: Populates the Throttle Shared Memory with max Throttle Values for each interface
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
6.1.1 Fetches the max throttle value from config_main Return Success Success
table
6.1.2 Populates the fetched values to AppThrottle Return Success Success
Structure
6.1.3 Inserts the populated structure into Throttling Return Success Success
Shared Memory

Negative Test Cases:

Sr. No. Description Expected Result Observation
6.2.1 If failed to fetch the max throttle value from Return False Success
config_main table
6.2.2 If failed to populate the fetched values to Return False Success
AppThrottle Structure
6.2.3 If failed to insert the populated structure into Return False Success
Throttling Shared Memory

Function ID: 4.a Function Name: FetchConfigDetails

Function Overview: Fetch Max Throttle Values for different interface from Config_main table from database

Function Inputs: None

Function Outputs: populates the AppThrottle Structure
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
7.1.1 Fetches the application related parameters from Return Success Success
application_config and SMPP/CIMD2 table from
database
7.1.2 Return Success Success
7.1.3 Return Success Success

Negative Test Cases:

Sr. No. Description Expected Result Observation
7.2.1 If failed to fetche the application related
parameters from application_config and
SMPP/CIMD2 table from database
7.2.2
7.2.3

Function ID: 4.b Function Name: InsertAppDetailsinShm

Function Overview: Inserts the populated AppThrottle Structures into Throttling Shared Memory

Function Inputs: None

Function Outputs:
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
8.1.1 Inserts the populated structure into Application Return Success Success
Shared memory
8.1.2 Return Success
Cimd2ProtocolHandler
object
8.1.3 Return NULL Success

Negative Test Cases:

Sr. No. Description Expected Result Observation
8.2.1
8.2.2
8.2.3

Function ID: 5 Function Name: FetchConfigData

Function Overview: Fetches the application wise parameters from Db and populates respective structue

Function Inputs: None

Function Outputs: populates AppShmDetails and SmppCimd2 Structures
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
9.1.1 Fetches the various application related information Return Success Success
from application_config table
9.1.2 If interface is SMPP/CIMD2 fetches the other Return Success Success
parameters from SMPP_CIMD2Application details
table
9.1.3 Populates the respective structure Return Success Success

Negative Test Cases:

Sr. No. Description Expected Result Observation
9.2.1 If failed to fetch the various application related Return False
information from application_config table
9.2.2 If interface is SMPP/CIMD2 and failed to fetch the Return False
other parameters from SMPP_CIMD2Application
details table
9.2.3 If failed to populate the respective structure Return False

Function ID: 5.b Function Name: FetchAppDetails

Function Overview: Fetches the application wise parameters from Application_config table and depending on the
interface type 2 or 3 fetches SMPP/CIMD2 related parameters from SMPP_SIMD2_APPLICATION_DETAILS and
populates respective structure.
Function Inputs: None
Function Outputs: Populates AppShmDetails ans SmppCimd2 Structures
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
10.1.1 Fetches the application related values from Db Return true Success
tables Application_config,SMPP_CIMD2
Application Details
10.1.2 populates the AppShmDetails and SMPPCimd2 Returns true Success
Structure

Negative Test Cases:

Sr. No. Description Expected Result Observation
10.2.1
10.2.2
10.2.3

Function ID: 6 Function Name: CreateShmAndFiles

Function Overview: Creates All Applications in Shared Memory and creates application wise cfg files and destrule
files

Function Inputs: None

Function Outputs: Creates Application sharedmemory and files
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
11.1.1 Creates Shared memory and files Returns false

Negative Test Cases:

Sr. No. Description Expected Result Observation
11.2.1
11.2.2
11.2.3

Function ID: 6.a Function Name: CreateAllApplicationInSharedMem

Function Overview: Inserts the Application wise informations into Throttle Shared Memory and Application Shared
memory and Creates DestRule Files .If the interface type is SMPP/CIMD2 the creates the listener application files

Function Inputs: None

Function Outputs: Populates the sharedmemory and creates DestRule files and listener Files
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
12.1.1 Creates Throttling Shared Memory
12.1.2 Creates Application Shared Memory
12.1.3 If Interface is SMPP/CIMD2

Negative Test Cases:

Sr. No. Description Expected Result Observation
12.2.1 Creates Throttling Shared Memory
12.2.2 Creates Application Shared Memory
12.2.3 If Interface is SMPP/CIMD2

Function ID: 6.b Function Name: CreateListenerFiles

Function Overview: If the interface is SMPP/CIMD2 then creates files with application names and populates applicatio
wise information into those files

Function Inputs: None

Function Outputs: Creates Application wise files
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
13.1.1 Creates files with application names and copies
the populated structure to the file

Negative Test Cases:

Sr. No. Description Expected Result Observation
13.2.1
13.2.2
13.2.3

Function ID: 6.c Function Name: CreateDestRuleFiles

Function Overview: Creates files with application names in appdestrule directory and copies SampleDestRule.cfg file
to the newly created files

Function Inputs: None

Function Outputs: Creates Applicationwise Destination Rule files
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation
14.1.1 Creates files with application names and copies
the SampleDestRule files to the file
Negative Test Cases:
Sr. No. Description Expected Result Observation
14.2.1
14.2.2
14.2.3
S

the Dbmanager
ory.

Remarks

OK

OK
According to
Code no
failure logs
were
observed.

Remarks
 OK

OK

ceConfg
existing files with
creates the

Remarks
OK

OK

OK

Remarks

OK

OK

OK

e
dest rule files to a backup

urrent directory

Remarks
 OK
OK
OK

OK
OK
OK

Remarks
OK

n Details
tabase and populates to

Remarks

OK

Remarks

OK

ceConfg
e from database aand

ace.cfg file

Remarks
 OK

OK

Remarks

e Throttle shared

nterface

Remarks

OK

OK

Remarks

OK

OK

OK

ls
rom database
 Remarks

OK
OK
OK

Remarks

Shm
ory

Remarks

OK

OK

Remarks

ve structue
 Remarks

OK

OK
OK

Remarks

nd depending on the
ON_DETAILS and

Remarks

OK

OK

Remarks

es
cfg files and destrule
 Remarks

Remarks

onInSharedMem
nd Application Shared
ner application files

Remarks

Remarks

s
and populates application

Remarks
 Remarks

es
SampleDestRule.cfg file

Remarks

Remarks
 Unit Test Plan Of SDDP_Translator

Module Name: SDDP_Translator

Function ID: 1
Function Overview: Initializes DataBase, Hash Table, Throttle Manager and Reference Directory. Fetch all user details from

Function Inputs: None

Function Outputs: Status of Process Initilalization
Configuration/Environment: MAX_REF_ENTRIES value set between 1-300
Positive Test Cases:
Sr. No. Description
1.1.1 Init DbManager success
1.1.2 Init HashTable success
1.1.3 Init ThrottleManager success
1.1.4 Init SddpReferenceDirectory with MAX_REF_ENTRIES
success
1.1.5 Fetch User Details(APP_ID,APP_NUM,NAME) for
SMPP/CIMD2 interface from DataBase success
Negative Test Cases:
Sr. No. Description
1.2.1 Init DbManager failed
1.2.2 Init HashTable failed
1.2.3 Init ThrottleManager failed
Init SddpReferenceDirectory with MAX_REF_ENTRIES
1.2.4 failed
Fetch User Details(APP_ID,APP_NUM,NAME) for
SMPP/CIMD2 interface from DataBase failed(return of
1.2.5 DB_NO_RECORD_FOUND_ERR)

Function ID: 2
Function Overview: The function Reads Request from Listener in blocking mode
Function Inputs:
Function Outputs: Success/failure to Read Request
Configuration/Environment:
Positive Test Cases:
Sr. No. Description
2.1.1 Read Request message from Listener Queue success

2.1.2 Received Submit Message

2.1.3 Received Query Message

2.1.4 Received Cancel Message

2.1.5 Received Replace Message

Negative Test Cases:
Sr. No. Description
2.2.1 Read Request message from Listener Queue failed

2.2.2 Received Invalid Operation

Function ID: 3
Function Overview: This function checks for valid user and Operation/Message type. For SubmitSM the process reduces thro
constructs kernel structure and write message to validation queue. If write message to validation queue fails/ReduceThrottle fa
SubmitNACK to Listener. For QuerySM, CancelSM and ReplaceSM write message to Query Handler Queue.

Function Inputs: None

Function Outputs: Status of the Request
Configuration/Environment:
Positive Test Cases:
Sr. No. Description
3.1.1 Check For Valid User success
3.1.2 For ASE_SUBMIT operation ReduceThrottle success

3.1.4 For ASE_QUERY/ ASE_CANCEL/ASE_REPLACE

operation
3.1.3 Write Request message to MSG_VAL_REQ_QUEUE_RCV
for ASE_SUBMIT success

3.1.4 For ASE_QUERY/ ASE_CANCEL/ASE_REPLACE

operation
3.1.5 Write Request message to for MSG_QRY_CAN_RCV_Q
ASE_QUERY/ ASE_CANCEL/ASE_REPLACE operation is
success

Negative Test Cases:

Sr. No. Description
3.2.1 Check For Valid User fails

3.2.2 For ASE_SUBMIT operation ReduceThrottle fails

3.2.3 If failed to write submit message to validation queue .

3.2.4 If failed to write ASE_QUERY/

ASE_CANCEL/ASE_REPLACE message to
MSG_QRY_CAN_RCV_Q
Function ID: 3(a)
Function Overview: Checks whether user is valid to send msg based on status
Function Inputs: None
Function Outputs: Status of User
Configuration/Environment:
Positive Test Cases:
Sr. No. Description
3(a).1.1 Get User Details from Reference Directory with the AppNum
success
3(a).1.2 Get Application Details from HashTable success

Negative Test Cases:

Sr. No. Description
4.2.1 Get User Details from Reference Directory with the AppNum
fails
4.2.2 Get Application Details from HashTable fails
4.2.3 If User is in Deactivated state

Function ID: 3(b)

Function Overview: Converts Generic Ase Structure into Kernel Structure
Function Inputs: None
Function Outputs: None
Configuration/Environment: Variable specified in gateway.env should be set.
Positive Test Cases:
Sr. No. Description
3(b).1.1 Constucts kernel structure

Negative Test Cases:

Sr. No. Description
3(b).2.1
Test Plan Of SDDP_Translator

Function Name: Init

ottle Manager and Reference Directory. Fetch all user details from DataBase to Reference Directory.

set between 1-300

Expected Result Observation Remarks

Should continue with initialization Success OK
Should continue with initialization Success OK
Should continue with initialization Success OK
Should continue with initialization Success
OK
Insert User Details into Reference Directory Success
and continue with initialization OK

Expected Result Observation Remarks

Should return failure with appropriate log
Should return failure with appropriate log
Should return failure with appropriate log
Should return failure with appropriate log

Should Continue initialization with approprate

log

Function Name: ReadRequest

ener in blocking mode

Expected Result Observation Remarks

Check for the type of operation/Message type Success
and continue the process OK
Copy OA, DA and firstdeliverytime and Success
continue to Process Request OK
Copy OA, DA and Servicecentertime continue Success
to Process Request OK
Copy OA, DA and Servicecentertime continue Success
to Process Request OK
Copy OA, DA and firstdeliverytime and Success
continue to Process Request OK
 Expected Result Observation Remarks
Handle Q Read Failure and print appropriate Success
Logs and return false OK
Return failure with appropriate log. Continue to Success
read next request OK

Function Name: Process Request

Operation/Message type. For SubmitSM the process reduces throttle value with the Appid is success ,
queue. If write message to validation queue fails/ReduceThrottle fails then process sends a
placeSM write message to Query Handler Queue.

Expected Result Observation Remarks

Continue to check for operation Success OK
Construct kernel structure with approprate log Success
and continue OK
Construct kernel structure with approprate log Success
and continue OK
Request processed with approprate log. Success
Continue to process next request
OK
Construct kernel structure with approprate log Success
and continue OK
Request processed with approprate log. Success
Continue to process next request
OK

Expected Result Observation Remarks

Should return failure with appropriate log. Success (This case is
Continue to process next request. tested using stub) OK
Should return failure.Checks the interface for Success (Tested for
appropriate error code and send Submit SMPP account only)
NACK with that error code
SMPP_ESME_RTHROTTLED for SMPP and
CIMD2_SUBMIT_MESSAGE_ERROR_CODE
_LICENCE_EXCEEDED for CIMD2 accounts.
Continue to process next request.
OK
Should return failure and Send Submit NACK Success
with error code SC_SYS_FAIL_ERR.
Continue to process next request. OK
Should return failure with appropriate log. Success
Continue to process next request.
OK
 Function Name: CheckForValidUser
msg based on status

Expected Result Observation Remarks

Continue process. Success
OK
Should Return success if status of user is Success
active with appropriate log(if AllLogsReq=1) OK

Expected Result Observation Remarks

Should return failure with appropriate log. Success
OK
Should return failure with appropriate log. Success OK
Should return failure with appropriate log(if Success
AllLogsReq=1). OK

Function Name: ConstructKernelStructure

ernel Structure

.env should be set.

Expected Result Observation Remarks

Continue process with appropriate log. Success OK

Expected Result Observation Remarks

 Unit Test Plan Of SDDP_Validation

Module Name: SDDP_Validation

Function ID: 1 Function Name: Init

Function Overview: The function is called during startup , used to initialize the Application Shared memroy object and Client Shared memory object.
Also initializes the destination rule object.

Function Inputs:

Function Outputs: Attaches to the Application Shared memory and Client Shared memory. Creates destination rule analysis table.

Configuration/Environment: env's from sddp.env must be set

Positive Test Cases:

Sr. No. Description Expected Result Observation
1.1.1 Read All Application details into AppShmDetails structure from Structure copied as it is. All application details
Application Shared memory. present in Application
shared memory will be
copied to structure.
1.1.2 Call Destrule object initialization and creates an analysis table Initialization and creation Initialized and created the
according application wise configured destrules. of analysis table success. analysis table.

1.1.3 Initializes the default destination rule object and creates the Initialization and creation Initialized and created the
default analysis table. of analysis table success. default analysis table.

1.1.4 Init call returns success Process initializaiton Process initializaiton

successful. successful.

Negative Test Cases:

Sr. No. Description Expected Result Observation
1.2.1 Failed to initialize the process when Queue Keys are not Process should exit. Process exited, giving
configured or missing. proper error cause.
1.2.2 Failed to initialize the DestRule object when there are no Process should exit. Process should exit.
corresponding files present in the appdestrule directory for the
applications configured in Application shared memory.
Function ID: 2 Function Name: ValidateOrigDispAddr
Function Overview: The function is called to validate the Origination Address on the basis of sender Id.
Function Inputs:
Function Outputs:
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation
2.1.1 Validates the Origination Address based on mode configured. 0 - NO_VALIDATION : Allowing messages if
In this mode the process mode is configured as ' 0'.
allow the Sender without
any validation.
Allows only messages with
1 - WL_DISPNAME : Whitelisted display names,
The process should otherwise drops the
allow the message if the message giving proper
Orig Address (Display reason.
Name) present in the
message matches with
the whitelisted names. Disallow messages with
display names matching to
2 - BL_DISPNAME : blacklisted names,
The process should otherwise allow the
disallow the message if messages.
the Orig Address
matched with Blacklisted
names configured.

Negative Test Cases:

Sr. No. Description Expected Result Observation
2.2.1
Function ID: 3 Function Name: ReadAndHandleMsg
Function Overview: The function reads messages from the validation receive queue and fetch the application information based on name received.

Function Inputs: SMSRequest Structure.

Function Outputs: AppShmDetails structure.
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation
3.1.1 Read message from MSG_VAL_REQ_QUEUE_RCV in blocking Read should become Read success.
mode with message Type 0. successful.
3.1.2 Fetch Application details from the application shared memory and Fetch should be Fetch success.
populates the structure AppShmDetails. successful.

Negative Test Cases:

Sr. No. Description Expected Result Observation
3.2.1 Read get failed if the structure is different other than SMSRequest Process should handle Process handled failure
Struct. queue read failure and sitaution and logs are
prints logs. generated.
3.2.2 Application details fetch fail , due to wrong application name sent Generates logs and Process handled failure
in the request. Also the same situation can be occurred when drops the message giving sitaution, generated logs
there is no application details present in Application Shared error and dropped the message.
memory. VAL_SC_SYS_FAIL_ER
R.

Function ID: 4 Function Name: ValidateDestNum

Function Overview: The process apply the destination rules configured application wise or default rules if no application wise rules are defined.

Function Inputs: SMSRequest

Function Outputs: return true/false.
Configuration/Environment: env specified in sddp.env must be set.

Positive Test Cases:

Sr. No. Description Expected Result Observation

4.1.1 Check for the invalid characters in the destination address. If check is success allow Allowing messages for
the message for further further processing.
processing, otherwise In case of failure dropping
drop the message giving message giving proper
VAL_INV_SME_ADDR_E reason.
RR error.

4.1.2 Check and Apply application wise destination rules for the Allow/Disallow the Allowing messages for
destination received in the message. destination as configured processing.
in application wise dest Diallowing messages
rules. giving proper reason
VAL_DEST_SME_BARRE
D_ERR.

4.1.3 If no rules are found matching to the destination address received Allow/Disallow the Allowing messages for
then apply default rules. destination as configured processing.
in default dest rules.
Even if no rules matched from Default rules configured then the Diallowing messages
message will be dropped if its configured to drop. giving proper reason
VAL_DEST_SME_BARRE
D_ERR.

Dropping messages when

no rule if matched and
DropIfNoRule flag is set.

Negative Test Cases:

Sr. No. Description Expected Result Observation
4.2.1 Destination rule applying may fail when invalid app_id is sent in Process exits. Process exiting due to
the request. segmentation fault.

4.2.2
4.2.3

Function ID: 5 Function Name: ProcessMsg

Function Overview: Processes the message for VP, Deferred delivery and Call AcceptMsg API to generate the message Id and scts and send Submit
response.

Function Inputs: SMSRequest

Function Outputs: SMSResponse structure / AseResponse struct.

Configuration/Environment:

Positive Test Cases:

Sr. No. Description Expected Result Observation
5.1.1 Checks the Validity period field of the message and if its empty Process should check Process puts default VP of
fills the default system VP in the same. and allow the VP if its not the system if VP is found
null. NULLL in the request.
If VP is not present then
apply the default system
VP.

5.1.2 Process should forward

Check for the deferred message based on firstdelivery time the message to actual
present in Submit message and if its greater than current time SMSC through Process is forwarding the
then forwards the message to actual SMSC for delivery. SmsForwarder. message to actual SMSC.
5.1.3 Then call AcceptMsg() which will allocates message Id for every Process should allocates Allocates Message Id &
message. The format is the message Id and SCTS for each message.
INSTANCEAPPIDMMDDhhmmssms. SCTS for every message. Process submtting
This api will then send back the Submit response to the Send Submit message to message to the
application. the application. application.

Negative Test Cases:

Sr. No. Description Expected Result Observation
5.2.1
5.2.2
5.2.3

Function ID: 6 Function Name: AcceptMsg()

Function Overview: Allocates message Id and SCTS for every message and validates for the GU/NGU and SR request. Backup the message to
Database.
Function Inputs: SMSRequest struct.

Function Outputs: SMSRequest struct and SMSResponse/AseResponse.

Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation
6.1.1 Should allocates message ID & SCTS for each message and Process should allocate Process allocating
send SUBMIT_ACK message to the application. The process can message Id & SCTS. message Id & SCTS.
write ack to 2 different queues based on interface type, also the
structure will vary. Process should Check Checking GU/NGU and
GU/NGU and SR SR flag.
For SMPP/CIMD2 applications uses requested or not.
MSG_ASE_LSTNR_TX_RSP queue and AseResponse structure. Writing correct SUBMIT
Process should write ACK message to the
For HTTP/GUI interface uses MSG_VAL_RSP_QUEUE_RCV correct structure to the application based on
queue and SMSResponse structure. queue based on interface interface.
type.

6.1.2 Should backup the message into Database for providing Process should backup Process is backing up the
reliability. message through message by writing to
SDDP_BackupDbWriter. BackupDbWriter process.

Negative Test Cases:

Sr. No. Description Expected Result Observation
6.2.1 If interface in the request structure is filled wrong then the Process should write Process is writing
response may be written to wrong queue due to which the reading response to specified response.
process from that will be affected. interface queue.
6.2.2
6.2.3

Function ID: 7 Function Name: ForwardMsg

Function Overview: Forwards the message to the Active client / to the actual SMSC.

Function Inputs:
Function Outputs: SMSRequest
Configuration/Environment:
Positive Test Cases:

Sr. No. Description Expected Result Observation

7.1.1 Should get the active client ID from the client shared memory and Process should get the Process is writing to the
send the message to the Distributor Server process. Active Client Id, write MSG_DIST_SER_RCV_Q
message with that Client when active client Id is
Id to received.
MSG_DIST_SER_RCV_
Q.

7.1.2 When no client is found active then process forwards the Process should write Process is writing to the
message to the actual SMSC through SDDP_SmsForwarder. message to MSG_SMS_FWD_RCV_Q
MSG_SMS_FWD_RCV_ .
Q.

Negative Test Cases:

Sr. No. Description Expected Result Observation
7.2.1
7.2.2

Function ID: 8 Function Name: DropMsg

Function Overview: Drops the message and send Submit NACK to the application.

Function Inputs: SMSRequest.

Function Outputs: SMSResponse/AseResponse.
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation
8.1.1. Should drop the message and based on interface write back the Process should write Process writing
responses to the application. SUBMIT_NACK to the SUBMIT_NACK to the
respective application respective application
For SMPP/CIMD2 applications uses based on interface. based on interface.
MSG_ASE_LSTNR_TX_RSP queue and AseResponse structure.

For HTTP/GUI interface uses MSG_VAL_RSP_QUEUE_RCV

queue and SMSResponse structure.

Negative Test Cases:

Sr. No. Description Expected Result Observation
8.2.1
Client Shared memory object.

rule analysis table.

Remarks

OK

OK

OK

OK

Remarks

OK

OK
 Remarks

OK

Remarks
ion based on name received.

Remarks

OK

OK

Remarks

OK

OK

on wise rules are defined.

 Remarks

OK

OK

OK

Remarks
 But there is a rare
chance that this
situtaion can happen
as the message is
dropped in previous
process.

age Id and scts and send Submit

Remarks

OK

OK
 OK

Remarks

st. Backup the message to

Remarks
OK

OK

Remarks

OK

Remarks
OK

OK

Remarks

Remarks
OK

Remarks
 Unit Test Plan Of SDDP_SmsForwarder

Module Name: SDDP_SmsForwarder

Function ID: 1 Function Name: Init

Function Overview: The function is called during startup , used to initialize the Database object.

Function Inputs:
Function Outputs:
Configuration/Environment: env's from sddp.env must be set
Positive Test Cases:
Sr. No. Description Expected Result
1.1.1 The funcation initializes the Db object, reads the configurations Proceed for further
and creates IPC. processing if Db object
is intialized.
1.1.4 Init call returns true/false Process initializaiton
successful.

Negative Test Cases:

Sr. No. Description Expected Result
1.2.1 Failed to initialize the process when Queue Keys are not Process should exit.
configured or missing.

1.2.2 Failed to initialize the process when Database object is not Process should exit.
initialized when Database connection is lost.

1.2.3 Fails to initialize the Process if instance number is not configured Process Terminates
for any session

Function ID: 2 Function Name: DeInit

Function Overview: The function is called when the process is terminating.
Function Inputs:
Function Outputs:
Configuration/Environment: env's from sddp.env must be set
Positive Test Cases:
Sr. No. Description Expected Result
2.1.1 The function perform COMMIT operation when it is going to Process should commit
terminate. the records inserted
before exit.

Negative Test Cases:

Sr. No. Description Expected Result
2.1.1.

Function ID: 3 Function Name: ReadSmsFwdRcvQ

Function Overview: Reads the message from MSG_SMS_FWD_RCV_Q and write messages to ASE_MESSAGE table.
Function Inputs: SMSRequest Struct
Function Outputs: SMSRequest Struct
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result
3.1.1 The process will read SMSRequest structure from the Process should read
MSG_SMS_FWD_RCV_Q and inserts messages into Database. message from the
MSG_SMS_FWD_RCV
_Q.

Negative Test Cases:

Sr. No. Description Expected Result
3.1.1

Function ID: 4 Function Name: InsertMsgIntoDb

Function Overview: Inserts messages into Database for different session Ids configured.
Function Inputs: SMSRequest Struct
Function Outputs: SMSRequest Struct
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result
4.1.1 The process will insert message into Database picking Process should insert
SESSION_IDS configured for each account in addition to this message into
also inserts the dispatcher instance. ASE_MESSAGE table.

Negative Test Cases:

Sr. No. Description Expected Result
4.1.1
Forwarder

ame: Init
e object.

Observation Remarks
Initialization success.

OK
Process initializaiton
successful. OK

Observation Remarks
Process exited, giving
proper error cause.

OK
Process exiting.

OK
Process Terminated
OK

ame: DeInit

Observation Remarks
Process is doing
commit.

OK

Observation Remarks
ame: ReadSmsFwdRcvQ
ssages to ASE_MESSAGE table.

Observation Remarks
Process is reading
messages with
message type 0.
OK

Observation Remarks

ame: InsertMsgIntoDb
d.

Observation Remarks
Process is inserting.

OK

Observation Remarks
 Unit Test Plan Of SDDP_BackupDbWriter

Module Name: SDDP_BackupDbWriter

Function ID: 1 Function Name: Init

Function Overview: Initializes DataBase.
Function Inputs: None
Function Outputs: Status of Process Initilalization
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation
1.1.1 Init DbManager success Should continue with Success
initialization
1.1.2
Negative Test Cases:
Sr. No. Description Expected Result Observation
1.2.1 Init DbManager failed Should return failure with Success
appropriate log

Function ID: 2 Function Name: ReadMsg

Function Overview: The function Read Messages from BackupDbWriter queue
Function Inputs:
Function Outputs: Success/failure to Read Message
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation
2.1.1 Read Request message from BackupDbWriter Should return success with Success
Queue success appropriate log.

Negative Test Cases:

Sr. No. Description Expected Result Observation
2.2.1 Read Request message from BackupDbWriter Return failure with Handles Qread
Queue failed appropriate log. Continue to Error and prints
read next request. appropriate logs
and returns false

Function ID: 3 Function Name: ProcessMsg

Function Overview: This function Inserts the messages read from BackupDbWriter queue into DataBase
Function Inputs: None
Function Outputs: Success/failure to insert the Message
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation
3.1.1 Insert Message into DataBase and Updates Should return success with Inserting and
the available Quota in Application_config Table appropriate log. updating the
values in
respective tables

Negative Test Cases:

Sr. No. Description Expected Result Observation
3.2.1 Insert Message into DataBase fails Should return failure with Printing
appropriate log. appropriate logs
and returns false
er

Remarks

OK

Remarks

OK

Remarks

OK

Remarks

OK

ataBase

Remarks
OK

Remarks

OK
 Unit Test Plan Of SDDP_ImsiRetreiver

Module Name: SDDP_ImsiRetreiver

Function ID: 1 Function Name: Init

Function Overview: The function is called during the start up of the process .the process initializes the Dbmanager
object ,Dilaogue Shared memory.

Function Inputs:
Function Outputs: Initializes the Dialogue Shared memory .
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

1.1.1 Initializes the Dialogue Shared Memory Reads Shared Creating Dialogue
Memory keys and shared memory pool
creates the and attaching to it.
shared Memory

Negative Test Cases:

Sr. No. Description Expected Result Observation

1.2.1 If the Dialogue Shared Memory already exists Fails to create Attached to the
Shared memory existing Dialogue
and returns false shared memory.

Function ID: 2 Function Name: ReadMsgFromQueue

Function Overview: The function reads the message from MSG_IMSI_RTV_REQ_RCV_Q with message type 0 ,
structure SMSRequest.

Function Inputs: SMSRequest Structure

Function Outputs: Read from Queue success/fail
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

2.1.1 memset the structure SMSRequest before reading the Success Success
message
2.1.2 Reads the message from Success Success
MSG_IMSI_RTV_REQ_RCV_Q with message type 0
using structure SMSRequest.
Negative Test Cases:
Sr. No. Description Expected Result Observation

2.2.1 If Failed to read the message from Fail/False Handle queue read
MSG_IMSI_RTV_REQ_RCV_Q error and generate
logs.

Function ID: 3 Function Name: Process Message

Function Overview: Generates the dialogue Id and populates the DlgRefDir structure and inserts the same into share
nmemory and writes Ss7 Structure to MSG_PROT_REQ_QUEUE_RCV

Function Inputs: None

Function Outputs: Inserts the structure into shared memory and writes Ss7 Structure to MSG_PROT_REQ_QUEUE_R

Configuration/Environment: Variable specified in sddp.env should be set.

Positive Test Cases:
Sr. No. Description Expected Result Observation

3.1.1 Generates Dialogue Id Allocates a free Success

Dialogue Id.
3.1.2 Inserts the DlgRefDir structure to the dialogue shared Should Insert Success
memory Structure into
SHM.
3.1.3 Writes Ss7 Msg Structure to write SRISM to Success
MSG_PROT_REQ_QUEUE_RCV the
protocoltranslator
Q.

Negative Test Cases:

Sr. No. Description Expected Result Observation

3.2.1 Failed to Generate Dialogue Id Returns Generates Log and

false ,writes write message to
message to SmsForwarder.
MSG_SMS_FWD
_RCV_Q
3.2.2 Failed to Insert Into Shared memory Returns false Success
3.2.3 Failed to write to MSG_PROT_REQ_QUEUE_RCV Returns false Success

Function ID: 3.a Function Name:GenerateDialogueId

Function Overview: Generates a free Dialogue Id using DlgShm linrary function GetFreeShmIndex()

Function Inputs: None

Function Outputs: Dialogue Id
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

4.1.1 Generates a free dialogue id Success Success

Negative Test Cases:

Sr. No. Description Expected Result Observation

4.2.1 If failed to generate a free DialogueId ,writes the Returns false Success
message to MSG_SMS_FWD_RCV_Q
Function ID: 3.b Function Name: InsertIntoSharedMemory
Function Overview: Populates the DlgRefDir structure and inserts the same into the shared memory
Function Inputs: None
Function Outputs: Inserts the DlgRefDir structure into shared memory
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

5.1.1 Populates the DlgRefDir structure and inserts the Success Success
same into shared memory using function
InsertatShmIndex

Negative Test Cases:

Sr. No. Description Expected Result Observation

5.2.1 If failed to insert into shared memory Returns false Generates Log

Function ID: 3.c Function Name:WriteToQueue

Function Overview: Populates the Ss7 structure and writes to MSG_PROT_REQ_QUEUE_RCV

Function Inputs: None

Function Outputs: Writes SRISM Request to MSG_PROT_REQ_QUEUE_RCV
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

6.1.1 Populates the Ss7 Msg Structure and writes to ReturnsSuccess Success
MSG_PROT_REQ_QUEUE_RCV

Negative Test Cases:

Sr. No. Description Expected Result Observation

6.2.1 If failed to write the message to Returns False Handle Q write error
MSG_PROT_REQ_QUEUE_RCV

Function ID: 4 Function Name: ReadResponse

Function Overview: Polls the DlgSharedMemory and calculates the response timeout for each dilaogue Id and if
response is timed out ,then it clears the dialogue and writes the message to
MSG_PROT_REQ_QUEUE_RCV,MSG_SMS_FWD_RCV_Q

Function Inputs: None

Function Outputs: Clears the Dialogue ,Writes end Message to MSG_PROT_REQ_QUEUE_RCV and forwards the
message MSG_SMS_FWD_RCV_Q

Configuration/Environment: Variable specified in sddp.env should be set.

Positive Test Cases:
 Sr. No. Description Expected Result Observation

7.1.1 Polls the DlgShared Memory and calculates the time Return Success Success
difference ,if response is timed out ,then sends the
End message to MSG_PROT_REQ_QUEUE_RCV
and forward the message to
MSG_SMS_FWD_RCV_Q

Negative Test Cases:

Sr. No. Description Expected Result Observation

7.2.1 If failed to poll the DlgShared Memory and calculate Returns False Success
the time difference .
7.2.2 If failed to write End message to Returns False Success
MSG_PROT_REQ_QUEUE_RCV and forward the
message to MSG_SMS_FWD_RCV_Q

Function ID: 4.a Function Name: GetNextDispatchShmIndex

Function Overview: Gets the next dialogue index using DlgShm library function

Function Inputs: None

Function Outputs: Returns the contents at that index
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

8.1.1 Gets the Contents of the Shared Memory at the Return Success Get the Dialogue Id
particular index from the Shared pool

Negative Test Cases:

Sr. No. Description Expected Result Observation

8.2.1 If failed to get the Contents of the Shared Memory at Return False Generates logs.
the particular index

Function ID: 4.b Function Name: ClearTimeOuts

Function Overview: Calculates the time difference for the particular dialogue id ,if timer exceeded then clears that
dialogue contents and writes End Msg to MSG_PROT_REQ_QUEUE_RCV and forwards the message to
MSG_SMS_FWD_RCV_Q

Function Inputs: None

Function Outputs: Writes End Message to MSG_PROT_REQ_QUEUE_RCV and forward the message to
MSG_SMS_FWD_RCV_Q

Configuration/Environment: Variable specified in sddp.env should be set.

Positive Test Cases:
Sr. No. Description Expected Result Observation
9.1.1 Calculates the time difference for the particular Return Success Success
dialogue id ,if timer exceeded then clears that
dialogue contents and writes End Msg to
MSG_PROT_REQ_QUEUE_RCV and forwards the
message to MSG_SMS_FWD_RCV_Q

Negative Test Cases:

Sr. No. Description Expected Result Observation

9.2.1 If timer exceeded and failed to clears that dialogue Return False Success
contents and write End Msg to
MSG_PROT_REQ_QUEUE_RCV and forward the
message to MSG_SMS_FWD_RCV_Q

Function ID: 4.c Function Name: TimeDifferenceInSec

Function Overview: Calculates the time difference between the system time and time from shared memory

Function Inputs: Shared Memory time

Function Outputs: Time Difference between system time and time from shared memory
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

10.1.1 Calculates the time difference between the system Returns time
time and time from shared memory difference
between system
time and time
from shared
memory

Negative Test Cases:

Sr. No. Description Expected Result Observation

10.2.1
10.2.2
10.2.3

Function ID: 4.d Function Name: WriteToSMSFwdQueue

Function Overview: Writes SMS Request structure to MSG_SMS_FWD_RCV_Q ,so that the message is tried by the
other SMSC
Function Inputs: None
Function Outputs:
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

11.1.1 Writes SMS Request structure to Returns True Write Success

MSG_SMS_FWD_RCV_Q ,so that the message is
tried by the other SMSC
Negative Test Cases:
Sr. No. Description Expected Result Observation

11.2.1 If failed to write SMS Request structure to Returns False Handle Qwrite error
MSG_SMS_FWD_RCV_Q

Function ID: 4.e Function Name: WriteEndMsg

Function Overview: Writes Ss7 structure to MSG_PROT_REQ_QUEUE_RCV to close the particular dialogue

Function Inputs: None

Function Outputs:
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

12.1.1 Writes Ss7 structure to Returns True Write Success

MSG_PROT_REQ_QUEUE_RCV to close the
particular dialogue
Negative Test Cases:
Sr. No. Description Expected Result Observation

12.2.1 If failed to write Ss7 structure to Returns False Success

MSG_PROT_REQ_QUEUE_RCV

Function ID: 4.f Function Name: ReleaseShmIndex

Function Overview: Clears the contents of shared memory at that index
Function Inputs: Dialogueid
Function Outputs:
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result Observation

13.1.1 Clears the contents of shared memory at that index Returns True Success

Negative Test Cases:

Sr. No. Description Expected Result Observation

13.2.1
13.2.2
r

zes the Dbmanager

Remarks

OK

Remarks

OK

romQueue
with message type 0 ,

Remarks

OK

OK

Remarks

OK

essage
inserts the same into shared

SG_PROT_REQ_QUEUE_RCV

Remarks

OK

OK

OK

Remarks

OK
OK

OK

alogueId
hmIndex()

Remarks

OK

Remarks

OK
haredMemory
ed memory

Remarks

OK

Remarks

OK

eue
RCV

Remarks

OK

Remarks

OK

onse
each dilaogue Id and if

_RCV and forwards the

 Remarks

OK

Remarks

OK

OK

patchShmIndex

Remarks

OK

Remarks

OK

Outs
ceeded then clears that
he message to

e message to

Remarks
 OK

Remarks

OK

nceInSec
shared memory

Remarks

OK

Remarks

SFwdQueue
e message is tried by the

Remarks

OK
 Remarks

OK

sg
articular dialogue

Remarks

OK

Remarks

OK

mIndex

Remarks

OK

Remarks
 Unit Test Plan Of SDDP_AseDispatcher

Module Name: SDDP_AseDispatcher

Function ID: 1 Function Name: GgiDispatchMgr()

Function Overview: This is a constructor function . Which will intialise the Submit structure
Function Inputs: None
Function Outputs: Submit structure gets initialised
Configuration/Environment: Variable specified in sddp.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result

1.1.1 Initialising the submit structure Submit structure gets

initilised successfully

Negative Test Cases:

Sr. No. Description Expected Result

1.2.1
1.2.2
1.2.3

Function ID: 2 Function Name: Init

Function Overview: This function initilizes Db Manager , Reads the config and creates queue
Function Inputs: None
Function Outputs: Initilisation success/failure
Configuration/Environment: Variable specified in sddp.env should be set. Ipc.cfg, ggi.cfg should be present in config directo
Positive Test Cases:
Sr. No. Description Expected Result

2.1.1 Reads configuratons in ipc.cfg, ggi.cfg, Successfully Read

all the configurations

2.1.2 Create the Gateway TX Queue using the queue keys Create gateway TX
read from ipc,cfg queue

2.1.3 Database connection is getting inilised Successful

initilisation of DB
manager with
username/password
sourced

Negative Test Cases:

 Sr. No. Description Expected Result
2.2.1
2.2.2
2.2.3

Function ID: 3 Function Name: FetchMsg()

Function Overview: This function fetches the messages from ase_message Table dispatch to the gateway Tx Queue .
Function Inputs: None
Function Outputs: Fetch sucesss/Fail
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result

3.1.1 Fetches AseMsg from ASE_MESSAGE Table when Messages fetched

the next retry time < sysdate acooording to the succesfully
instance

3.1.2 Stores the values AseMsg structure Fills the AseMsg

structure

Negative Test Cases:

Sr. No. Description Expected Result

3.2.1
3.2.2
3.2.3

Function ID: 4 Function Name: DispatchMsg()

Function Overview: Dispatches the fetched message to gateway TX queue
Function Inputs: None
Function Outputs: Dispatch to gateway Queue success/Fail
Configuration/Environment: .
Positive Test Cases:
Sr. No. Description Expected Result
4.1.1 Checks validity period of msg has expired Validity period of the
message should be
less than current
time
4.1.2 Checks the number of attempts exceeded then updates
maximum attempts next_retry_time for
this msg before
writing to queue
(Function ID:4a)

4.1.3 Writes to gateway TX Queue after converting to Writes to gateway tx

GateWay message (Function Id :4b) queue

4.1.4

Negative Test Cases:

Sr. No. Description Expected Result

4.2.1 Checks if validity period of msg has expired Validity period is not
less than current
time .Hence deletes
the message
(Function ID:4c)

4.2.2 Checks the number of attempts exceeded then Max number of

maximum attempts delivery attempts
exceeded. Deletes
msg.(Function ID:4c)

4.2.3

Function ID: 4b Function Name: ConvertToGatewayMsg()

Function Overview: Converts the record fetched from ASE_MESSAGE Table to Gateway message
Function Inputs: None
Function Outputs: None
Configuration/Environment: Variable specified in gateway.env should be set.
Positive Test Cases:
Sr. No. Description Expected Result

4b.1.1 Converts the AseMsg records fetched from Converts to gateway

ASE_MESSAGE Table to AseRequest structure with structure successful
which gateway can read

4b.1.2
Negative Test Cases:
Sr. No. Description Expected Result

4b.2.1
Function ID: 4c Function Name: DeleteMsg()
Function Overview: Deletes the record from ASE_MESSAGE Table when validity expires or when the maximum retry attemp
exceeds
Function Inputs: None
Function Outputs: Delete Success/Fail
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result

4c.1.1 Deletes the AseMsg according to the sequence number Deleted succefully
and status

4c.1.2

Negative Test Cases:

Sr. No. Description Expected Result

Function ID: 4a Function Name: UpdateMsg()

Function Overview:Updates the ase_message
Function Inputs: None
Function Outputs:
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result

4a.1.1 Updates the next retry attempt and status Updates the retry
attempt and
status(MSG_ATTEM
PTED)

Negative Test Cases:

Sr. No. Description Expected Result
AseDispatcher

Name: GgiDispatchMgr()
bmit structure

Observation Remarks

Success

OK

Observation Remarks

Name: Init
nd creates queue

c.cfg, ggi.cfg should be present in config directory

Observation Remarks

Success

OK
Success

OK
Success

OK
 Observation Remarks

Name: FetchMsg()
Table dispatch to the gateway Tx Queue .

Observation Remarks

Success

OK
Success

OK

Observation Remarks

Name: DispatchMsg()

Observation Remarks
 Deleting Msg as the
VP is lessthan current
time.
OK
Update Success

OK
Success

Ok

Observation Remarks

Success

OK
Success

Retry message till

max SMSC deliver
attempts reached

Name: ConvertToGatewayMsg()
e to Gateway message

t.

Observation Remarks

Success

OK

Observation Remarks
 Name: DeleteMsg()
alidity expires or when the maximum retry attempts

Observation Remarks

Delete Success

OK

Observation Remarks

Name: UpdateMsg()

Observation Remarks

Success

OK

Observation Remarks
 Unit Test Plan Of SDDP_AseRespMgr

Module Name: SDDP_AseRespMgr

Function ID: 1 Function Name: Init

Function Overview: This function initilizes Db Manager , Reads the config and creates queue
Function Inputs: None
Function Outputs: Initilisation success/failure
Configuration/Environment: Variable specified in sddp.env should be set. Ipc.cfg, ggi.cfg should be present in config directo

Positive Test Cases:

Sr. No. Description Expected Result Observation

1.1.1 Reads configuratons in ipc.cfg, ggi.cfg, Successfully Read all Success

the configurations

1.1.2 Create the Gateway RX resp Queue using the Create gateway RX Success
queue keys read from ipc,cfg Response queue

1.1.3 Database connection is getting inilised Successful Success

initilisation of DB
manager with
username/password
sourced

Negative Test Cases:

Sr. No. Description Expected Result Observation

1.2.1

Function ID: 2 Function Name: ReadRespMsg()

Function Overview: This function reads the Ase response message from gateway RX Response Queue
Function Inputs: None
Function Outputs: Reads Response messages from RX Response queue Success/Failure
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

2.1.1 Reads responses from gateway RX response Successfully read the Success
queue gateway responses

2.1.2

Negative Test Cases:

 Sr. No. Description Expected Result Observation

2.2.1
2.2.2
2.2.3

Function ID: 3 Function Name: ProcessRespMsg()

Function Overview: Process the positive and negative response messages
Function Inputs: None
Function Outputs: Prossesed postive/negative response success/fail
Configuration/Environment: .
Positive Test Cases:
Sr. No. Description Expected Result Observation

3.1.1 Checks errorCode is NO_ERROR for positive Positive response Success

response received

3.1.2 Process positive response (Function ID:3.a) Successful Success

processing of positive
response

3.1.3

Negative Test Cases:

Sr. No. Description Expected Result Observation

3.2.1 Checks errorCode is other than NO_ERROR for Negative Respose Delete message if
negative response received NACK is of
permanent error.

3.2.2 Process negative response (Function ID:3.b) Successful Delete message if

processing of NACK is of
nagative response permanent error.

3.2.3

Function ID: 3a Function Name: ProcessPositiveResp

Function Overview: Processes the positive responses and updates/Deletes the message according DSR REQ Flag
Function Inputs: Sequence No
Function Outputs: Process positive response success/fail
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation
3a.1.1 Gets the record for the sequence number passed Fetches the record Success
for the sequence no
(sequence no should
be present in
ASE_MESSAGE
table)

3a.1.2 check for DSR NOT required If DSR not required Success
the update the
message with state,
msg id and delete the
message

3a.1.3 Check for DSR required Updates Success

NEXT_RETRY_TIME
to (current time +
next submit time) ,
msgID and
status(MSG_SUBMI
TTED)

Negative Test Cases:

Sr. No. Description Expected Result Observation

3a.2.1 Failed to get the record for the sequence number DB_NO_RECORD_F Print Logs
passed OUND_ERR

3a.2.2 If other DB Error while getting record for the increment the retry Success
seqence no attempt

Function ID: 3b Function Name: ProcessNegativeResp()

Function Overview: Processes the positive responses
Function Inputs: Sequence No
Function Outputs: Processes the positive responses success/Fail
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

3b.1.1 Check for Permanent errors , Gets the AseMsg Gets the Success
from ASE_MESSAGE table corresponding
AseMsg for
sequence no ,
update the message
with
state(MSG_PERMAN
ENT_ERROR), blank
msg id and error
code and delete the
message

3b.1.2 Check for Temporary errors If temporary errors , Success

function returns true

3b.1.3

Negative Test Cases:

Sr. No. Description Expected Result Observation

3b.2.1 Failed to get the record for the sequence number DB_NO_RECORD_F Print Logs
passed OUND_ERR

3b.2.2 If other DB Error while getting record for the increment the retry Success
seqence no attempt

6.2.3
gr

uld be present in config directory

Remarks

OK

OK

OK

Remarks

()
nse Queue

Remarks

OK
 Remarks

sg()

Remarks

OK

OK

Remarks

OK

OK

eResp
ording DSR REQ Flag

Remarks
 OK

OK

OK

Remarks

OK

OK

veResp()
 Remarks

OK

OK

Remarks

OK

OK
 Unit Test Plan Of SDDP_AseMsgHdlr

Module Name: SDDP_AseMsgHdlr

Function ID: 1 Function Name: Init

Function Overview: This function initilizes Db Manager , Reads the config and creates queue
Function Inputs: None
Function Outputs: Initilisation success/fail
Configuration/Environment: Variable specified in sddp.env should be set. Ipc.cfg, ggi.cfg should be present in config
directory

Positive Test Cases:

Sr. No. Description Expected Result Observation

1.1.1 Reads configuratons in ipc.cfg, ggi.cfg, Successfully Read all Success

the configurations

1.1.2 Create the Gateway Rx Queue using the Create gateway RX Success
queue keys read from ipc,cfg Msg queue

1.1.3 Dsr Handler object gets initilized Successful initilisation Success

of Dsr handler object

1.1.4 Database connection is getting inilised Successful initilisation Success

of DB manager with
username/password
sourced

Negative Test Cases:

Sr. No. Description Expected Result Observation

1.2.1

Function ID: 2 Function Name: ReadAseMsg()

Function Overview: Reads the DSR from Rx Msg queue
Function Inputs: None
Function Outputs: Reads fromR X queue success/Fail
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

2.1.1 Reads DSR from gateway RX Msg queue Successfully read the Success
DSR

2.1.2
Negative Test Cases:
Sr. No. Description Expected Result Observation

2.2.1
2.2.2
2.2.3

Function ID: 3 Function Name: ProcessDsr()

Function Overview: Process the DSR messages
Function Inputs: None
Function Outputs: Prossesed DSR success/failure
Configuration/Environment: .
Positive Test Cases:
Sr. No. Description Expected Result Observation
3.1.1 Checks for MsgId format in Dsr

Gets the AseMsg for message id Positive Dsr received Success

passed :messageState for msg gets deleted
:DELIVERED/ACCEPTED from database
(Function ID: 3b)

3.1.4

Negative Test Cases:

Sr. No. Description Expected Result Observation

3.2.1 Failed to get the AseMsg for message id Inserts into Insert Success
passed DSR_RETRY table
(Function ID: 3a) with
next retry time and
number of attempts.

3.2.2 Gets the AseMsg for message id msg gets deleted Deleting message
passed :messageState :UNDELIVERABLE from database from the AseMsg
.Receives Negative Dsr with peramnat error (Function ID: 3b) table.

3.2.3 Gets the AseMsg for message id Update the message Update Success and
passed :messageState with current time as resubmits message.
:DELETED:/EXPIRED:/REJECTED:Receive next retry time
s Negative DSR with temporary error (Function ID: 3c)

Function ID: 3b Function Name: DeleteMsg

Function Overview: Deletes the message for passed messageID after updating with MsgStatus and Msg Error
Function Inputs: messageID, status, error
Function Outputs: Delete Msg success/failure
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

3b.1.1 AseMsg gets deleted AseMsg gets deleted Deletes message

successfully when positive
response is received.

Negative Test Cases:

Sr. No. Description Expected Result Observation

3b.2.1 Couldnot find find the record with AseMsg not found Print Logs and returns
messageID while deleting from the API.

Function ID: 3c Function Name:UpdateMsg

Function Overview: Sets current time as next retry time and update the record
Function Inputs: None
Function Outputs: Update success/Fail
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

3c.1.1 Updates the record Setting current time as Successfully updated Updating
next retry time the record NEXT_RETRY_TIME
when DSR is
requested and waits
for the DSR.

3c.1.2

Negative Test Cases:

Sr. No. Description Expected Result Observation

3c.2.1
3c.2.2

Function ID: 3c Function Name: InsertDsrIntoRetryTable

Function Overview: Inserts the record into DSR Retry table with MsgID, DSR Retry time ,RX data
Function Inputs: None
Function Outputs: Insert success/Fail
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

3c.1.1 Inserts the record into DSR Retry table with Message Written to Insert success. This is
MsgID, DSR Retry time ,RX data DSR_RETRY observed when the
DSR is received
before Submit
Response.

3c.1.2

Negative Test Cases:

Sr. No. Description Expected Result Observation

3c.2.1
3c.2.2
dlr

eue

should be present in config

Remarks

OK

OK

OK

OK

Remarks

Remarks

OK
 Remarks

Remarks

Messages are gettting

deleted.

Remarks

OK

OK

OK
Status and Msg Error

Remarks

OK

Remarks

OK

Remarks

OK

Remarks

ryTable
RX data
 Remarks

OK

Remarks
 Unit Test Plan Of SDDP_AseDsrRetry

Module Name: SDDP_AseDsrRetry

Function ID: 1 Function Name: Init

Function Overview: This function initilizes Db Manager , Reads the config and creates queue
Function Inputs: None
Function Outputs: Initilisation success/fail
Configuration/Environment: Variable specified in sddp.env should be set. Ipc.cfg, ggi.cfg should be present in config directo

Positive Test Cases:

Sr. No. Description Expected Result Observation

1.1.1 Reads configuratons in ipc.cfg, ggi.cfg, Successfully Read all Success

the configurations

1.1.2 Create the Gateway Rx Queue using the queue Create gateway RX Success
keys read from ipc,cfg Msg queue

1.1.3 Database connection is getting inilised Successful initilisation Success

of DB manager with
username/password
sourced

Negative Test Cases:

Sr. No. Description Expected Result Observation

1.2.1

Function ID: 2 Function Name: ReadDSR()

Function Overview: Fetches the record from DSR_RETRY table for records which has retry time less than sysdate , fills in t
gateway request structure and deletes the record from DB

Function Inputs: None

Function Outputs: Fetch and delete from DSR retry table
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

2.1.1 Fetches the record from DSR_RETRY table for Succefully fetched and Success
records which has retry time less than sysdate , deleted the record from
fills in the gateway request structure and deletes DSR_RETRY table
the record from DB

2.1.2
Negative Test Cases:
Sr. No. Description Expected Result Observation

2.2.1

Function ID: 3 Function Name: ProcessDsr()

Function Overview: Process the DSR messages
Function Inputs: None
Function Outputs: Prossesed DSR success/failure
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

3.1.1 Checks for MsgId format in Dsr

3.1.2 Checks for MsgId in ASE_MESSAGE Table Found MsgID in Deletes the record
ASE_MESSAGE Table from the
DSR_RETRY table
and write the DSR
to Gateway Rx
Queue.

Negative Test Cases:

Sr. No. Description Expected Result Observation

Function ID: 3b Function Name: WriteDsrIntoQueue()

Function Overview: Writes the DSR into RX Queue
Function Inputs: None
Function Outputs: Write to Queue success/failure
Configuration/Environment:
Positive Test Cases:
Sr. No. Description Expected Result Observation

3b.1.1 Write the message to RX queue for DSR Retry Write to RX queue Success
Success

Negative Test Cases:

Sr. No. Description Expected Result Observation
ry

ould be present in config directory

Remarks

OK

OK

OK

Remarks

time less than sysdate , fills in the

Remarks

OK
 Remarks

Remarks

OK

Remarks

eue()

Remarks

OK

Remarks