On 6/25/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
Traditionally for testing my webapp, I've started up an embedded jetty server instance to serve the pages. While this generally works (some classpath trickery has to happen for HiveMind), it seems that the jetty6 plugin would obviate the need for this. Unfortunately, it looks like the remainder of the lifecycle blocks until the jetty6 plugin halts execution. So, is there anyway to start up the server and run my tests, short of using two different maven instances?
There is an example of using the Cargo Maven 2 plugin to start and stop a container in the pre- and post- integration test phases, here: http://cargo.codehaus.org/Maven2+plugin This actually isn't the recommended way to do it, since if the tests fail, Cargo never gets a chance to stop the container. Better is to use the Java API in a TestSetup class that wraps your tests. There's an example of that, here: http://cargo.codehaus.org/Functional+testing HTH, -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
