On 6 June 2013 14:44, Dennis Schetinin <chaetal@gmail.com> wrote:
TDD is not about tests (as a bug-finding/debugger tool) at all. And the anti-regression feature of TDD is just the secondary one.
First of all, TDD is about structuring thinking/creation process. And "test" here is a tool that allows and makes developer to formalize requirements and to translate them to the language they will be implemented in. This starts and really drives coding. Thus, a programmer that really masters TDD (really means an ability to apply "pure" TDD for all programming activities: both top-down and bottom-up design activities) is expected to produce much better architecture/design/code.
⦠So, I don't think TDD is somehow obsolete by Smalltalk. Vice versa, TDD should be really efficient here. And it's a great pity TDD is not actually popular in Smalltalk society. One of the dire consequences is that modern Smalltalk environments are not "TDD-oriented" and don't advantage from good TDD methodology.
Why do you think Smalltalk environments aren't "TDD oriented"? What would an IDE need to be TDD oriented? (I can think of something like Ruby's guard, which runs tests every time you save a file.) frank