I think the tests could provide valuable design feedback about the code under test, so it is good to have them. I can respond to those feedbacks effectively only when I'm writing them first, otherwise it might be too late. But this is a long topic.
When I write tests first, I like the fact that the initial state of my test is red. So I can catch the point when it changes to green. If this happens when I expect, then I can be sure that I understand what is happening, and I managed to write a meaningful test. Writing tests afterwards makes easier to write tests which are always green. To avoid this I have to break the test after I finished it by changing something in the code. This is an extra step which I can save by writing tests first. -- View this message in context: http://forum.world.st/Pharo-dev-Necessity-of-TDD-with-Smalltalk-tp4691867p4692373.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
