The main difference of the failsafe-maven-plugin is that it doesn't abort the build on errors. Thus you can cleanly shutdown the server after all tests did run. There is actually not much difference regarding the phase as we already configured the surefire plugin to run in the integration-test phase.
LieGrue, strub ----- Original Message ----- > From: Christian Kaltepoth <[email protected]> > To: [email protected] > Cc: Mark Struberg <[email protected]> > Sent: Friday, July 6, 2012 10:48 AM > Subject: Re: [DISCUSS] drop the integration-test module? > > +1 for dropping it. > > As I already mentioned some time ago, having two places for the tests > (tests in the integration-test module and test in the module itself) > is IMHO a bad idea. And I think it is easier to have the tests > directly in the modules. > > Regarding the failsafe plugin: Would this bring us any advantage apart > from the fact that the integration tests would run in a different > Maven phase? > > Christian > > 2012/7/6 Romain Manni-Bucau <[email protected]>: >> if surefire is still used for weld or owb by default +1 >> >> - Romain >> >> >> 2012/7/6 Mark Struberg <[email protected]> >> >>> and merge those profiles to the main impl modules? >>> >>> Our integration tests are currently pretty hard to debug as we unpack > the >>> test sources to the integration test module and then run the tests. >>> >>> It was originally planed that the core tests do always run with Weld or >>> OWB and only the container specific tests will run again if an EE > container >>> got specified. But it turned out that this is a bit complicated to > debug. >>> >>> >>> >>> Thus I'm thinking about dropping the integration-test modules and > move all >>> the profiles to parent/code/pom.xml >>> >>> I also like to move the integration tests from moving the surefire > plugin >>> to failsafe. >>> >>> LieGrue, >>> strub >>> >>> > > > > -- > Christian Kaltepoth > Blog: http://chkal.blogspot.com/ > Twitter: http://twitter.com/chkal >
