From a36842deee9faaf137cd04be42fbe79c8aa43054 Mon Sep 17 00:00:00 2001 From: maier Date: Sun, 20 Oct 2013 18:07:20 +0000 Subject: [PATCH] Add documentation git-svn-id: https://svn.dealii.org/branches/branch_port_the_testsuite@31345 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/doc/developers/testsuite.html | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/deal.II/doc/developers/testsuite.html b/deal.II/doc/developers/testsuite.html index 754e765dc3..31573f99e8 100644 --- a/deal.II/doc/developers/testsuite.html +++ b/deal.II/doc/developers/testsuite.html @@ -63,6 +63,7 @@
  • Restricting tests for build configurations
  • Restricting tests for feature configurations
  • Running tests with MPI
    • +
  • Changing condition for success
  • Adding new tests
  • Submitting test results
    • @@ -433,7 +434,7 @@ just category/test.output: 
     
-    category/test.[with_<feature>=<on|off>.]*[mpirun=<x>.][<debug|release>.]output
+    category/test.[with_<feature>=<on|off>.]*[mpirun=<x>.][expect=<y>.][<debug|release>.]output
    Normally, a test will be set up so that it runs twice, once in debug and once in release configuration. @@ -509,6 +510,22 @@ files for different numbers of MPI processes.

    + +

    Changing condition for success

    +

    + Normally a test is considered to be successful if all test stages + could be run and the test reached the PASSED stage (see + the output description section for details). + If (for some reason) the test should succeed ending at a specific + test stage different than PASSED you can specify it via + expect=<stage>, e.g.: + 

    +
+    category/test.expect=run.output
+
    +

    + +

    Adding new tests

    -- 2.39.5