Recently I wrote about the necessity in TDD of specifying both sides of a behavioral boundary, and its epsilon. This is important because we want a complete, detailed record of the critical business rules and other values in the system. But there is another reason that this is important. It has to do with the … Continue reading "Specifying Boundaries in TDD: Part 2"