Testing Against The Current Time

ploeh blog : Testing Against Non-Determinism

ploeh blog : Testing Against Non-Determinism — Sat, 12 May 2007 21:47:07 GMT

PingBack from http://blogs.msdn.com/ploeh/archive/2007/05/11/TestingAgainstNonDeterminism.aspx

Testing Against Guids

ploeh blog — Sat, 12 May 2007 21:47:44 GMT

This is the second in a small series of posts about testing against non-determinism. In this installation,

re: Testing Against The Current Time

kost — Sun, 13 May 2007 20:19:29 GMT

If you do not take the time zone into consideration, CheckMonday() may not return the same result if run on two different computers.

While UTC is good for log files, I would recommend a time zone that takes account of daylight saving times; otherwise you will have to change any reconfiguration twice a year.

Kost

re: Testing Against The Current Time

ploeh — Mon, 14 May 2007 11:06:31 GMT

Hi Kost :)

Thank you for your comment. I'm not sure I understand why the CheckMonday test may yield a different result on different machines.

No matter the time zone of the machine, the injected date is May 7th, 2007. Since the test is calling the test target via an in-process call, the time zone of the test code is always the same as the time zone of the test target.

Thus, I think May 7th, 2007 will always be May 7th, 2007, or am I missing your point?

Testing Against The Passage of Time

ploeh blog — Mon, 14 May 2007 20:08:30 GMT

This is the fourth in a small series of posts about testing against non-determinism. In this installation,