Ben wrote: >Actually some Smalltalk'ers consider the debugger a major facilitator of >TDD by mostly coding from within the debugger.
Yes. It is part of what we present as "TDD done right". We've shown it at a devnology user group meeting in March. If anyone is interested in doing a presentation to their local (non-smalltalk) user group, just let me know. >1. Before writing any application code, write a test. which only contains self assert: false. which is the simplest thing needed to get the test to fail. >2. Execute that test straight away. Of course it fails because you >haven't written any application code. >3. Up comes the debugger - now "from within the debugger" add the >application code needed to satisfy the test. >4. Repeat. While writing the application code, you often notice the name of the test method is not right. Not being able to fix that in the debugger is one of the annoying things why "smalltalk environments are not TDD oriented" (Even though they are much better than other environments for TDD). Another is lack of browser support for long method names. Tests tend to have (very) long names Stephan
