Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of baerrach@gmail.com designates
 209.85.128.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAG54imb_BZ4NBxmJmFqcTsZQuj4+O8D6=JfqzygjAsYyTYkEfQ@mail.gmail.com>
References: 
 <CAG54imb9m34Q4VsyMoGdp2t4fcPMEfxR-1zpcU6kNWF+vsXwoA@mail.gmail.com>
	<CAKDUN1uO9_c_s=4d3XuVz61GP2hLrTuuNxXCQB6nM6KVSx0b+g@mail.gmail.com>
	<CAG54imb_BZ4NBxmJmFqcTsZQuj4+O8D6=JfqzygjAsYyTYkEfQ@mail.gmail.com>
Date: Tue, 14 Jan 2014 11:15:14 +1030
Message-ID: 
 <CADVp3v9Qi_2S3OQ2LkxVpX+rWzX2wYS0jvq03wN+Xj68_PMrbg@mail.gmail.com>
Subject: Re: Running cleanup code after tests in multi-module project.
From: Barrie Treloar <baerrach@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On 14 January 2014 10:49, Todd Chapman <todd@chaka.net> wrote:
> Anders,
>
> I agree with you. Unfortunately I inherited this project and there is setup
> required that is identical for each module and is expensive to set up and
> tear down. It will take time to refactor the tests to be less expensive to
> prepare.
>
> In the mean time I'm looking for ways to deal with situation I have now.

It sounds like these tests are not unit tests if they need any
setup/teardown of external systems.
These are integration tests.

It would make more sense to move these tests into one integration-test module.
You then get your one setup/teardown and all the tests are together.

It should be a matter of moving things around in version control
rather than having to refactor the tests.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org