maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Green <>
Subject Re: maven-failsafe-plugin: what is it actually intended for?
Date Fri, 15 Nov 2013 11:06:33 GMT
On 15 November 2013 06:57, Vincent Latombe <>wrote:

> maven-failsafe-plugin implies some specific steps are required *before*
> (pre-integration-test) and *after* (post-integration-test) the test
> execution, which allows to do fire up a container then turn it off after
> the tests (for example).
> Then, only after these, the test results are evaluated during 'verify'
> phase and will fail the build if needed.
> This is unlike maven-surefire-plugin, that performs both the tests
> execution and verification in the same step, which prevents you from doing
> any kind of cleanup outside of test execution.
> So, using failsafe or surefire boils down to a single question : do you
> need to perform any set up/teardown outside of the test execution
> framework? If yes, use failsafe, if no, use surefire

That provides ambiguity since junit supplies before and after routines for
exactly the same reason but in a very different context.

I'm keen to see the knowledge from this thread make it into the
documentation. What procedures exist to allow this?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message