3 Template for xml messages (message.dtd), dictionaries (dictionary.dtd) and services (services.dtd)
4 are informative, not actually required by process. They are located at './DTDs'. Stacks are available
5 at './stacks'. There are also some stuff (hex/xml examples, etc.) which could be useful.
7 The directory 'tests' contains resources to create FT test cases. The script 'common.sh' implement
8 a basic scheduler to launch a request to the server, waits for incoming activity, retrieve the
9 answer received and match such message with certain criteria. Execute 'case_1.sh' as example.
11 An advanced FT test framework involves the use of the ANNA::diameter API in an ad-hoc diameter
12 client executable (for example we could define an incoming handler in different libraries which
13 represent different test cases, linking them to a common simple diameter client agent). But with
14 this simple scripts we could do something valid to start with.
18 Launch the executable process without arguments to see a complete command-line help.
19 Don't be scared. There are plenty of possibilities but the 'run.sh' script and 'services.xml'
20 have been prepared for the type of launcher you wanted.
24 Management interface for this version is based on SIGUSR2 signal caugh. Use './operation.sh'
25 script to send any operation to the process. Ask for help with that script to see all the