Hi all, I posted this question a couple of weeks ago (with a slightly different subject), but got no response.
I was looking for a way to setup and tear-down a test-run environment separately for *every* test that I'm running. Currently, our tests are started using a special script that handles this. However, the problem with this setup is that I cannot do a 'ctest -D MemoryCheck', because that will not memory-check my test program, but the wrapper script instead. So I was looking for a way to do this setup and tear-down in the pre-test and post-test phase. Is this possible at all? Another "interesting" problem to solve is that the current test wrapper script also analyses the output of a test program and compares it to a reference output, in order to decide if the test succeeded or failed. Would it be possible to do this in a post-test phase? The main goal I'm trying to achieve here is to make it possible to memory-check my test programs, ideally using 'ctest -D MemoryCheck'. Best regards, Marcel Loose. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
