3 ms·
To be fair, I have difficulty imagining how you could practically test for this kind of bug ahead of time. You can't test every feature in every app in the app
by rcthompson 9y ago
To be fair, I have difficulty imagining how you could practically test for this kind of bug ahead of time. You can't test every feature in every app in the app store with the clock set to every possible date and time.
- eropple 9y agoIt's not every app. It's a problem with the OS and notifications.
- zuppy 9y agoThis is something you test with unit tests. It should have been pretty easy to discover it. I know most of us don’t have that much cover by these tests, but also we don’t have hundreds of millions of daily users. They ahould invest into this.
- userbinator 9y agoThis is not a bug that should be caught by testing, but by simply looking at the code and thinking about it (and often getting others to do the same for your code.) The current fashion of "write some code, write some tests, modify either until the tests pass" is not a way towards fewer bugs. All it leads to is the analogy of "throwing things on a wall and seeing what sticks". Tests should be for reducing the remaining uncertainty about the functioning of some code, and not a substitute for actually trying to get it right through careful reasoning.
- Tobba_ 9y agoUnit testing seems to frequently result in overconfidence.