On 6/22/06, Clifton Craig <[EMAIL PROTECTED]> wrote:
How would you configure Maven2 to handle functional tests? I have a bunch of tests that I don't want to run every time the build runs. Instead I want to run them manually on special occasions (Hannukkah, the Swedish new year, when the Phillies win the world series, etc.). I want to know where to put the compiled output (target/functional-test-classes?) and how to tell maven to pick them up from a different source folder during compile. I'm thinking of storing the functional tests under src/functional-tests. What are youre thoughts on this?
There have been several threads on this in the past few months, and the advice is usually to put your functional/integration tests in a separate module. Maven does have an 'integration-test' phase, so for this module you can use a packaging type of 'pom' and bind executions of the plugins you need to compile and run the tests to the right phases. There is an example of this in Better Builds with Maven book: http://www.mergere.com/m2book_download.jsp You *can* get both unit tests and functional tests to work in a single module, but I would only do that for a very simple webapp. We're doing that for the Shale framework example apps, where maintaining a separate test module for each example would be a pain. This is an area of Maven development that's still under discussion. There are some JIRA issues open and a Wiki page or two where ideas are being considered. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
