This patch provides preliminary support for run-time tests using the Cactus framework. The way rttests were being provided in t2 and t3 was mavenized and a special build file, build-rttest.xml, is now being generated by maven. An additional delagator is added so the ant target is 'ant maven:rttest'. The patch includes updating ProjectProperties to create a pattern set based on the jar dependencies. This was used to build the war file for the cactus test.
Apply the patch and copy the build-rttest.xml into src/template/build. You may need to add the delegator by hand into the build-maven.xml if you want to try it with t2 or t3. The t3 rttest attempts to copy a pipeline configuration file into the correct location before the test runs. This patch has no 'hook' for pre-test configuration. I have gotten the test to work by moving the testing pipeline into the WEB-INF/conf directory of the testapp and updating the tr.props to load the file from there. This directory is pacakged up into the war and deployed in the test container, so the running turbine instance has it availiable. The requirement for pre-test configuration may be an indication that the way the tests are implemented could be cleaned up. Ideally each testcase should set itself up and not rely on the build system for configuration. It may not be possible in all cases though. I've been using this patch for the entire week with t2 and t3, no problems. I'm not sure this is the best route to go for cactus integration, but it allows our runtime tests to be executed and may clear the path to using maven soely for builds. Instead of pushing this into cvs, I thought as a patch other could give it a try. It is a pretty easy way to get our rttest's running again with maven.
patch
Description: Binary data
build-rttest.xml
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
