I have always used surefire for integration tests with a Maven profile (to activate them on demand since they are time consuming). What benefit am I missing not using failsafe?
Cheers, Paul On Tue, Oct 28, 2014 at 5:26 AM, Oliver B. Fischer <[email protected]> wrote: > Hi, > > I see a lot of people using *Surefire for intergation tests instead of > Failsafe*. I think the reason for this is that *Failsafe* is from my > perspective is *not integrated* in Maven *as is possible*. > > While unittest (*Test.java) are executed if we place them in > |src/test/java| for integrationtests we have to add > > |<build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-failsafe-plugin</artifactId> > <executions> > <execution> > <phase>integration-test</phase> > <goals> > <goal>integration-test</goal> > <goal>verify</goal> > </goals> > </execution> > </executions> > </plugin> > </plugins> > </build> > | > > Why is is not possible to integrate Failsafe in the same convenient way as > Surefire. > > I prepared a small example project you can checkout via Git > > |git clone https://bitbucket.org/obfischer/bugreport-maven-failsafe.git > | > > Integrating Failsafe in the same way as Surefire would be great for a lot > of people I think. > > Oliver > >
