Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 9
    This is a really important part of TDD that is often overlooked and I've rarely seen talked about in articles and guides - it's really important to test edge cases and boundary conditions as I find that's the source of 90% of bugs - of-by-one errors, over and underflows, last day of the month, last month of the year, leap-years etc etc Commented Jul 13, 2018 at 8:51
  • 2
    @GoatInTheMachine - and 90% of those 90% bugs are around daylight savings time transitions..... Hahaha Commented Jul 14, 2018 at 6:06
  • 1
    You can first divide the possible inputs in equivalence classes and then determine the edge cases at the classes' borders. Of ourse that's an effort which may be larger than the development effort; whether that's worth it depends on how important it is to deliver software as error-free as possible, what the deadline is and how much money and patience you have. Commented Jul 16, 2018 at 12:04
  • 2
    This is the correct answer. A lot of busines rules require you to divide a range of values to intervals where they are cases to be handled different ways. Commented Jul 16, 2018 at 12:24