SVI-STP SSME
Squire Technologies - Confidential Document
Page
50
of
57
9
Internal Testing
9.1
Description
In the XML it is possible to create a set of tests to be run against the configuration at point of
validation. The XSD defines an element called Test. This is used to create an internal test to be run
when the SVI-STP loads a new XML file. The testing does not impact the live system, but each test
tests individual endpoints within the SSME XML.
The format of the test is as follows:
<
Test
epname
=
"xxxxx"
name
=
"yyyy"
>
<
Input
ic.sccp.cdpn.digits
=
"5978199036"
ic.sccp.cdpn.tt
=
"10"
tcap.opCode
=
"MO Forward Short
Message"
/>
<
ExpectedOutput
ssmeResult
=
"Ignore"
/>
</
Test
>
9.2
Test
Attributes for the Test element is epname – the endpoint to be tested and the name of the test
The sub-element Input contains the information that is required to test a specific path in the SSME
xml, this can contain the following information:
ic.mtp.xxx where xxx is the dpc, opc or ni
ic.sccp.xxx where xxx is the sccp information such as called party number, calling party
number information
tcap.opCode the TCAP operation to be simulated
map.cnts the map expression to be tested.
9.3
Expected Output
The sub-element ExpectedOutput contains the validation that is required to be checked on
completion of the test. This can then contain the following information:
linkset – the outgoing linkset for a routed message
destination – the outgoing destination for a routed message
ssmeResult – the result expected from the SSME will be ignore, NoMatch, Match, Route,
NoRoute or Reject
og.mtp.xxx where xxx is the dpc, opc or ni
og.sccp.xxx where xxx is the translated sccp information for the outgoing message
map.translate – the converted map contents string.