A quick lesson on how to get rid of a pair of classes that shouldn't have been introduced in the first place.
One thing stands out here: he doesn't do a lot of work to verify that the tests he wants to get rid of are redundant. Think, zap, done. And here, that's the right thing (toy problem, not too much to keep in your head, and of course it happens the tests are actually unnecessary).
Of course, if we are deleting tests that are passing, there's no problem in the sense that the production code is still right. The potential difficulty would be if we continue to assume that some part of the code is covered by tests when in fact it is not, and then start working on that code expecting to be afforded the same protections we had when the test was in place, and start making mistakes.
No comments:
Post a Comment