<html>#2869: Modify cactus flesh and SimFactory to enable post processing during testsuite
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Deborah Ferguson</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Context: The Cactus testing framework includes the ability to provide an executable in the test.ccl file to run over files and then compare the output rather than comparing the files themselves. This enables, for example, running a script to print the contents of an h5 file so they can be compared during testing. </p>
<p>The issue: this executable is currently only looked for inside <thorn>/util but that isn’t where compiled utilities generally are put. Additionally, when using SimFactory to perform the tests, it copies everything needed to run the tests into scratch, but doesn’t currently copy these compiled utilities. </p>
<p>To enable usage of this feature, we need to<br>
1) In the cactus flesh, tell it to also look in exe/<config-name> where utilities are compiled to and <br>
2) In simfactory, also copy the utilities in exe/<config-name> when copying everything else (the test data, the executable, etc)</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2869/modify-cactus-flesh-and-simfactory-to'>https://bitbucket.org/einsteintoolkit/tickets/issues/2869/modify-cactus-flesh-and-simfactory-to</a></p>
</html>