From 0818fb6b59c6eae28c21e94cac609f9d93084478 Mon Sep 17 00:00:00 2001 From: Matthias Maier Date: Thu, 10 Feb 2022 04:20:59 -0600 Subject: [PATCH] add documentation --- doc/developers/testsuite.html | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/doc/developers/testsuite.html b/doc/developers/testsuite.html index 445b9d3956..74e7d708cb 100644 --- a/doc/developers/testsuite.html +++ b/doc/developers/testsuite.html @@ -475,7 +475,7 @@ category/test.output just category/test.output. In pseudo code: 
 category/test.[with_<string>(<=|>=|=|<|>)<on|off|version>.]*
-              [mpirun=<N|all>.][threads=<N|all>.][expect=<y>.][binary.][<debug|release>.]output
+              [mpirun=<N|all>.][threads=<N|all>.][expect=<y>.][binary.][<debug|release>.](output|run_only)
Normally, a test will be set up so that it runs twice, once in debug and once in release configuration. @@ -608,6 +608,20 @@ category/test.output.4 category/test.expect=run.output

+

+ The testsuite also suppors the special file ending + .run_only that indicates that the diff stage should be + skipped in order to reach the PASSED stage. You can + specify the keyword by changing the file ending from + .output to .run_only: +

+category/test.run_only
+
+ Note that this is semantically different from specifying + expect=diff.output: The expect keyword requires that a + test reaches a specified stage but fails in it. In this case + the test has to reach the DIFF stage but fail it. +

-- 2.39.5