Refactor mdrun integration tests
authorMark Abraham <mark.j.abraham@gmail.com>
Mon, 10 Mar 2014 12:29:26 +0000 (13:29 +0100)
committerGerrit Code Review <gerrit@gerrit.gromacs.org>
Tue, 23 Sep 2014 13:51:08 +0000 (15:51 +0200)
commit293630c584fc91d87438538030a612fce4ed31f3
tree4438af2f3a4fa49edfb7b4115b79421d25d2c17d
parent897da8f26d941a8ceb8f6d131d2a13198d19298f
Refactor mdrun integration tests

Future work will need the ability for such a test to call mdrun more
than once and compare the results. This means that a test fixture
object needs to be able to keep track of the separate files in an
orderly way. Created SimulationRunner to manage the setup and calls to
grompp and mdrun, somewhat like an implementation
class. MdrunTestFixture now owns a single such object. Created
MdrunTestFixtureBase to be the common point for managing issues of
controlling the execution environment of mdrun, so that future work
can derive classes from it that use more than one SimulationRunner.

Change-Id: Ic2ab82b3bacb01f9bf77de67909567352fc2d306
src/programs/mdrun/tests/compressed_x_output.cpp
src/programs/mdrun/tests/interactiveMD.cpp
src/programs/mdrun/tests/moduletest.cpp
src/programs/mdrun/tests/moduletest.h
src/programs/mdrun/tests/replicaexchange.cpp
src/programs/mdrun/tests/rerun.cpp
src/programs/mdrun/tests/swapcoords.cpp
src/programs/mdrun/tests/trajectory_writing.cpp
src/testutils/integrationtests.h