<li><a href="#restrictbuild">Restricting tests for build configurations</a></li>
<li><a href="#restrictfeature">Restricting tests for feature configurations</a></li>
<li><a href="#mpi">Running tests with MPI</a></li>
+ <li><a href="#expect">Changing condition for success</a></li>
<li><a href="#layoutaddtests">Adding new tests</a></li>
</ol>
<li><a href="#submit">Submitting test results</a></li>
just <code>category/test.output</code>:
<pre>
- category/test.[with_<feature>=<on|off>.]*[mpirun=<x>.][<debug|release>.]output
+ category/test.[with_<feature>=<on|off>.]*[mpirun=<x>.][expect=<y>.][<debug|release>.]output
</pre>
Normally, a test will be set up so that it runs twice, once in debug and
once in release configuration.
files for different numbers of MPI processes.
</p>
+ <a name="expect"></a>
+ <h3>Changing condition for success</h3>
+ <p>
+ Normally a test is considered to be successful if all test stages
+ could be run and the test reached the <code>PASSED</code> stage (see
+ the <a href="#runoutput">output description</a> section for details).
+ If (for some reason) the test should succeed ending at a specific
+ test stage different than <code>PASSED</code> you can specify it via
+ <code>expect=<stage></code>, e.g.:
+ <pre>
+
+ category/test.expect=run.output
+ </pre>
+ </p>
+
+
<a name="layoutaddtests"></a>
<h3>Adding new tests</h3>