<h3>Tests with multiple comparison files</h3>
<p>
Sometimes it is necessary to provide multiple comparison files for a
- single test. Additional comparison files have the same path as the
- main comparison file (in this case <code>test.output</code>) followed
- by a dot and a variant description:
+ single test, for example because you want to test code on multiple
+ platforms that produce different output files that, nonetheless, all
+ should be considered correct. An example would be tests that use the
+ <code>rand()</code> function that is implemented differently on
+ different platforms. Additional comparison files have the same path
+ as the main comparison file (in this case <code>test.output</code>)
+ followed by a dot and a variant description:
<pre>
category/test.output
category/test.output.2
<ol>
<li> make the test more robust such that differences can be
expressed in round-off errors detectable by numdiff.
- <li> restrict comparison files to specific feature versions
+ <li> restrict comparison files to specific
<a href="#restrictfeature">versions of an external feature</a>.
</ol>
</p>
<ol>
- <li> Removed: The testsuite does no longer support compiler constraints
- of the form <code>".compiler=[NAME]...</code>.
+ <li> Removed: The testsuite no longer supports compiler constraints of
+ the form "<code>.compiler=[NAME]...</code>".
<br>
(Matthias Maier, 2015/08/21)
</li>