With the new DST kicking in in March, I have 1 customer who wants us to test and prove our software and webbased application will continue to work. Anyone else running into this?? I am trying to figure the best way to test. Mainly thinking to work with my network team and set the clock ahead on the server, go into our aps and prove they still work, then set the internal clock back to reflect the correct time. If anyone else has to do this I would love to hear how yo are going to test. Course I am arguing with the customers that since they never had issues before, they wont now just because the DST is being pushed up to March. Thanks all in advance.
Sad thing is it is sometimes just easier to do those simple tests than try to explain why you don't really need to think of them needing to be done, but is any testing really bad testing when none is planned?
I haven't had this requirement set to test with my side of the product as yet, but I am sure it is going to play into it as some point, but you have pretty much described how I would be going for a simple quick-feel-nice test for an end user on te matter.
Insanity: doing the same thing over and over again and expecting different results
We have 15 customers as of now, and its always this same one that puts us through the ringer for things like this. The others go with the flow. lol. But there is always one in the group I guess that needs to be comforted.