-File Names
-The unit test script will find all files named *_test.c and assume that
-they can be compiled and executed using the local Makefile. Files
-which are needed by these programmes (e.g. common functions) are expected
-to reside in this directory as test_*.c and test_*.h files and should
-be directly included by the test programmes (not built and linked). This
-allows the unit test script to isngore the functions, and files, when
-generating coverage reports.
+Because of the static nature of the RMr library, tests with the
+intent of providing coverage information, as opposed just to providing
+functional verification, are a bit trickier. To that end, the test
+files in this directory are organised with three file name formats:
+
+ test_*.c tools for testing, not tests
+
+ *_test.c main test programmes which can be compiled in
+ a stand-alone manner (e.g. gcc foo_test.c)
+
+ *_static_test.c Test functions which are real tests and are
+ included by one or more stand-alone driver.
+
+The unit_test script will search only for *_test.c and will ignore
+*_static_test.c files when building it's list for testing.
+
+
+Use the command 'unit_test.ksh -?' to see the usage information
+and complete set of options available.
+
+
+Merging .gcov files
+As some unit test programmes may not be able/designed to cover all
+of a module completely, the script will merge each .gcov prooduced
+with the prior, matching, file after each pass. The result is a
+final .gcov file that shows the coverage of the module over all
+tests. This allows a true coverage value to be determined while
+permitting more simple tests to be used without the requirement of
+each test to cover everything.