Alternatively, if possible, you could possibly run the app with both configurations in parallel (two executions of jetty-maven-plugin in pre-integration-test and post-integration-test phase, using different ports), and run you tests twice, for each app / port (two executions of failsafe at integration-test phase)
On Fri, Oct 12, 2018 at 8:44 AM Anders Hammar <and...@hammar.net> wrote: > I'd say you need two modules; one for each IT setup. Each module is a Maven > project and will then run the integration tests. The actual integration > test code could then be in a third module and you declare a dependency on > that artifact. > > /Anders > > On Thu, Oct 11, 2018 at 11:21 PM Ellis, Scott <selli...@harris.com.invalid > > > wrote: > > > Hi, > > > > I have a project that builds a webapp and runs integration tests against > > it using the failsafe plugin and the jetty-maven-plugin. > > > > That is, I use the jetty-maven-plugin to start jetty in the > > pre-integration-test phase, run the tests, then shut jetty down in the > > post-integration-test phase. > > > > Now, my web app can have an entirely different configuration in addition > > to the existing one, so I need to start jetty with a new config and run a > > new suite of tests, while maintaining all the existing functionality. > > > > So what I really want to do it run these phases twice: > > > > pre-integration-test > > integration-test > > post-integration-test > > > > First I want to run them with the my webapp configured the old way, and > > then run the same phases again with my webapp configured the new way. > > > > Any advice on how to do this? The configurations can be set with system > > properties. The problem is how to run those phases twice in that order. > > > > Thanks for any insight you can offer, > > Scott > > >
