*** empty log message ***

diff --git a/allParam/test/README b/allParam/test/README
index ac8314a7cb4c88e5148e15db409ac4e79f74d9fe..902868e50821dac81a15b3d228952bb5ce4fab10 100644 (file)
--- a/allParam/test/README
+++ b/allParam/test/README
@@ -11,34 +11,36 @@ Content
 -------
 
 1. testing requirements
-  1.1 ca test
-  1.2 file test
-  1.3 ora test
-  1.4 psql test
-  1.5 tcl test
 2. testing results
 
 1. testing requirements
 -----------------------
 
-  
-
-1.1 ca test
-
-1.2 file test
-
-1.3 ora test
-
-1.4 psql test
-
-1.5 tcl test
+  For the tests there are of course needed all the libraries against which the
+user aplications have to be linked, too. This can easily be extracted out of
+the Makefile.
 
 2. testing results
 ------------------
 
-
-
-Please send bug reports to
+  The testing results are written down to files called <lib>_test_protocol.txt
+in the test directory. There is also included a timing information, which
+unfortunately is (depending on the shell you are using) not always written to
+the file but sometimes only to stderr. Note that channel access is not
+deterministic as timeouts can occur on a heavily used network, which can be
+tuned changing the TIMEOUT definition in ca/param.h. Of course the enviroment
+needed at runtime is also needed when testing (i.e. a channel access server
+has to provide the data in case of ca_test_suite and network connection to the
+database hosts are needed for ora_test_suite and psql_test_suite.
+
+  There is also a huge field of errors not tested yet (containing all overflows
+of name lengths, index lengths, param file lengths, array lengths and so on -
+including restrictions that occur not due to param library limitations but also
+limitations in database access or channel access. Anyhow the stucture of the
+tests is very easy so you can enhance the suite with little efford or propose
+additional tests as of course you can also:
+
+Send bug reports to
 
 Benjamin.Sailer@ph.tum.de