Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:14774
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net, Jochem Maas <jochem@iamjochem.com>
Message-ID: <420A7850.8020000@php.net>
Date: Wed, 09 Feb 2005 21:53:36 +0100
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
References: <20050209203810.59785.qmail@lists.php.net> <420A7781.50504@iamjochem.com>
In-Reply-To: <420A7781.50504@iamjochem.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] timeoffset per process
From: lsmith@php.net (Lukas Smith)

Jochem Maas wrote:
> Lukas Smith wrote:
> 
>> Hi,
>>
>> I am currently writing test cases for time sensitive code. Meaning 
>> this code behaves different depending on the time of day. Obviously 
>> one solution is to mess with the server time, but that is going to 
>> screw up anything else going on the server.
>>
>> The only solution that I have currently come up with requires alot of 
>> uglyness by making my code call a wrapper function instead of time() 
>> or date() which optionally adds an offset to the time that can be set 
>> before executing the tests.
>>
>> It seems like a minor feature to add to the date extension. But then 
>> again I can understand that Derick doesnt feel features for testing 
>> fits into the new date extension. Am I missing an obvious alternative? 
>> Is there a better place to add this feature?
> 
> 
> maybe install a test setup on your local machine?
> then you can mess with the local time, no problems?

this is what I do now, but obviously its far from ideal, especially 
since you also want to be able to run your tests on your production 
server to check if the install went fine or when bugs are reported.

regards,
Lukas