Often a given behavior will change due to a certain condition: sometimes the system will behave one way, sometimes another. We call this kind of behavioral change a “boundary” and it should be specified as such in TDD. For example, let’s say there is a business rule that dictates how a passed-in value should be … Continue reading "Specifying Boundaries in TDD: Part 1"