I work for a company that like most spans all of the time zones. As the Lead QA guy I have just been task with coming up with a general strategy for all of our OS's and Apps. This will also include embedded devices. Is any one else out there doing the same type of test planning.
[ QUOTE ]
Does the time setting of the client machine matter? If so, what of the client time is not the same as the server time?
[/ QUOTE ]
Here's another thought to consider - what if the locality DOESN'T participate? For example: think Arizona (and I think Indiana) here in the US - they don't change.
Also are the files pulled all times of the day/night? Be sure to confirm the crossover hour (2am) on the date of the change. Will it just skip the hour - what about the 'fall back' can the system handle two files that technically have the same timestamp but are actually different (or will one be overwritten).
Lastly - I believe the exact date of the change is being altered (I recall this being a big topic of discussion this past October - next year it will be moving one week later into November). I'm not sure if the same is happening in the Spring. Double check that the application doesn't change on the wrong date.
We're in the last stages of testing this change now; I'm not sure the estimable Mr. Bush considered the IT implications when he signed it into law [img]/images/graemlins/smile.gif[/img].
Our business is world-wide. Functionally, we had to test every time-zone affected by the change, those states which do not recognize DST, and verify existing world-wide timestamps remain unchanged. We identified those test cases that had apps that are time-dependent and ran them through. In addition, we have future-dated and back-dated capabilities that had to be tested (before, at, after the change). Several test suites required we switch our system dates to the DST date to verify, which was not the easiest thing in the world to accomplish. It was equally challenging to coordinate the tests using interfaces that link to outside entities.
We think we're covered now, but it was a nasty little project [img]/images/graemlins/smile.gif[/img].