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?
regards,
Lukas
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 oftime()
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?
rgds,
Jochem
regards,
Lukas
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 oftime()
ordate()
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
Lukas Smith wrote:
Jochem Maas wrote:
...
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.
yeah, sorry wrong list. I thought I was answering on generals :-/
my apologies. (should have recognized the name.)
regards,
Lukas