Improvement: show avp name if known (validation)

[anna.git] / example / diameter / launcher / resources / ft-client / README

diff --git a/example/diameter/launcher/resources/ft-client/README b/example/diameter/launcher/resources/ft-client/README
index 37c1353..84e5128 100644 (file)
--- a/example/diameter/launcher/resources/ft-client/README
+++ b/example/diameter/launcher/resources/ft-client/README
@@ -4,13 +4,14 @@ Template for xml messages (message.dtd) and dictionaries (dictionary.dtd) are in
 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
 --------------------