On 6/29/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
The CargoTestSetup class that you added to the test framework (was this Wendy's first commit of Java code? :-) nicely leverages the fact that Cargo will figure out which container to use based on system properties (specifically "cargo.container.id"). However, the way that this class is being used in Tomcat5xWelcomeTestCase in the shale-blank application is definitely not container-agnostic, because it presumes to use Tomcat 5.x.
(Cargo itself doesn't use the system properties. The CargoTestSetup class looks for that property and uses the value to construct Deployable and LocalConfiguration objects.) The end goal is to be able to run the same tests in multiple containers with a single execution of 'mvn test'. I think CargoTestSetup in shale-test will eventually be deprecated in favor of some 'test runner' code that has been contributed to Cargo by Atlassian, so I'm not inclined to do much else with it. It works for what I needed already, and if you've found a better way to configure it, that's fine. Thanks, -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
