Changeset 1642 for trunk

Timestamp:

Dec 12, 2008, 10:09:19 PM (14 years ago)

Author:

Peter

Message:

adding a paragraph on how to access files in tests, and fixing indentation

File:

• trunk/test/README (modified) (2 diffs)

trunk/test/README

@@ -66 +66 @@
   typical usage.
 
-  Tests shall return 0 at success and -1 otherwise (see
-  test::Suite::return_value()). If the test should be skipped for some
-  reason it shall return 77.
+  Tests shall return 0 at success and -1 otherwise (see
+  test::Suite::return_value()). If the test should be skipped for some
+  reason it shall return 77.
 
   When a test is run without verbose flag, it should be silent also at
@@ -74 +74 @@
   test::Suite class (see functions err() and out()).
 
-  If a test grows large, avoid having several tests in one long
-  main. It creates long correlations and complicates debugging and
-  extending the test. If you don't want to split the test into several
-  files, split the test into several independent sub-functions.
+  If a test needs a data file, place the data in directory
+  'test/data'. However, you should feel free to re-use the data files
+  already there. It should be possible to run test from any directory,
+  in particular from builddir in a VPATH build. To achieve this, use
+  test::Suite::filename() to get the absolute path to the file.
+
+  If a test grows large, avoid having several tests in one long
+  main. It creates long correlations and complicates debugging and
+  extending the test. If you don't want to split the test into several
+  files, split the test into several independent sub-functions.