We are new to Maven and Selenium. We are developing a set of portlets and have chosen to use Selenium to test the functionality of these web-applications (each portlet is a web-application). To be tested, the portlets must be compiled, packaged into a WAR, and deployed to our portal. Then the Selenium functional tests must be executed on each of the portlets. The Selenium Plug-ins for Maven allow us to start the Selenium server appropriately, but it seems like we need to execute Maven twice to get to do the functional testing:
mvn compile package deploy mvn test (or mvn integration-test) Seems like the Maven build lifecycle does not have good support for this: validate generate-sources process-sources generate-resources process-resources compile process-classes generate-test-sources process-test-sources generate-test-resources process-test-resources test-compile test prepare-package (2.1) package pre-integration-test integration-test post-integration-test verify install deploy We have to "deploy" our portlets before we can do the "integration-test", right!?! Is there a way to define our own phases to do what we need? One solution is to wrap Maven with another tool like Ant to do the steps we need done, but I'm hoping a more elegant solution is available... Any thoughts you are willing share are greatly appreciated. Thanks, -Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
