Similarly, there are separate tests for dollar and franc multiplication. Looking at the code, we can see that there is no difference in the logic at the moment based on the currency (there was a difference when there were two classes). We can delete testFrancMultiplication() without losing any confidence in the behavior of the system
isn't this looking at it in a very implementation driven way as opposed to a test/behavior driven way.. ? shouldn't we make our decision on the tests to have based on the behavior to expect, not our knowledge of the CURRENT implementation?
Share this highlighthttp://www.safaribooksonline.com/a/test-driven-development/17841543/