> > So failsafe will pickup > > ITblahblah.java > BlahblahIT.java > > And a third form that I forget >
*ITCase.java http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#includes /Anders > > > > > > > > > > 3) Run integration tests after compile? > > > > The real reason for question 2 is that I wish to run integration > tests > > > > only after I have deployed the new application to ensure the > > > > integration tests run on the server with the new content. Is there a > > > > way to do this? > > > > > Sounds like you should consult my answer to a related question: > > > > > > http://stackoverflow.com/questions/16935290/maven-deploy-webapp-to-tomcat-before-junit-test/16936585#16936585 > > > > OK, this was very helpful too. In this case, I am working with a > > multi-module project and I decided it was best to add our selenium > > tests in a new project to keep them away from other project code. We > > have 13 pom.xml files, not counting the one I am adding. So this is my > > next challenge, to ensure I get this project executing after the > > others have done their job and deployed to the app server. > > > Dependencies will ensure sequencing of modules > > > > > > Why, sometimes I've believed as many as five impossible things before > > after-noon tea. Time for one more before I knock off at 5pm. > > > > Rob > > :) > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > <javascript:;> > > For additional commands, e-mail: users-h...@maven.apache.org > > <javascript:;> > > > > > > -- > Sent from my phone >
