Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates
 74.125.82.180 as permitted sender)
Message-ID: <51A0B6E2.9000704@gmail.com>
Date: Sat, 25 May 2013 15:04:34 +0200
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Server-integ tests are taking way too long...
References: <51A08EF4.6010502@gmail.com> <51A0A806.5000601@stefan-seelmann.de>
In-Reply-To: <51A0A806.5000601@stefan-seelmann.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le 5/25/13 2:01 PM, Stefan Seelmann a écrit :
> On 25.05.2013 12:14, Emmanuel Lécharny wrote:
>> The PasswordPolicy tests are expensive because they need to sleep to
>> check some time condition. At this point, I'm wondering if it would not
>> worth creating a separate module for it.
> Hm, maybe we can avoid using the "real" time (via
> System.currentTimeMillis) and use a "time provider" instead. By default
> it obtails the system time. But for tests the returned time can be
> modified according to the test needs. JodaTime for example has a
> DateTimeUtils class with static accessors for getting and setting the
> time. In other projects we used a TimeProvider interface with different
> implementations for production and tests.

That would be an extremely useful thing. I think we can benefit from
such an addition for the replication tests, especially those which are
time dependents. We can even simuate some use cases that are time
dependent this way.


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com