QT: Added QT_PROJECT variable

[omk.git] / tests / README.tests

diff --git a/tests/README.tests b/tests/README.tests
index 1acc864c4e5b9ba78ec037de8a4cb5dd554bdbaf..8aa6cbe6f8c292ef77e98216e54354e312870986 100644 (file)
--- a/tests/README.tests
+++ b/tests/README.tests
@@ -29,7 +29,7 @@ counted).
 
   - runtest*.rules: Specifies the set of rules the testcase applies
     to. If there is more runtest files, every testcase can have its
-    own .rules file. The syntax of this files is describes in section
+    own .rules file. The syntax of this files is described in section
     `Rules description'.
 
 * Testcase Execution:
@@ -43,18 +43,22 @@ counted).
   Each execution of testcase should produce the following outputs:
 
   - Exit status of make or runtest: 
-        0 - the testcase was successfully passed
-        1 - the testcase failed
-        2 - the testcase cannot be executed (e.g. because the needed
-            compiler is not available)
+        zero - the testcase was successfully passed
+        other than zero - the testcase failed or cannot be executed
+                         (e.g. because the needed compiler is not
+                         available)
 
   - Error message:
-    In the case of error, the file '_error' should contain more
-    detailed description of the error.
+    In the case of nonzero exit status, if file '_canttest' exists in
+    the same directory as Makefile.rules, it is considered that the
+    test cannot be executed (i.e. the compiler is missing) and the
+    content of that file is provided as error message in results
+    log. Otherwise, the test is considered as failed and file '_error'
+    can contain more detailed description of the error.
 
   - stdout and stderr: The output of testcase execution is captured
     and is included in the results log. It should contain useful
-    information to ease debugging problems.
+    information to ease the debugging process.
 
 Rules Description
 -----------------