<html>#2320: make choice of tests to consider runnable an env variable
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</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>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Currently the Cactus testsuite system has not way to select which tests to run other than using the interactive menus shown by <code>make sim-testsuite</code>. Simfactory works around this by copying only the tests requested by a user to the run directory. </p>
<p>Pull request <a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactus/pull-requests/82/rhaas-testslist/diff" rel="nofollow">https://bitbucket.org/cactuscode/cactus/pull-requests/82/rhaas-testslist/diff</a> adds an environment (or make for that matter) variable <code>CCTK_TESTSUITE_RUN_TESTS</code> that can be set to the list of thorns and / or test parfiles to run. It uses the same syntax that simfactory uses, so eg “GRHydro” will run all GRHydro tests while “GRHydro Carpet/kasner_amr” would run all GRHydro tests as well as the “kasner_amr” test in Carpet.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2320/make-choice-of-tests-to-consider-runnable'>https://bitbucket.org/einsteintoolkit/tickets/issues/2320/make-choice-of-tests-to-consider-runnable</a></p>
</html>