Adobe and Apple Didn't Unit Test For "Forward Date" Bugs. Do You? 169
Posted
by
timothy
from the everyone-misses-a-few dept.
from the everyone-misses-a-few dept.
llamafirst writes "As the year flipped to 2013, we learned that Adobe and Apple don't test for "forward date" bugs. Adobe prevented any copy of FrameMaker 10 from launching and Apple broke Do Not Disturb for the first week of 2013. Surely some more critical and safety systems also have lurking issues. Got tips for catching time/date bugs 'from the mysterious future?' (Also, obligatory link to Falsehoods programmers believe about time.)"
leap year (Score:4, Interesting)
Why? (Score:5, Interesting)
Why does software functionality depend on the date? Calculation issues maybe... but failure to lauch? WTF? I'm most curious to learn how this even happens.
I've had the opposite experience.... (Score:4, Interesting)
I've had mock SSL certs and HTTP cookie jars that both expired and made it seem like the system was failing all over the place during unit/integration/general testing.
So just watch out in general because this can swing either way...
Re:leap year (Score:4, Interesting)
Yeah, I don't entirely understand why apple is having such a rough time getting basic time keeping and scheduling working...