[mailto:p...@hammant.org]
Sent: Saturday, October 13, 2018 9:00 AM
To: Maven Users List
Subject: [SUSPICIOUS] Re: [SUSPICIOUS] Re: Running integration tests twice
against different webapp configurations
You're explicitly calling stop() on both Jetty instances ... (pass or fail) and
not just letting it fa
or already started," even with a different
> key and port.
>
> Thanks,
> Scott
>
> -Original Message-
> From: Thomas Broyer [mailto:t.bro...@gmail.com]
> Sent: Friday, October 12, 2018 2:34 AM
> To: Maven Users List
> Subject: [SUSPICIOUS] Re: Running inte
e: Running integration tests twice against different
webapp configurations
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
There's Cuppa which is super cool and allows to control such things to a
very fine level.
https://github.com/cuppa-framework/cuppa/
It is not clear that Cuppa has multi-year life though. I wish it did.
On Thu, Oct 11, 2018 at 10:21 PM Ellis, Scott
wrote:
> Hi,
>
> I have a project that builds
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
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
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.
