4 ms·

Noticed this yesterday, it is odd that apple does not catch bugs like this in their qa process.

• josegonzalez 14y ago
  Programming is hard. Likely they didn't have a test for every possible date.
  • Derander 14y ago
    It seems likely that the fact that this is the 1st of the year is related. This should be an obvious edge condition for testing.
  • rimantas 14y ago
    Seems like calendars and time are really hard to get right. The missing December on Android is a good example of that too. http://arstechnica.com/gadgets/2012/11/december-conspicuously-missing-from-android-4-2s-people-app/ http://arstechnica.com/gadgets/2012/11/december-conspicuousl...
  • andrewcooke 14y ago
    if you're writing tests, you should aim for corner cases. for date-based applications that would include the first and last days in the year, leap years, etc. programming can be a bit less hard if you learn to do it right.
    • roc 14y ago
      Good luck enumerating all the edge-case tests for date functions every single time you need a date.
      • deleted 14y ago
        [deleted]
      • deleted 14y ago
        [deleted]
• leephillips 14y ago
  Odd, but not new: http://news.ycombinator.com/item?id=4916627 http://news.ycombinator.com/item?id=4916627
• kemiller 14y ago
  Calendar-based stuff is absurdly difficult to get right. Even if you have something that seems to work you likely have a hidden error somewhere. That's not really an excuse -- edge conditions like DST on/off, and end-of-year should be first on your test list. But calendars suck to work with.
• sourc3 14y ago
  Same here! After missing three calls, I was wondering if I had turned this on by mistake. Glad to see it on front page of HN :)