# Diameter dictionary:
STD_DICTIONARY=stacks/avps_etsi.xml,stacks/avps_ietf.xml,stacks/avps_tgpp.xml,stacks/commands_baseProtocol.xml
-APP_DICTIONARY=stacks/commands_pccPS_EricssonSAPC_se.xml
+APP_DICTIONARY=stacks/commands_qosControl.xml
DICTIONARY=$STD_DICTIONARY,$APP_DICTIONARY
# Perhaps the stack is not fully defined:
KINDNESS=-ignoreErrors
STARTED=\`pgrep $1 2>/dev/null\`
[ \$? -eq 0 ] && { echo "Already started!"; echo "\$STARTED" ; exit 1 ; }
0> launcher.traces
+rm -f counters/*
# Execution line:
./$@ &
echo \$! > .pid
actually required by process. They are located at './DTDs'. Stacks are available at './stacks'.
There are also some stuff (hex/xml examples, etc.) which could be useful.
-The script 'test.sh is an example of scheduler which launch a request to the server and then
-waits for a specific answer to continuing testing. Some functions could be reused to prepare
-any kind of testing. The method used is quite simple: monitor the launcher traffic log for
-incoming activity. An advanced FT test framework involves the use of the ANNA::diameter API
-in an ad-hoc diameter client executable (for example we could define an incoming handler in
-different libraries which represent different test cases, linking them to a common simple
-diameter client agent).
+The directory 'tests' contains resources to create FT test cases. The script 'common.sh' implement
+a basic scheduler to launch a request to the server, waits for incoming activity, retrieve the
+answer received and match such message with certain criteria. Execute 'case_1.sh' as example.
+
+An advanced FT test framework involves the use of the ANNA::diameter API in an ad-hoc diameter
+client executable (for example we could define an incoming handler in different libraries which
+represent different test cases, linking them to a common simple diameter client agent). But with
+this simple scripts we could do something valid to start with.
STARTING THE PROCESS
--------------------