Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
From: Stefan Bodewig <bodewig@apache.org>
To: dev@commons.apache.org
Subject: Re: [compress] How to deal with long running test?  Maven Profile?
References: <1313075066.83638.YahooMailClassic@web27804.mail.ukl.yahoo.com>
Date: Thu, 11 Aug 2011 17:29:21 +0200
In-Reply-To: <1313075066.83638.YahooMailClassic@web27804.mail.ukl.yahoo.com>
	(Mark Struberg's message of "Thu, 11 Aug 2011 16:04:26 +0100 (BST)")
Message-ID: <87y5z0c6ge.fsf@v35516.1blu.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On 2011-08-11, Mark Struberg wrote:

> A common pattern is to introduce an own 'run-its' profile which
> configures surefire to pickup those tests.

How? 8-)

Do I put the test into a separate directory and tell surefire inside the
profile to look into that other dir?

> It's just not good to have tests which in summary takes longer than 3
> minutes to run. This usually leads to developers using
> -Dmaven.test.skip=true which is kind of counter productive...

Absolutely, that why I want to move them to a separate profile.

If you want to test reading of an archive of more than 4GB then you
simply have no choice but to wait for the data to be read - and the
writing tests are even worse, at least on my box.  It simply takes a few
minutes just to move the data from or to the disk.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org